Install TeamForge, SCM and Git integration, and EventQ on separate servers

Three-server distributed setup with TeamForge (including Database and Datamart), SCM (Subversion and CVS) and Git, and EventQ services installed on RHEL/CentOS 7.2 servers.

The following table shows the distribution of services on different servers.
App Server: server-01 SCM and Git Integration Server: server-03
TeamForge Application Server SCM Integration Server (Subversion and CVS)
Database Server (Operational DB and Reports DB) Git Integration Server
ETL Server  
Search Server (Indexer)  
EventQ Server: server-02
TeamForge EventQ Server (App, MongoDB and RabbitMQ)
Attention: As Black Duck Code Sight 2.1.3 has no support for RHEL/CentOS 7.2, CollabNet recommends you install Black Duck Code Sight on a separate RHEL/CentOS 6.8 server.
Note: For the ETL service to run as expected in a distributed TeamForge installation, all servers must have the same time zone.
Attention: Installing or upgrading TeamForge needs root privileges. You must log on as root or use a root shell to install or upgrade TeamForge.

Do this on the TeamForge Application Server (server-01)

  1. Install Red Hat Enterprise Linux/CentOS 7.2 and log in as root.
  2. Check your basic networking setup. See Set up networking for your TeamForge server for details.
  3. If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
    Important: If you have SELinux in "enforcing" mode, you must either disable SELinux or switch to "Permissive" mode (recommended) before running the /opt/collabnet/teamforge/bin/teamforge provision command. TeamForge create runtime fails otherwise.
    1. Verify if SELinux is running in enforcing mode.
      • getenforce
    2. If the output of the getenforce command is "Permissive", continue with the next step. If not, run the following command to bring it to 'Permissive' mode.
      • setenforce 0
    See Set up SELinux to have TeamForge run in SELinux enforcing mode after completing the installation or upgrade.
  4. Configure your TeamForge installation repository.
  5. Install the following application packages.
    1. TeamForge: To install the TeamForge application packages run the following command:
      • yum install teamforge
  6. Set up your site's master configuration file.
  7. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision

    The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "Yes" or "No" to proceed. For more information, see The teamforge script.

Do this on the SCM and Git Integration Server (server-03)

  1. Install Red Hat Enterprise Linux/CentOS 7.2 and log in as root.
  2. Check your basic networking setup. See Set up networking for your TeamForge server for details.
  3. If the TeamForge server has SELinux enabled, disable it temporarily while installing or upgrading TeamForge. TeamForge create runtime fails otherwise.
    1. Verify if SELinux is running in enforcing mode.
      • getenforce
    2. If the output of the getenforce command is either "Disabled" or "Permissive", SELinux is already disabled.
    3. If not disabled, run the following command to disable SELinux.
      • setenforce 0
  4. Configure your TeamForge installation repository.
  5. Install the TeamForge SCM and Git packages.
    • yum install teamforge-scm teamforge-git
  6. Copy the site-options.conf file from the TeamForge Application Server to the SCM and Git Integration Server's /opt/collabnet/teamforge/etc/ directory.
  7. Modify the host token settings on the site-options.conf file.
    HOST_server-03=subversion cvs gerrit
    DOMAIN_server-03=my.scmandgit.domain.com
    HOST_my.app.domain.com=app database datamart etl indexer
  8. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision

    The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "Yes" or "No" to proceed. For more information, see The teamforge script.

Do this on the TeamForge Application Server (server-01)

  1. Important: If the token REQUIRE_USER_PASSWORD_CHANGE is set to true, login to TeamForge user interface, change the admin password and then run the post-install.py script.
    Run the TeamForge post installation script. For more information, see post-install.py.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py
    Note: In case you face any GIT-related issues while running the post-install.py script, see Post install fails for Git. What should I do?.

Do this on the SCM and Git Integration Server (server-03)

  1. Run the TeamForge post installation script. For more information, see post-install.py.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py

Do this on the TeamForge Application Server (server-01)

  1. Restart TeamForge.
    • /opt/collabnet/teamforge/bin/teamforge restart

Do this on the EventQ server (server-02)

  1. Install EventQ. See EventQ installation walk-through

Do this on the Application Server (server-01)

  1. Apply some finishing touches and make sure everything is running smoothly.
    1. Reboot the server and make sure all services come up automatically at startup.
    2. Log on to the TeamForge web application using the default Admin credentials.
      • Username: "admin"
      • Password: "admin"
    3. Create a sample project. See Create a TeamForge project.
    4. Write a welcome message to your site's users. See Create a site-wide broadcast.