Running the TeamForge connector server as a service on Linux systems depends on the service launcher JSVC, a part of the Apache Commons Daemon. Since this is a native executable, we only supply it for certain architectures.
If the following steps don't work for you, try
these instructions to create a version of JSVC for your machine. Alternatively, the package management system of your distribution may contain a package providing the commons-daemon.
Important: You must use a JVM that matches the architecture of your Linux distribution -- if you're using a 64-bit distribution, you must use a 64-bit JRE (and a 32-bit JRE for 32-bit systems).
-
Set up the
ccf.conf file for your environment. In addition, edit the two
lines in bin/CCFMaster.sh that specify where you unzipped the TeamForge connector server
and
the location of your JRE.
CATALINA_HOME="/opt/ccfmaster/apache-tomcat-7.x.xx"
JAVA_HOME="/opt/java/jdk1.6.0_25"
-
Add a user named ccf to your system.
This is the user that runs the Tomcat server.
-
adduser -r -s /sbin/nologin ccf
To run the TeamForge connector server as a different user, make the appropriate changes to bin/CCFMaster.sh.
-
Log in as the newly created user and perform all installation steps as the ccf user. If
not, you need to make sure that the ccf user account has read and write access to the Tomcat
distribution directory as well as the connector home directory.
Tip: Since the ccf user's shell is set to /sbin/nologin, it is not possible to log in as the user. However, you can change to the ccf user with the command sudo -u ccf /bin/bash and then perform the installation. Alternatively, you can omit the -s /sbin/nologin option from the adduser command to create a user with the default login shell, and use the chsh command to change the shell to /sbin/nologin once installation is complete.
The service launcher script, bin/CCFMaster.sh, acts as a regular systemV init script and expects one argument to specify the action it should take. Possible actions include: