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
JVM Heap Size 1.5GB 3GB 6GB > 8GB
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.8 or 7.2 1 (64 bit) | CentOS 6.8 or 7.2 (64 bit)
Browser Google Chrome 49
Mozilla Firefox 45
Microsoft IE 10 and 11
Safari 6.0.5 (8536.30.1).
TeamForge user interfaces are best viewed at screen resolution of at least 1280 x 800 (or more) pixels.
Database PostgreSQL 9.3.12 is installed by default when you install TeamForge 16.7. However, you can use Oracle if you want to. See PostgreSQL or Oracle for more information.
Oracle Server 12c
Oracle Client 12c
Yum package manager 3.2.29 or earlier versions
TeamForge 16.7 supports the following software versions for integration
Nexus 2.9.0 or later
Artifactory Pro 4.7 or later
Jira 6.3-7.1
TestLink 1.9.15 and 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.3.12 is installed automatically when you install TeamForge 16.7. 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.7 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 2.0.11 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.

* 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).