This topology example is for a fully distributed enterprise with WebSphere® Application Server and an enterprise database management system, such as DB2®.
The following topology is useful for production or medium-sized teams with large volume deployments, and for existing deployments where multiple Rational Team Concert™ instances have already been deployed. The Jazz™ Team Server and each application is installed separately on its own server. For migrations of existing multiple installations of Rational Team Concert or if you anticipate heavy use of the change and configuration management tool, then put them on their own servers so that you can distribute the load easily. Use a stable, company approved DNS and register it so that you can keep the data in case you decide to move to another deployment.
Databases are required for the Jazz Team Server, Change and Configuration Management, and the Data Warehouse. See the topics in Setting up the database for details about each database.
To resolve existing URL references, the Change and Configuration Management (CCM) application must use the same Public URI and be deployed at the same context root as the version 2 installation. By default, this Public URI is https://hostname.example.com:port/jazz for the CCM application. Likewise, the default context root for CCM is /jazz. You can set up a reverse proxy, which is a proxy server that logically sits in front of a set of other servers and determines where to route a particular request. For more information on how you can reallocate applications and data across physical servers and preserve URL stability, see Using a reverse proxy in your topology.
The following shows a fully distributed Rational Team Concert 2.0 enterprise topology.

After you have upgraded, the following shows a fully distributed enterprise topology with one instance of Rational Team Concert 3.0.1 installed on separate application servers.

If you have more than one instance, the following figure shows a fully distributed Rational Team Concert 3.0.1 topology with multiple instances of Change and Configuration Management installed on separate application servers.

| Abbreviations | Name |
|---|---|
| CCM | Change and Configuration Management |
| JTS | Jazz Team Server |
| WebSphere | WebSphere Application Server |