codeBeamer is shipped with a web container (tomcat), database server (Derby) and on Windows with Subversion, Git and Mercurial (hg). On Linux, Unix, MAC-OS systems the required SCM(s) must be installed via package manager. The installation typically takes 10-15 minutes.
The pre-configured Derby database is for evaluation purposes only, and should not be used for production purposes.
codeBeamer's server must always be started by the same operating system user to avoid file and database access problems. The server requires read and write file permissions for its own working and temporary files, and for the databases.
codeBeamer's server inherits access permissions from the user who started the server. To avoid permission problems on Linux/Unix systems, it is good practice to create a new operating system user (for example codebeamer) with very restricted access to the file system, and to use this system account to start codeBeamer. In this case, even when there is no restriction specified in the codeBeamer configuration file, a restricted access to the file system is guaranteed on the operating system level.
Installation on a Single Server
This paragraph describes installation on a single server.
To install codeBeamer on your server, first download and execute a single self extract file for your platform.
Installation on Windows
After downloading the self extract file, you can start the installation by double-clicking on the self extract file.
It is strongly recommended installing codeBeamer as Service to ensure that codeBeamer will be running also after the user logged out.
Installation on Linux
On Linux systems we suggest to install and run codeBeamer under a special user account, typically codebeamer.
Do not install or run codeBeamer as root.
If you want to put an Apache Web server in front of codeBeamer (e.g. to access codebeamer via the standard HTTP(S) ports 80 (443) or to access managed Subversion repositories via HTTP protocol), you should install the Apache server for your platform first (see Configuring Tomcat for codeBeamer, Configuring Apache for Subversion) and then create the codebeamer user in the same group where Apache is:
E.g. on Red Hat Enterprise:
sudo adduser codebeamer --ingroup apache
Before installing codeBeamer:
JRE/JDK: It must be ensured that either Openjdk-1.7 or 1.8 or Oraclejdk-1.7 or 1.8 can be found in PATH.
To install codeBeamer:
Log in or sudo as user codebeamer
into the home directory of the codebeamer user (.e.g. /home/codebeamer).
Make the downloaded installation file (e.g. CB-7.0-GA-linux.bin) executable
To make upgrading to newer codeBeamer versions easier, we suggest to create a symbolic link called CB in the codebeamer home directory, that points to the current/active version (e.g. CB-7.0):
ln -s CB-7.0 CB
If you later install a new codeBeamer version, (e.g. CB-7.1) you will get a new directory CB-7.1 parallel to existing CB-7.0), but by simply redirecting the CB symbolic link to CB-7.1 all scripts based on CB will now consistently operate on the new version.
The codeBeamer server must be started before you can access codeBeamer.
If you select to install codeBeamer as a Windows Service (during the Installation), codeBeamer will be automatically started and stopped with the system. To manaully start/stop/restart the service, use the Windows Services Control panel.
Only if you did not choose to install codeBeamer as a service, you can start and stop it manually!
From the Window's Start menu select
Programs -> CodeBeamer x.x -> Start CodeBeamer Server
To stop the server, use:
Programs -> CodeBeamer x.x -> Stop CodeBeamer Server
When the server has started, start your browser on the server's URL with:
Programs -> CodeBeamer x.x -> Browse CodeBeamer
Linux, Unix, MAC-OS
From shell the commands as below can be used:
To stop codeBeamer, type:
Starting during System Boot (Linux, Unix)
Typically when Linux starts, the codeBeamer service should also start automatically.
For that create a new file in /etc/init.d/codebeamer with this content: