Install TeamForge, Oracle database, and EventQ on Three separate servers

Three-server distributed setup with TeamForge, Oracle Database (including Datamart) and EventQ on three separate servers.

Dos and Don'ts

Check this list before installing or upgrading TeamForge.

Three Server Setup

Here's how the services are distributed across three separate RHEL/CentOS 7.3 servers.
Services TeamForge Application Server (server-01) EventQ Server (server-02) Database Server (server-03)
ctfcore
   
mail
   
search
   
codesearch
   
etl
   
gerrit
   
gerrit-database
   
reviewboard
   
reviewboard-database
   
reviewboard-adapter
   
subversion
   
cvs
   
binary
   
binary-database
   
cliserver
   
eventq  
 
mongodb  
 
redis  
 
rabbitmq  
 
ctfcore-database    
ctfcore-datamart    

Do this step by step on TeamForge Application Server (server-01)

  1. Install Red Hat Enterprise Linux/CentOS 7.3 and log on as root.

    The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux.

    See the Red Hat installation guide for help.

  2. Check your basic networking setup. See Set up Networking for more information.
  3. If the TeamForge server has SELinux enabled, run it in 'permissive' mode temporarily while installing or upgrading TeamForge.

    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
  4. Configure your TeamForge installation repository.
    • TeamForge installation repository configuration for sites with internet access
    1. Contact the CollabNet Support and download the TeamForge 17.4 installation repository package to /tmp.
    2. Install the repository package.
      • yum install -y /tmp/collabnet-teamforge-repo-17.4-1.noarch.rpm
    3. Refresh your repository cache.
      • yum clean all
    • TeamForge installation repository configuration for sites without internet access
    1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 17.4 disconnected installation and save it in /tmp.
      • Red Hat Enterprise Linux/CentOS 7.3 64 bit: CTF-Disconnected-media-17.4.824-110.rhel7.x86_64.rpm
        Note: In addition to the above CentOS 7.3 64 bit RPM package, you must get the following CentOS 7.3 compatibility RPM, which is required for TeamForge 17.4 disconnected media installation on CentOS 7.3 profile: compat-ctf-dc-media-1.1-1.el7.noarch.rpm.
    2. Unpack the disconnected installation package.
      • rpm -ivh <package-name>
    3. Unpack the compat-ctf-dc-media-1.1-1.el7.noarch.rpm package if you are installing TeamForge 17.4 on CentOS 7.3.
      • rpm -ivh compat-ctf-dc-media-1.1-1.el7.noarch.rpm
    4. If not mounted already, mount the Red Hat Enterprise Linux/CentOS installation DVD. The DVD contains the necessary software and utilities required for installing TeamForge without internet access.

      In the following commands, replace "cdrom" with the identifier for your server's CD/DVD drive, if necessary.

      • cd /media/
      • mkdir cdrom
      • mount /dev/cdrom ./cdrom/

      If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.

    5. Create a yum configuration file that points to the Red Hat Enterprise Linux/CentOS installation DVD.
      • vi /etc/yum.repos.d/cdrom.repo
      Here's a sample yum configuration file.
      [RHEL-CDROM] 
name=RHEL CDRom 			
baseurl=file:///media/cdrom/Server/
gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release 
enabled=1
gpgcheck=0
    6. Verify your yum configuration files.
      • yum list httpd
      • yum list apr
  5. Install the TeamForge application packages.
    • yum install teamforge
  6. Rename the sample site configuration file from the installation package.
    • cd /opt/collabnet/teamforge/etc/
    • cp site-options-oracle.conf site-options.conf
  7. Set up your site's master configuration file.
    • vi /opt/collabnet/teamforge/etc/site-options.conf

    host: SERVICES Token

    Note: cliserver and reviewboard-adapter are the new services added in TeamForge 17.4.
    • server-01:SERVICES=ctfcore mail etl search subversion cvs codesearch cliserver gerrit 
gerrit-database binary binary-database reviewboard reviewboard-database reviewboard-adapter
    • server-02:SERVICES=eventq mongodb redis rabbitmq
    • server-03:SERVICES=ctfcore-database ctfcore-datamart
    Note: You may remove the identifiers of components you do not want. For example, remove binary and binary-database if you are not planning to install binary repository managers such as Nexus. See TeamForge services for more information.

    host: PUBLIC_FQDN Token

    server-01:PUBLIC_FQDN=my.app.domain.com

    Save the site-options.conf file.

    For further customization of your site configuration:

    SSL Tokens

    SSL is enabled by default and a self-signed certificate is auto-generated. Use the following tokens to adjust this behavior.
    SSL_CERT_FILE=
    SSL_KEY_FILE=
    SSL_CHAIN_FILE=
    • To generate the SSL certificates, see Generate SSL certificates.
    • Have the custom SSL certificate and private key for custom SSL certificate in place and provide their absolute paths in these tokens. SSL_CHAIN_FILE (intermediate certificate) is optional.
    • All SSL certificates including self-signed certificates are added automatically.

    Password Tokens

    • TeamForge 7.1 and later support automatic password creation. See AUTO_DATA for more information.
    • If the token REQUIRE_PASSWORD_SECURITY is enabled, then set a value for the token, PASSWORD_CONTROL_EFFECTIVE_DATE.
      Warning: 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.
    • 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__}
    • If you have LDAP set up for external authentication, you must set the “REQUIRE_USER_PASSWORD_CHANGE” site options token to false.

    PostgreSQL Tokens and Settings

  8. Download the corresponding version of Oracle client from http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html and run the following command:
    • yum localinstall <path to oracle client rpm>
  9. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision
    Note:

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

    TeamForge 17.4 (and later) installer expects the system locale to be LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.

