TeamForge installation requirements

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
JIRA Core	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	1.8.3.1 or later	EventQ-git-adapter-1.0
Git/Gerrit	2.13.x	-
External Subversion	1.7 or later	EventQ-svn-adapter-1.0
Subversion Edge	5.0 or later	-
CVS	1.11.x	-
ViewVC	1.1.24	-
Crucible	3.0.1	EventQ-Crucible-adapter-1.0
Review Board3	2.5.6.1	RBInstaller-17.8.14, RB-EventQ-adapter-1.2
TestLink	1.9.15-1.9.16	collabnet-testlink-1.0.2
Nexus Repository OSS	2.9 - 2.14.5	CTF-Nexus-Integration-Plugin-2.1.1
Artifactory Pro (on premises only)	4.7 or later	Artifactory-teamforge-plugin

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.

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.