Install, Upgrade and Site Administration

Install/Upgrade best practices

See and understand the software and hardware requirements.
See the CollabNet TeamForge 16.3 release notes and know more about the TeamForge version you want to install or upgrade to.
Plan your installation or upgrade. See Plan your installation | Plan your upgrade
Do not customize your operating system installation. Select only the default packages list.
Verify your basic networking setup before installing or upgrading TeamForge. See .
Generate SSL certificates, if required, and keep them handy. See Generate SSL certificates.
If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
Create a file, /etc/security/limits.d/teamforge.conf, and make sure it has the following "nproc" and "nofile" settings.
- vim /etc/security/limits.d/teamforge.conf
- sf-admin soft nproc 10240
- sf-admin hard nproc 10240
- sf-admin hard nofile 65536
- sf-admin soft nofile 65536
- Save the file and reboot the server.
You must have no tasks in progress while uninstalling the CLI add-ons during the upgrade process.
Look for new or modified site-options.conf tokens and update your site-options.conf file as required during the upgrade process.
During upgrades, refer to the TeamForge 8.2 site-options.conf file and make sure that the TeamForge 16.3 site-options.conf file inherits all the required tokens.
CAUTION:
You run the risk of missing out on newly added (or removed) site option tokens if you keep reusing your site-options.conf file from an older TeamForge version on newer versions. See Site options change log for more information.
Do not manually modify TeamForge-managed site option tokens such as the AUTO_DATA token. See AUTO_DATA for more information.
No backup is required for same hardware upgrades. However, you can create a backup as a precaution. See to learn more about backing up TeamForge database and file system.
Always use compatible JDBC drivers meant for specific database versions. See JDBC Drivers Reference for more information. Also see:
You can run the initial load job any time after the site is upgraded to TeamForge 16.3. We recommend that you run it before you hand over the site to the users. For more information, see When do I run the initial load job?

Install TeamForge

Upgrade TeamForge

Upgrade on same hardware	Upgrade on new hardware
From 8.2 to 16.3 on: \|	From 8.2 to 16.3 on:
From 7.2 to 16.3 on RHEL/CentOS

RHEL/CentOS 7.2
Upgrade TeamForge on a server and:

Reporting services on a separate server


Oracle database on a separate server

Install or upgrade Orchestrate

Install, Upgrade and Site Administration

Install/Upgrade best practices

Install TeamForge

Before you begin

Single-server setup

Two-server setup

Three-server setup

Post installation

Install TeamForge on VMware Player or VMware ESXi

Upgrade TeamForge

Before you begin

Single-server setup

Two-server setup

Three-server setup

Install or upgrade Orchestrate