Software requirements for CollabNet TeamForge 16.3

This is the official list of software tested for compatibility with CollabNet TeamForge 16.3.

Software version requirements for 64 bit platform

Important: Do not customize your operating system installation. Select only the default packages list.
 

Red Hat Enterprise Linux 6.7 or 7.21 | CentOS 6.7 or 7.2

Database PostgreSQL3 9.3.6
Oracle DB** 12c
Oracle Client 12c
Java4 JDK 1.8.0_74
Wildfly/Jboss 8.2.0.Final
Tomcat 8.0.39
Lucene 4.4
Open LDAP 2.4.23
Quartz Job Scheduler 1.8.3
Browser Google Chrome 49
Mozilla Firefox 45
Microsoft IE 10 and 11
TeamForge user interfaces are best viewed at screen resolution of at least 1280 x 800 (or more) pixels.
yum package manager 3.2.29 or earlier versions

CollabNet TeamForge 16.3 supports the following software versions for integration

Black Duck Code Sight5 2.1.3
Review Board 2.0.11
GIT 2.4.2 or later
Subversion 1.8.16
Subversion Edge 5.0
CVS 1.11.x
ViewVC 1.1.24
Nexus 2.9.0 or later
Jira 6.3-7.1

Orchestrate

Orchestrate Installation requirements

CollabNet TeamForge 16.3 on Safari

CollabNet TeamForge 16.3 is tested for compatibility with Safari 6.0.5 (8536.30.1).

CollabNet TeamForge 16.3 on VMware and ESXi

The CollabNet TeamForge 16.3 is tested for compatibility with VMware Player 5.0 or later. For Windows and Linux versions supported by VMware Player 5.0 or later, see VMware Player Documentation.

The CollabNet TeamForge 16.3 is tested for compatibility with ESXi 5.1 or later.

PostgreSQL or Oracle?

PostgreSQL 9.3.6 is installed automatically when you install TeamForge 16.3. 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.3 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.6 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 2.0.11 was tested with PostgreSQL 9.3.6 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.

Microsoft applications

The following Microsoft applications have been tested with CollabNet TeamForge:

1 Red Hat Enterprise Linux servers must have access to the Red Hat Network or equivalent (satellite server, spacewalk, or RHN proxy).
3 PGTurant tool is available for quick pg_upgrade. See Upgrade PostgreSQL using PGTurant for more information.
4 For larger installs, the max JVM heap size should be increased to 1024MB (or larger), depending on available resources on the server.
5
Important: Black Duck Code Sight has no support for RHEL/CentOS 7.x. CollabNet recommends that you install or upgrade Black Duck Code Sight on a separate RHEL/CentOS 6.7 server if you choose to install or upgrade TeamForge 8.0 or later on a RHEL/CentOS 7.2 server.