Configuring and Tuning the Jazz Team Server (JTS)

Configuring JTS should be simple and straightforward for most initial implementations. There should not be too many things to consider during the initial configuration of JTS. After the server is deployed, sometimes performance issues dictate that you consider configuring and tuning the Java Virtual Machine (JVM) for JTS.

General concerns

When you consider how to configure JTS, it is critical to know the Jazz applications that the server will support, and the expected user load on the solution. Keep in mind that any single Jazz solution will contain a single JTS. Some organizations deploy multiple JTS instances into their enterprise solution, but, as an administrator, it is best for you to consider each of these instances as a single stand-alone instance of a Jazz solution. Each single JTS can support multiple CCM (RTC) instances, multiple QM (Rational Quality Manager) instances, a single RM (Rational Requirements Composer) instance, and a single data warehouse instance (Rational Reporting for Development Intelligence or Rational Insight).

Configuring the JVM settings

One of the most important things that you configure are the JVM settings that are used when you deploy the JTS. These settings often have a large impact on the performance of your JTS application, and you should have these tracked somewhere as part of your solution architecture description. Often, it is best to start with the default JVM settings suggested by the development team.

Related topics: Configuring and tuning the JVM

External links:

• None

Additional contributors: None