Install, Upgrade and Site Administration

Install/Upgrade best practices

  • See Platform specification for TeamForge 16.3 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 Set up networking for your TeamForge server.
  • 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 Back up and restore CollabNet TeamForge data 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: Why do ETL jobs fail post TeamForge upgrade?
  • 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

Before you begin

Platform information | Software requirements
How many servers are required to run TeamForge?
Plan your installation | Set up networking | Open ports
Installation FAQs

Single-server setup

All services on a single: RHEL/CentOS 7.2 server | RHEL/CentOS 6.7 server

Two-server setup

Refer to the following topics if you plan to install TeamForge 16.3 on a two-server distributed setup.

RHEL/CentOS 7.2
Install TeamForge 16.3 on a server and:
Database and Datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
SCM and Git on a separate server
Oracle database on a separate server
Git on a separate server

Three-server setup

Refer to the following topic if you plan to install TeamForge 16.3 on a three-server distributed setup.

Install TeamForge 16.3 on a server and Database and SCM on separate servers

Post installation

Supply license key: From TeamForge user interface | As a text file
Verify your TeamForge 16.3 installation
Maintain your site | Perform common administration tasks

Install TeamForge on VMware Player or VMware ESXi

Hardware and software requirements for CollabNet TeamForge 16.3 on a virtual machine
Install TeamForge 16.3 on: VMware Player | ESXi
Configure CollabNet TeamForge on VMware Player
Supply your TeamForge license key

Upgrade TeamForge

Before you begin

Platform information | Software requirements
How many servers are required to run TeamForge? | Should I upgrade to TeamForge 16.3 on a new server?
Plan your upgrade
Upgrade FAQs
Attention: TeamForge installer is being optimized quite a bit. It's likely that you might come across a lot of warning messages while upgrading to TeamForge 16.3 on the same hardware (when you run the yum install teamforge command). You can safely ignore such warning messages and proceed with the upgrade.

Single-server setup

You may choose to upgrade on the same hardware or new hardware. Refer to the topic that suits your needs.

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

Two-server setup

Refer to the following topics if you have TeamForge 8.2 running on a two-server distributed setup and are planning to upgrade to TeamForge 16.3 on the same hardware.

RHEL/CentOS 6.7
Upgrade TeamForge on a server and:
Database and datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
Git on a separate server
Oracle database on a separate server
RHEL/CentOS 7.2
Upgrade TeamForge on a server and:
Database and datamart on a separate server
Reporting services on a separate server
Black Duck Code Sight on a separate server
Git on a separate server
Oracle database on a separate server

Three-server setup

Refer to the following topics if you have TeamForge 8.2 running on a three-server distributed setup and are planning to upgrade to TeamForge 16.3 on the same hardware.

RHEL/CentOS 6.7
Upgrade TeamForge on a server and Database and SCM on separate servers
RHEL/CentOS 7.2
Upgrade TeamForge on a server and Database and SCM on separate servers

Install or upgrade Orchestrate

Installation requirements | Installation orientation
Install Orchestrate
Upgrade Orchestrate
Orchestrate integration adapters