Install TeamForge 8.0 with Oracle database on a separate server

In this option, we install the Oracle database (Operational database and Reports database) 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.

In this option, the following services run on the application server (we call this my.app.host).

TeamForge Application Server
ETL Server
GIT Integration Server
SCM Integration Server (Subversion and CVS)
Search Server (Indexer).

The following service runs on the database server. (We call this my.db.host)

Database Server (Operational DB and Reports DB)

Note: If either of the remote servers (the data server or the source code server) is not under your direct control, check with the Database Administrator to make sure that you can carry out these instructions on that server.

Note: For the ETL service to run as expected in a distributed TeamForge installation, all servers must have the same time zone.

Log on to the server as root user always.

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

Install Red Hat Enterprise Linux/CentOS 7.0 or later versions and log in as root.
- The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux. See Platform specification for TeamForge 8.0 for the full platform requirements.
- See the Red Hat installation guide for help.
Important: Don't customize your installation. Select only the default packages list.
Check your basic networking setup. See Set up networking for your TeamForge server for details.
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.
Upgrade the operating system packages.
- yum upgrade
Reboot the server.
- reboot
Disable postfix which is enabled by default on CentOS 7.0 profile.
- systemctl stop postfix
- systemctl disable postfix
Configure your TeamForge 8.0 installation repository. See TeamForge installation repository configuration for Red Hat/CentOS.
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
Rename the sample site configuration file from the installation package.
- cd /opt/collabnet/teamforge-installer/8.0.0.1
- cp conf/site-options-oracle.conf conf/site-options.conf
Note: The files site-options-small.conf, site-options-medium.conf and site-options-large.conf contain options to tune the performance of the TeamForge site. To tune your site's performance, you can look through these files for the load specifications they are intended for, and use the appropriate one for your site's requirements.
Set up your site's master configuration file.
- vi /opt/collabnet/teamforge-installer/8.0.0.1/conf/site-options.conf
1. Configure the HOST token.
```
HOST_localhost=app etl indexer subversion cvs
```
```
DOMAIN_localhost=my.app.domain.com
```
```
HOST_<my.db.host>=database datamart
```
2. Add 'gerrit' to the HOST_localhost token if you are installing GIT.
```
HOST_localhost=app etl indexer subversion cvs gerrit
```
3. Add 'binary' to the HOST_localhost token if you are installing Nexus.
```
HOST_localhost=app etl 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=oracle
```
```
DATABASE_USERNAME=sitedatabaseusername  
```
```
DATABASE_PASSWORD=sitedatabasepwd  
```
```
DATABASE_READ_ONLY_USER=sitedatabasereadonlyusername
```
```
DATABASE_READ_ONLY_PASSWORD=sitedatabasereadonlyuserpwd
```
```
DATABASE_NAME=sitedatabaseinstancename
```
```
REPORTS_DATABASE_USERNAME=reportingdatabaseusername
```
```
REPORTS_DATABASE_PASSWORD=reportingdatabasepwd
```
```
REPORTS_DATABASE_NAME=reportingdatabaseinstancename
```
```
REPORTS_DATABASE_READ_ONLY_USER=reportingreadonlyusername
```
```
REPORTS_DATABASE_READ_ONLY_PASSWORD=reportingreadonlyuserpwd
```
```
REPORTS_DATABASE_MAX_POOL_SIZE=30
```
```
DATABASE_SERVICE_NAME
```
```
REPORTS_DATABASE_SERVICE_NAME
```
  Tip: To find the value for the token DATABASE_SERVICE_NAME log in to your Oracle server and execute this command.
  - su - oracle
  - tnsping <database_name>
  Find the value of the SERVICE NAME in the output and use this value for the DATABASE_SERVICE_NAME in the site-options.conf file.
6. 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.
7. 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.
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. Ensure to set the token DEDICATED_INSTALL=true. This makes the installation process very simple as the TeamForge installer takes care of configuring the Apache and Postgres automatically.
14. Make sure that the following tokens have a value if ETL is enabled.
```
SOAP_ANONYMOUS_SHARED_SECRET
```
```
ETL_SOAP_SHARED_SECRET
```
15. Configure Black Duck Code Sight tokens if you are installing Black Duck Code Sight. See Black Duck Code Sight site-option tokens.
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.
Note: Perform this step in case your Oracle server version is not 11.2.0.1.
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>
Recreate the runtime environment.
- cd /opt/collabnet/teamforge-installer/8.0.0.1
- ./install.sh -r -I -V
Copy the Oracle datamart setup script from /opt/collabnet/teamforge/runtime/scripts to the /tmp directory of my.db.host.
- scp /opt/collabnet/teamforge/runtime/scripts/datamart-oracle-setup.sh <username>@<my.db.host>:/tmp

Do this on the database server - my.db.host

Install Red Hat Enterprise Linux/CentOS 7.0 or later versions and log in as root.
- The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux. See Platform specification for TeamForge 8.0 for the full platform requirements.
- See the Red Hat installation guide for help.
Important: Don't customize your installation. Select only the default packages list.
Upgrade the operating system packages.
- yum upgrade
Install Oracle 11G (R1 and R2).
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.
Copy the Oracle datamart setup script.
- mkdir /u1
- cp /tmp/datamart-oracle-setup.sh /u1
Log in as Oracle user and create the site database user and permissions. See Set up an Oracle database for help.
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 the following on the Black Duck Code Sight server - my.codesight.host.

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 this on the TeamForge Application Server (my.app.host)

Set up the initial site data (bootstrap).
- ./bootstrap-data.sh
Start TeamForge.
- /etc/init.d/collabnet start
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
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
Restart the collabnet services.
- /etc/init.d/collabnet restart
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.

Review Board: To install Review Board, see: Set up Review Board.
SELinux: To run TeamForge in SELinux enabled mode, see Set up SELinux.
Orchestrate: To install TeamForge Orchestrate, see TeamForge Orchestrate installation.
Cross-project life cycle metrics reporting in TeamForge 8.0

As the new reporting framework is expected to evolve over the next few releases, unlike TeamForge 7.2 or earlier versions, TeamForge 8.0 and later have the life cycle metric reports feature (that lets you create and add cross-project life cycle metric charts to project pages) deprecated and turned off by default. While the new reporting framework makes reporting effortless, expect it to cater only to intra-project reporting needs at the moment. If you still want cross-project life cycle metrics reporting in TeamForge 8.0, you must set this REPORTS_ENABLE_LIFECYCLE_METRICS token to true. See REPORTS_ENABLE_LIFECYCLE_METRICS for more information.

Git: To install Git integration, see Install Git integration on a separate server.