How many servers do I need to run a TeamForge site?

You can run TeamForge on one server or distribute its services on multiple servers.

TeamForge functionality is delivered by several discrete services. Each service can run on its own server or share a server with one or more other services. You assign specific services to specific boxes when you customize your TeamForge installation by editing the site-options.conf file. See TeamForge installation requirements for more information.

TeamForge core functionality

This is known internally as the app server. It implements JBoss and Apache services. One and only one instance of this application must be present.

Tip: TeamForge 17.11 supports an integration with the Review Board, a source code review tool supported by TeamForge, if required, must be installed on the TeamForge app server.

Database

The database application handles site users' data. You set the type of database by setting the value of the DATABASE_TYPE token to oracle or postgresql. One and only one instance of this application must be present. TeamForge's operational database can run on the TeamForge app server or on a separate server.

Subversion

Subversion can be used to provide source control functionality. It uses the Tomcat and Apache services. A site can have zero, one, or more than one instances of the svn application, running on an arbitrary number of servers.

CVS

CVS can be used to provide source control functionality. It uses the Tomcat service. A site can have zero, one, or more than one instances of the cvs application, running on an arbitrary number of servers.

etl

The reporting service.

datamart

A mirror of your site database for the reporting engine to work with.

EventQ

TeamForge EventQ is a TeamForge capability that provides traceability for product life cycle activities such as work items, SCM commits, continuous integration (CI) builds, and code reviews. While you can run both EventQ and TeamForge on the same server, CollabNet recommends such an approach only for testing purposes. It's always recommended to run EventQ on a separate server for optimal scalability. See EventQ installation requirements for more information.

Git

TeamForge 17.11 supports an integration with the Git distributed version control tool powered by Gerrit. TeamForge 17.11 supports Git integration based on Gerrit 2.13.x. For more information, see Set up Git.

In principle, services can be combined in any configuration, with some constraints, such as:

• Only one site database, datamart and reporting service.
• Multiple source control integration services, but only one per box.

In practice, CollabNet has identified few configurations as the most useful for a wide variety of site. You can follow the instructions here to set up your site in one of these configurations, or you can adapt one of them to your own conditions.