Here's what it takes to install and run TeamForge.
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 # |
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+ |
Operating system | RHEL 6.8 or 7.3 1 (64 bit) | CentOS 6.8 or 7.3 (64 bit) |
Browser | Google Chrome 58 |
Mozilla Firefox 53 | |
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.1 is installed by default when you install TeamForge 17.4. 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_112 | |
Tomcat 8.0.39 | |
Elasticsearch | 5.1.1 |
Yum package manager | 3.2.29 or earlier versions |
TeamForge 17.4 supports the following software versions for integration | |
Review Board 3 | 2.5.6.1 |
Git/Gerrit | 2.13.x |
Subversion | 1.8.17 |
Subversion Edge | 5.0 |
CVS | 1.11.x |
ViewVC | 1.1.24 |
Nexus | 2.9.0 or later |
Artifactory Pro | 4.7 |
Jira | 6.3-7.1 |
TestLink | 1.9.15 and 1.9.16 |
The following Microsoft applications have been tested with TeamForge:
PostgreSQL 9.6.1 is installed automatically when you install TeamForge 17.4. 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.