Install TeamForge 8.0 with Reporting services on a separate server

In this option, we install the datamart (Reporting database) and ETL on a separate server and other services on the main application server. If you want Black Duck Code Sight, you must install it on a separate RHEL/CentOS 6.6 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). The following service runs on the database server. (We call this my.reports.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.0 or later versions and log in as root.
    Important: Don't customize your installation. Select only the default packages list.
  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.
    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, run the following command to disable SELinux.
      • setenforce 0
    See Set up SELinux to have TeamForge run in SELinux mode after completing the installation or upgrade.
  4. Upgrade the operating system packages.
    • yum upgrade
  5. Reboot the server.
    • reboot
  6. Disable postfix which is enabled by default on CentOS 7.0 profile.
    • systemctl stop postfix
    • systemctl disable postfix
  7. Configure your TeamForge 8.0 installation repository. See TeamForge installation repository configuration for Red Hat/CentOS.
  8. Install the following application packages.
    1. TeamForge: To install the TeamForge application packages run the following command:
      • yum install teamforge-app teamforge-database teamforge-scm teamforge-binary
    2. GIT: To install the GIT packages run the following command.
      • yum install teamforge-git
  9. Set up your site's master configuration file.
    • vi /opt/collabnet/teamforge-installer/8.0.0.1/conf/site-options.conf
    1. Identify the servers and services running on them. 
      HOST_localhost=app database indexer subversion cvs
      DOMAIN_localhost=my.app.domain.com
      HOST_my.reports.domain.com=datamart etl
    2. Add 'gerrit' to the HOST_localhost token if you are installing Git. 
      HOST_localhost=app database indexer subversion cvs  gerrit
    3. Add 'binary' to the HOST_localhost token if you are installing Nexus. 
      HOST_localhost=app database indexer subversion cvs gerrit binary
    4. Configure the following token if you are installing Black Duck Code Sight. 
      HOST_my.codesight.domain.com=codesearch
    5. Configure the database and datamart settings.
      Note: For more information about configuring variables, see site-options.conf
      DATABASE_TYPE=postgresql
      DATABASE_USERNAME=ctfuser
      DATABASE_NAME=ctfdb
      DATABASE_READ_ONLY_USER=ctfrouser
      REPORTS_DATABASE_USERNAME=ctfrptuser
      REPORTS_DATABASE_NAME=ctfrptdb
      REPORTS_DATABASE_READ_ONLY_USER=ctfrptrouser
      REPORTS_DATABASE_MAX_POOL_SIZE=30
      Note: The database name and user name values are arbitrary alphanumeric strings.
    6. TeamForge 7.1 and later support automatic password creation. See AUTO_DATA for more information.
    7. Password Obfuscation

      The password obfuscation is enabled by default. As a result, all password-related tokens are encrypted in all the TeamForge configuration files.

      Restriction: The password-related tokens cannot contain the following characters in the site-options.conf file: $<>/\'"`
      • To disable password obfuscation, set OBFUSCATION_ENABLED=false.
      • To configure the obfuscation key, set OBFUSCATION_KEY=<Any AlphaNumeric value with length >= 8 bytes>. The default value of OBFUSCATION_KEY token is XSJt43wN.
    8. Turn on the SSL for your site by editing the relevant variables in the site-options.conf file. To generate the SSL certificates, see Generate SSL certificates. 
      • SSL=on
      • SSL_CERT_FILE
      • SSL_KEY_FILE
      • SSL_CA_CERT_FILE
      • SSL_CHAIN_FILE
      Note: The SSL_CA_CERT_FILE and SSL_CHAIN_FILE are optional.
    9. If the token REQUIRE_PASSWORD_SECURITY is enabled, then set a value for the token, PASSWORD_CONTROL_EFFECTIVE_DATE.
      CAUTION:
      The Password Control Kit (PCK) disables, deletes or expires user accounts that don't meet the password security requirements starting from the date set for the PASSWORD_CONTROL_EFFECTIVE_DATE token. If a date is not set, the PCK disables, deletes or expires user accounts immediately. See PASSWORD_CONTROL_EFFECTIVE_DATE for more information.
    10. Include the SCM_DEFAULT_SHARED_SECRET token in the site-options.conf file of the primary TeamForge server and provide it with a value of 16-24 characters. Remember to use the same key in the external SCM integration server also.
    11. If the token REQUIRE_RANDOM_ADMIN_PASSWORD is already set to true, then set the token ADMIN_EMAIL with a valid email address. ADMIN_EMAIL=root@{__APPLICATION_HOST__}
    12. If you have LDAP set up for external authentication, you must set the “REQUIRE_USER_PASSWORD_CHANGE” site options token to false.
    13. Make sure that the following tokens have a value if ETL is enabled. 
      SOAP_ANONYMOUS_SHARED_SECRET
      ETL_SOAP_SHARED_SECRET
    14. Configure Black Duck Code Sight tokens if you are installing Black Duck Code Sight. See Black Duck Code Sight site-option tokens.
    15. To enable the history protection feature of TeamForge Git integration, set the GERRIT_FORCE_HISTORY_PROTECTION=true. For more information, see GERRIT_FORCE_HISTORY_PROTECTION.
    16. If you are installing TeamForge through disconnected media, set the token HELP_AVAILABILITY=local.
    17. Ensure to set the token SELINUX_SETUP=false.
    18. Make sure the PostgreSQL tokens in the site-options.conf file are set as recommended in the following topic: What are the right PostgreSQL settings for my site?
    19. Save the site-options.conf file.
  10. Recreate the runtime environment.
    • cd /opt/collabnet/teamforge-installer/8.0.0.1
    • ./install.sh -r -I -V

Do this on the reporting server - my.reports.host

  1. Install Red Hat Enterprise Linux/CentOS 7.0 or later versions and log in as root.
    Important: Don't customize your installation. Select only the default packages list.
  2. Upgrade the operating system packages.
    • yum upgrade
  3. Check your basic networking setup. See Set up networking for your TeamForge server for details.
  4. 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
  5. Configure your TeamForge 8.0 installation repository. See TeamForge installation repository configuration for Red Hat/CentOS.
  6. Run the following command to install the Reporting packages.
    • yum install teamforge-database teamforge-etl
  7. Copy the site-options.conf file from the application server to the reporting server in the directory /opt/collabnet/teamforge-installer/8.0.0.1/conf
  8. Modify the host token settings on the site-options.conf file.
    Note: 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.reports.host=datamart etl
    Note: 'HOST_my.reports.host' is just an example. As you are installing reporting services on a separate server, do not use 'HOST_localhost'. Use 'HOST_<valid host name>' instead.
    DOMAIN_my.reports.host=my.reports.domain.com
    HOST_my.app.domain.com=app database indexer subversion cvs gerrit
  9. Recreate the runtime environment.
    • cd /opt/collabnet/teamforge-installer/8.0.0.1
    • ./install.sh -r -I -V

Do the following on the Black Duck Code Sight server - my.codesight.host.

  1. Set up Black Duck Code Sight on a separate server. See Install Black Duck Code Sight on a separate RHEL/CentOS 6.6 server.

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

  1. Set up the initial site data (bootstrap).
    • cd /opt/collabnet/teamforge-installer/8.0.0.1
    • ./bootstrap-data.sh
  2. Start TeamForge.
    • /etc/init.d/collabnet start
  3. By default, firewall is enabled on CentOS 7.0 profile and needs to be configured, without which no external access is possible.
    • firewall-cmd --zone=public --add-service=http --permanent
    • firewall-cmd --zone=public --add-service=https --permanent
    • firewall-cmd --reload
  4. Note: 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
  5. Revoke the super user permissions of database and datamart users.
    • /opt/collabnet/teamforge/runtime/scripts/revoke-superuser-permission.py
  6. Restart the collabnet services.
    • /etc/init.d/collabnet restart
  7. 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.
Parent topic: Install CollabNet TeamForge 8.0 on Red Hat/CentOS
Related concepts
TeamForge installation/upgrade/configuration/administration FAQs