TeamForge installation requirements

Here's what it takes to install and run TeamForge.

Hardware requirements
The following table lists the CPU, RAM and JVM Heap Size recommendations for Small, Medium, Large and Extra-large sites.
  Small Medium Large X-Large
Users 100 500 1000-5000 10000+
CPU Octa-core 12-core > 12-core > 16-core
RAM 16GB 24GB 32GB 32GB
Jboss JVM Heap Size 1.5GB 3GB 6GB > 8GB
Elasticsearch JVM Heap Size* 2GB 2GB 2GB 2GB
200 GB (or more) hard drive #
The following table highlights the factors that can impact TeamForge performance. Numbers are indicative. Anything more than the prescribed numbers may impact the performance.
  Small Medium Large X-Large
Artifacts 15000 70000 100000 100000
Flex Fields 25 50 100 100
Projects 20 80 500 500
Integrations 0-1 0-2 0-2 0-2
Integrated Applications 0-2 0-3 3+ 3+
Important: On Medium, Large and X-Large sites, it is highly recommended that you install the TeamForge Application, Database and SCM services on separate 64-bit servers based on the usage pattern.
Software requirements
Important: Do not customize your operating system installation. Select only the default packages list.
Operating system RHEL 6.9 or 7.4 1 (64 bit) | CentOS 6.9 or 7.4 (64 bit)
Browser Google Chrome 59
Mozilla Firefox 54
Microsoft IE 11
Safari 10.1.
TeamForge user interfaces are best viewed at screen resolution of at least 1280 x 800 (or more) pixels.
Database PostgreSQL 9.6.5 is installed by default when you install TeamForge 17.11. However, you can use Oracle if you want to. See PostgreSQL or Oracle for more information.
Oracle Server 12c
Oracle Client 12c
Java 2 Jboss/Wildfly 10.1.0.Final
JRE 1.8.0_131
Tomcat 8.0.46
Yum package manager 3.2.29 or earlier versions
TeamForge 17.11 supports the following software versions for integration
Product Version (s) Supported Integrations Supported

JIRA Software

6.3 – 6.4.14

TeamForge Associations Add-on 2.11-6, Webhooks

7.0 – 7.4.4

TeamForge Associations Add-on 2.11-7, Webhooks

JIRA Software Data Center

6.3 –6.4.14

TeamForge Association sAdd-on 2.11-6, Webhooks

7.0 –7.4.4

TeamForge Associations Add-on 2.11-7, Webhooks


6.3 –6.4.14

TeamForge Associations Add-on 2.11-6

7.0 –7.4.4

TeamForge Associations Add-on 2.11-7

Jenkins (Job and Pipeline)

1.645 or later

collabnet.hpi 2.0.4

External Git or later





External Subversion

1.7 or later


Subversion Edge

5.0 or later











Review Board3






Nexus Repository OSS

2.9 - 2.14.5


Artifactory Pro (on premises only)

4.7 or later


Microsoft applications

The following Microsoft applications have been tested with TeamForge:

  • Microsoft Office XP (with Service Pack 3) on Windows XP Service Pack 2 and Windows 2000 Service Pack 4.
  • Microsoft Office 2003 (with Service Pack 1) on Windows XP Service Pack 2 and Windows 2000 Service Pack 4.

PostgreSQL or Oracle?

PostgreSQL 9.6.5 is installed automatically when you install TeamForge 17.11. 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 17.11 supports Oracle server 12c and Oracle client 12c.
  • Oracle express edition is not supported for both client and server.
  • Review Board was tested with PostgreSQL 9.6.5 only. Review Board with Oracle was not tested.
  • 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.

* You must have adequate RAM to accomodate the JVM heap requirements of Elasticsearch in addition to the JVM heap requirements of other components such as Jboss, integrated applications, and so on.
# The required hard drive capacity depends on the estimated amount of document and file release uploads.
1 Red Hat Enterprise Linux servers must have access to the Red Hat Network or equivalent (satellite server, spacewalk, or RHN proxy).
2 For larger installs, the max JVM heap size should be increased to 1024MB (or larger), depending on available resources on the server.
3 It is recommended to install Review Board on the TeamForge application server.