Do this step by step on Oracle Database Server (server-03)

  1. Install Red Hat Enterprise Linux/CentOS 7.3 and log on as root.

    The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux.

    See the Red Hat installation guide for help.

  2. Check your basic networking setup. See Set up Networking for more information.
  3. Install Oracle 12c.
    Note: Make sure your database uses UTF8 or AL32UTF8 encoding. This is needed to support users in Asian languages. See this Oracle knowledge base article.
  4. Log on to the Oracle Database Server as a system administrator with 'SYSDG' privilege and run the following query.
    • alter system set parallel_threads_per_cpu=4;

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

  1. Copy the Oracle Datamart setup script from /opt/collabnet/teamforge/runtime/scripts/ to the /tmp directory of server-03.
    • scp /opt/collabnet/teamforge/runtime/scripts/datamart-oracle-setup.sh <username>@<server-03>:/tmp

Do this step on Oracle Database Server (server-03)

  1. Copy the Oracle Datamart setup script.
    • mkdir /u1
    • cp /tmp/datamart-oracle-setup.sh /u1
  2. Log in as Oracle user and create the site database user and permissions. See Set up an Oracle database for help.
  3. Create the reporting user and schema.
    Note: Skip this step if you have already set up the datamart setup in the Oracle database. Your responses to the script's prompts must match the values of the equivalent variables in the site-options.conf file on my.app.server.
    • cd /u1
    • sh datamart-oracle-setup.sh

Do this step by step on EventQ server (server-02)

  1. Install Red Hat Enterprise Linux/CentOS 7.3 and log on as root.

    The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux.

    See the Red Hat installation guide for help.

  2. Check your basic networking setup. See Set up Networking for more information.
  3. If the TeamForge server has SELinux enabled, run it in 'permissive' mode temporarily while installing or upgrading TeamForge.

    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
  4. Configure your TeamForge installation repository.

    TeamForge installation repository configuration for sites with internet access

    1. Contact the CollabNet Support and download the TeamForge 17.4 installation repository package to /tmp.
    2. Install the repository package.
      • yum install -y /tmp/collabnet-teamforge-repo-17.4-1.noarch.rpm
    3. Refresh your repository cache.
      • yum clean all

    TeamForge installation repository configuration for sites without internet access

    1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 17.4 disconnected installation and save it in /tmp.
      • Red Hat Enterprise Linux/CentOS 7.3 64 bit: CTF-Disconnected-media-17.4.824-110.rhel7.x86_64.rpm
      • In addition to the above CentOS 7.3 64 bit RPM package, you must get the following CentOS 7.3 compatibility RPM, which is required for TeamForge 17.4 disconnected media installation on CentOS 7.3 profile: compat-ctf-dc-media-1.1-1.el7.noarch.rpm.
    2. Unpack the disconnected installation package.
      • rpm -ivh <package-name>
    3. Unpack the compat-ctf-dc-media-1.1-1.el7.noarch.rpm package if you are installing TeamForge 17.4 on CentOS 7.3.
      • rpm -ivh compat-ctf-dc-media-1.1-1.el7.noarch.rpm
    4. If not mounted already, mount the Red Hat Enterprise Linux/CentOS installation DVD.

      The DVD contains the necessary software and utilities required for installing TeamForge without internet access. In the following commands, replace "cdrom" with the identifier for your server's CD/DVD drive, if necessary.

      • cd /media/
      • mkdir cdrom
      • mount /dev/cdrom ./cdrom/

      If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.

    5. Create a yum configuration file that points to the Red Hat Enterprise Linux/CentOS installation DVD.
      • vi /etc/yum.repos.d/cdrom.repo
      Here's a sample yum configuration file.
      [RHEL-CDROM] 
name=RHEL CDRom 			
baseurl=file:///media/cdrom/Server/
gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release 
enabled=1
gpgcheck=0
    6. Verify your yum configuration files.
      • yum list httpd
      • yum list apr
  5. Install the EventQ packages.
    • yum install teamforge-eventq
  6. Copy the site-options.conf file from the TeamForge Application Server (server-01) to the EventQ Server's /opt/collabnet/teamforge/etc/ directory.
  7. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision
    Note:

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

    TeamForge 17.4 (and later) installer expects the system locale to be LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.

Do this step by step on TeamForge Application Server (server-01)

  1. Run the TeamForge post installation script. For more information, see post-install.py.
    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.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py
  2. Restart TeamForge.
    • setenforce 1
    • /opt/collabnet/teamforge/bin/teamforge restart
  3. Verify TeamForge installation.
    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.

Post Installation Tasks

Parent topic: Install TeamForge
Related concepts
TeamForge installation/upgrade/configuration/administration FAQs