Plan your installation

Before you install TeamForge 16.10, let's take a look at the product from a system administrator's perspective, so that you know exactly what you are getting into.


A TeamForge site consists of a core TeamForge application and several tightly integrated services that support it. In addition, you can integrate TeamForge with other third party applications such as Review Board, Nexus, Black Duck Code Sight, Git, and so on.


TeamForge supports integration with a wide array of third party applications such as Review Board, Git, Black Duck Code Sight, Nexus, Jira and so on. As a customer you may or may not always want (or have) all of TeamForge's supported integrated applications. It's also quite possible that some of the integrated applications may not always run on all the platforms supported by TeamForge.

To accommodate a wider audience, by default, TeamForge install and upgrade instructions include steps to integrate such third party applications with TeamForge. However, use your discretion to ignore and skip such steps if they are not relevant to your site. See TeamForge installation requirements to understand what it takes to run TeamForge 16.10 with integrations.

Important: To activate Black Duck Code Sight, a dedicated Black Duck Code Sight licensing key is required. To receive a Black Duck Code Sight license key, contact your CollabNet account manager, or send an email request to (A commercial TeamForge license is required, i.e. TeamForge "free option license" does not qualify).

Plan your TeamForge installation setup

TeamForge supports multiple options for customizing and expanding your site to fit your organization's unique use patterns. TeamForge 16.10 can run on RHEL/CentOS 6.8 or 7.2.

In the default setup, all services run on the same server as the main TeamForge application. But in practice, only the TeamForge application needs to run on the TeamForge application server. The other services can share that server or run on other servers, in almost any combination. When you distribute your services on multiple servers, you must do some configuration to handle communication among the services.

Install considerations for RHEL/CentOS 6.8 and 7.2

Though TeamForge 16.10 can run on RHEL/CentOS 6.8, it is a best practice to install TeamForge 16.10 on the most recent version of RHEL/CentOS supported by TeamForge, which in this case is RHEL/CentOS 7.2. However, choosing between RHEL/CentOS 6.8 and 7.2 depends on whether or not you need Black Duck Code Sight.

As Black Duck Code Sight 2.1.3 has no support for RHEL/CentOS 7.2, CollabNet recommends that you install Black Duck Code Sight on a separate RHEL/CentOS 6.8 server if you choose to install TeamForge 16.10 on a RHEL/CentOS 7.2 server.

In practice, it is always recommended to run Black Duck Code Sight on a separate server. Assess your own site's particular use patterns and resources to decide how to distribute your services, if at all. For example, if you anticipate heavy use of your site, you will want to consider running the site database, the source control service, or the reporting engine on separate hardware to help balance the load.

PostgreSQL or Oracle?

PostgreSQL 9.3.12 is installed automatically when you install TeamForge 16.10. If you intend to use Oracle, CollabNet recommends that you let the installer run its course, make sure things work normally, and then set up your Oracle database and switch over to it.

If you want to use Oracle as your database, consider the following points:
  • TeamForge 16.10 supports Oracle server 12c and Oracle client 12c.
  • Oracle express edition is not supported for both client and server.
  • Black Duck Code Sight (BDCS) 2.1.3 was tested with PostgreSQL 9.3.12 only. BDCS with Oracle was not tested. If you want BDCS, you may install BDCS on the PostgreSQL database that is installed by default during TeamForge installation.
  • Review Board was tested with PostgreSQL 9.3.12 only. Review Board with Oracle was not tested. Note that Review Board must be installed on the TeamForge application server and therefore uses the PostgreSQL database that is installed by default during TeamForge installation.
  • GIT integration works only with PostgreSQL. The Git integration will use PostgreSQL even if your TeamForge site uses Oracle.

The efficiency of your database can have an impact on your users' perception of the site's usability. If your site uses a PostgreSQL database (which is the default), you may want to consider tuning it to fit your specific circumstances. The default settings are intended for a small-to-medium site running on a single server. See What are the right PostgreSQL settings for my site? for recommendations from CollabNet's performance team on optimizing PostgreSQL for different conditions.

Choose your hardware

TeamForge can run on a wide range of hardware configurations.

For more information, see TeamForge installation requirements.

What's new in TeamForge 16.10

New TeamForge deploy framework

A new script, /opt/collabnet/teamforge/bin/teamforge, has been introduced in TeamForge 16.10. Use the teamforge script to start and stop services, bootstrap or migrate data and do much more. For more information, see The teamforge script

Use the teamforge script wherever applicable as it subsumes the functions of the following legacy TeamForge scripts:
  • collabnet

Review Board: TeamForge 16.10 supports Review Board

site-options.conf changes

Obsolete tokens:
    Note: SELinux is supported "by default" in TeamForge 16.10 (and later). As a result, SELINUX_ENABLED token is no longer required.


  • The and scripts are no longer available.
  • The script is no longer available.

End-of-life announcements/feature removals

TeamForge SOAP50 APIs and event handlers are no longer supported in TeamForge 16.10 and later. Instead, Customers can use the latest TeamForge SOAP/REST APIs.