Install TeamForge 8.2: Black Duck Code Sight on a separate server on RHEL/CentOS

In this option, we install Black Duck Code Sight on a separate server and other services on the main application server.

Note: For the ETL service to run as expected in a distributed TeamForge installation, all servers must have the same time zone.
In this option, the following services run on the application server (we call this my.app.host).
Important: Black Duck Code Sight is not supported on RHEL/CentOS 7.2. CollabNet recommends that you install Black Duck Code Sight on a separate RHEL/CentOS 6.7 server.
The following service runs on the code sight server (we call this my.codesight.host).

Log on to the server as root user always.

Do this on the main TeamForge application server. We'll call this my.app.host.

  1. Install Red Hat Enterprise Linux/CentOS 7.2 and log in as root.
    Important: Don't customize your installation. Select only the default packages list.
  2. Create a file, /etc/security/limits.d/teamforge.conf, and make sure it has the following "nproc" and "nofile" settings.
    • vim /etc/security/limits.d/teamforge.conf
    • sf-admin soft nproc 10240
    • sf-admin hard nproc 10240
    • sf-admin hard nofile 65536
    • sf-admin soft nofile 65536
    • Save the file and reboot the server.
  3. Check your basic networking setup. See Set up networking for your TeamForge server for details.
  4. If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
    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 mode after completing the installation or upgrade.
  5. Configure your TeamForge installation repository.
  6. Install the following application packages.
    1. TeamForge: To install the TeamForge application packages run the following command:
      • yum install teamforge
    2. GIT: To install the GIT packages run the following command.
      • yum install teamforge-git
  7. Set up your site's master configuration file.
  8. Recreate the runtime environment.
    • cd /opt/collabnet/teamforge-installer/8.2.0.0
    • ./install.sh -r -I -V

Do this on the Black Duck Code Sight Server. We'll call this my.codesight.host.

  1. Install Red Hat Enterprise Linux/CentOS 6.7 and log in as root.
    Important: Don't customize your installation. Select only the default packages list.
  2. If the TeamForge server has SELinux enabled, disable it temporarily while installing or upgrading TeamForge.
    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
  3. Configure your TeamForge installation repository.
  4. Run the following command to install the Black Duck Code Sight packages.
    • yum install teamforge-codesearch
  5. Copy the site-options.conf file from the application server to the /opt/collabnet/teamforge-installer/8.2.0.0/conf directory of the Black Duck Code Sight server.
  6. Modify the host token settings on the site-options.conf file.
    Important: If you choose not to use the application server's site-options.conf file, then don't forget to copy the value of AUTO_DATA token from the application server.
    • HOST_my.codesight.host=codesearch
    • DOMAIN_my.codesight.host=my.codesight.domain.com
    • HOST_my.app.domain.com=app database datamart etl indexer subversion cvs gerrit
  7. Recreate the runtime environment.
    • cd /opt/collabnet/teamforge-installer/8.2.0.0
    • ./install.sh -r -I -V

Do the following on the application server - my.app.host

  1. Set up the initial site data (bootstrap).
    • cd /opt/collabnet/teamforge-installer/8.2.0.0
    • ./bootstrap-data.sh
  2. Start TeamForge.
    • /etc/init.d/collabnet start

Note: Gerrit is configured as part of the post installation tasks included in the post-install.py script. As a result, Gerrit's status would be Not configured during startup, which you can safely ignore.

  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?.
  2. Revoke the user permissions of the database and datamart users.
    • /opt/collabnet/teamforge/runtime/scripts/revoke-superuser-permission.py

Do this on my.codesight.host

  1. Install the Black Duck Code Sight license on the server where Black Duck Code Sight is installed. For more information, see Install the Black Duck Code Sight license.
  2. Run the TeamForge post installation script. For more information, see post-install.py.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py
  3. Restart the Black Duck Code Sight service.
    • /etc/init.d/collabnet restart tomcatcs

Do this on my.app.host

  1. Restart the collabnet services.
    • /etc/init.d/collabnet restart
  2. 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 into your site as the administrator. The value of the DOMAIN variable in the site-options.conf file is the URL to log into.
    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.