Install TeamForge 17.4: All services on a single RHEL/CentOS 7.3 server

The easiest way to install TeamForge is to install it on a single server, dedicated to TeamForge taking the default configuration settings.

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 RPM package: 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. Note: If the Red Hat Enterprise Linux/CentOS installation DVD is mounted already, skip the following instructions. If not, mount the DVD.
      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. Set up your site's master configuration file.
   • vi /opt/collabnet/teamforge/etc/site-options.conf
   1. Configure the services and domain name tokens.
      Note: cliserver and reviewboard-adapter are the new services added in TeamForge 17.4.

      localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion 
      cvs codesearch eventq mongodb redis rabbitmq cliserver

      localhost:PUBLIC_FQDN=my.app.domain.com

   2. Add Gerrit identifiers if you are installing Git.

      localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion 
      cvs codesearch eventq mongodb redis rabbitmq cliserver gerrit gerrit-database

   3. Add Binary identifiers if you are installing Nexus.

      localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion 
      cvs codesearch eventq mongodb redis rabbitmq cliserver gerrit gerrit-database binary binary-database

   4. Add Review Board identifiers if you are installing Review Board.

      localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion 
      cvs codesearch cliserver eventq mongodb redis rabbitmq  gerrit gerrit-database binary binary-database 
      reviewboard reviewboard-database reviewboard-adapter

   5. Attention: SSL is enabled by default and a self-signed certificate is auto-generated. Use the following tokens to adjust this behavior. 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.

      SSL_CERT_FILE=

      SSL_KEY_FILE=

      SSL_CHAIN_FILE=

      Important: All SSL certificates including self-signed certificates are added automatically.
   6. TeamForge 7.1 and later support automatic password creation. See AUTO_DATA for more information.
   7. 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.
   8. 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__}
   9. If you have LDAP set up for external authentication, you must set the REQUIRE_USER_PASSWORD_CHANGE site options token to false.
   10. 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?
   11. Save the site-options.conf file.
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.

8. 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
9. Restart TeamForge.
   • setenforce 1
   • /opt/collabnet/teamforge/bin/teamforge restart
10. 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.