Upgrade to TeamForge 8.0 with Oracle database services on a separate server

In this procedure, we assume that you are upgrading on the same server where your existing TeamForge 7.2 site is running.

Important: TeamForge 8.0 supports RHEL/CentOS 7.0. However, it also supports RHEL/CentOS 6.6 if you choose to upgrade on the same server that runs RHEL/CentOS 6.6.

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

TeamForge Application Server
Black Duck Code Sight Server
ETL Server
GIT Integration Server
Search Server (Indexer).
SCM Integration Server (Subversion and CVS)

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

Database Server (Operational DB and Reports DB)

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 Oracle Database Server - my.db.host

Make a dump file of your site database.
To back up the Oracle database, follow the Oracle backup procedure.

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

Stop the Apache server and the TeamForge application server.
- /etc/init.d/httpd stop
- /etc/init.d/collabnet stop

Back up the file system data.

Tip: /tmp in the following step is just an example. You can use any directory or partition that you prefer.

Make an archive file with the following data directories:

Directory	Contents
/opt/collabnet/teamforge/var	User-created data, such as artifact attachments
/svnroot	Subversion source code repositories.
/sf-svnroot	Subversion repository for branding data
/cvsroot	CVS source code repositories (not present on all sites)

mkdir -p /tmp/backup_dir
cp -Rpfv /svnroot /sf-svnroot /cvsroot /opt/collabnet/teamforge/var /tmp/backup_dir

If GIT integration is enabled, do the following:
- mkdir /tmp/backup_dir/gerrit
- cp -Rpfv /gitroot /tmp/backup_dir
- cp -Rpfv /opt/collabnet/gerrit/ /tmp/backup_dir/gerrit
Back up your SSH keys, if any.
Back up your SSL certificates and keys, if any.

If GIT is enabled, create a gerrit database dump file, for PostgreSQL upgrade.
- su - postgres
- /usr/bin/pg_dumpall > /var/lib/pgsql/9.2/backups/teamforge_gerrit_data_backup.dmp
- exit
Move the collabnet repository of the older version of TeamForge.
- mv /etc/yum.repos.d/collabnet-7.2.0.x.repo /etc/yum.repos.d/collabnet-7.2.0.x.repo.cn_backup
Note: Replace "x" with the appropriate patch release number if applicable.
Upgrade the operating system packages.
- yum upgrade
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.
Configure your TeamForge 8.0 installation repository. See TeamForge installation repository configuration for Red Hat/CentOS.
Uninstall the TeamForge CLI add-on.
- cd /opt/collabnet/teamforge/add-ons/teamforge_cli_server
- ./install --uninstall
- yum erase teamforge_cli_server
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
3. Black Duck Code Sight: To install the Black Duck Code Sight packages run the following command:
  - yum install teamforge-codesearch
In the site-options.conf file, make sure you do the following.
Note: Back up your site-options.conf file before making any changes.
- vi /opt/collabnet/teamforge-installer/8.0.0.1/conf/site-options.conf
1. Update the host name and domain name, if required.
```
HOST_localhost=app etl indexer subversion cvs
```
```
HOST_my.db.host=database datamart 
```
```
DOMAIN_localhost=my.app.domain.com
```
2. Add "gerrit" to the HOST_localhost token if you are installing GIT.
```
HOST_localhost=app etl indexer subversion cvs gerrit
```
3. Add "codesearch" to the HOST_localhost token if you are installing Black Duck Code Sight.
```
HOST_localhost=app etl indexer subversion cvs gerrit codesearch
```
4. Add "binary" to the HOST_localhost token if you are installing Nexus.
```
HOST_localhost=app etl indexer subversion cvs gerrit codesearch binary
```
5. 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.
6. 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.
7. If your site is running in SSL mode (SSL=on), add the following java runtime property to the JBOSS_JAVA_OPTS token.
```
JBOSS_JAVA_OPTS=-Xms1536m -Xmx1536m -XX:MaxPermSize=512m -server -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -verbose:gc -XX:+
PrintGCTimeStamps -XX:+PrintGCDetails -Djsse.enableSNIExtension=false -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000
```
8. 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.
9. 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.
10. Ensure to set the token DEDICATED_INSTALL=true.
11. Include the list of non-expiring TeamForge user accounts (password never expires).
```
USERS_WITH_NO_EXPIRY_PASSWORD=admin,nobody,system,scmviewer,scmadmin
```
12. Make sure that the following tokens have a value if ETL is enabled.
```
SOAP_ANONYMOUS_SHARED_SECRET
```
```
ETL_SOAP_SHARED_SECRET
```
13. Configure Black Duck Code Sight tokens. See Black Duck Code Sight site-option tokens.
14. If you have LDAP set up for external authentication, you must set the “REQUIRE_USER_PASSWORD_CHANGE” site options token to false.
15. If you are installing TeamForge through disconnected media, set the token HELP_AVAILABILITY=local.
16. Ensure to set the token SELINUX_SETUP=false.
17. Save the site-options.conf file.
Download the corresponding version of the Oracle client from http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html
- 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
Update the file permissions on your site's data.
- /opt/collabnet/teamforge/runtime/scripts/fix_data_permissions.sh
Note: This process can take a long time for sites with a lot of data.
Convert your site data to work with TeamForge 8.0.
Tip: Before you kick off the data migration, do the following:
- Use the /etc/init.d/collabnet status command to make sure the JBoss, Tomcat and Tomcatcs services are stopped.
- If any of the trackers in your project already contains a field with the name team, conflict may arise while running the migrate.py script. This is because of the inclusion of the Team feature in TeamForge 8.0. To prevent this conflict, follow the steps given in FAQ on troubleshooting.
- /opt/collabnet/teamforge/runtime/scripts/migrate.py
The migrate.py script locates the existing site data and modifies it as needed.
This includes configuration data for LDAP and the James mail server. Any modifications that you have applied to these components on your old site are reproduced on your upgraded TeamForge 8.0 site.
Start TeamForge.
- /etc/init.d/collabnet start
If you have CVS integrations, synchronize permissions post upgrade. See, Synchronize TeamForge source control integrations.
Run the TeamForge post installation script. For more information, see post-install.py.
- /opt/collabnet/teamforge/runtime/scripts/post-install.py
If you have installed Black Duck Code Sight, then install the license for Black Duck Code Sight. For more information, see Install the Black Duck Code Sight license.
Run the svn_cache.sh script.
- cd /opt/collabnet/teamforge/runtime/scripts/codesearch/
- ./svn_cache.sh <Repository Base URL Path of the SCM Integration Server>
Provide a repository base URL path of the SCM integration server, for example, "http://myint.box.net/svn/repos", where myint.box is the server with the SCM integration server.

In addition, if you add a new integration server at some point later, you must run this svn_cache.sh script, (after creating the new integration server), on the TeamForge application server.
Restart the collabnet services.
- /etc/init.d/collabnet restart
Apply the finishing touches and make sure everything is running smoothly after upgrading to TeamForge 8.0.
Important: Do not delete the teamforge-installer/8.0.0.1 directory. You will need it for future maintenance and upgrades.
1. Log into your site as the administrator.
2. If your site has custom branding, verify that your branding changes still work as intended. See Customize anything on your site.
3. Let your site's users know they've been upgraded. See Communicate with all site users at once.

ETL initial load jobs: Run the ETL initial load jobs. See ETL initial load jobs.
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.