This topology example is for a fully distributed enterprise deployment with IBM WebSphere® Application Server and an enterprise database management system, such as DB2®, DB2 for z/OS®, and DB2 for i.
The following topology is useful for production or medium-sized teams with large volume deployments, and for existing deployments where multiple IBM 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 application, put the applications on their own servers so that you can distribute the load easily. Use a stable, company-approved domain name server (DNS), and register the DNS so that you can keep the data in case you decide to move to another deployment.
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.

| Abbreviation | Name |
|---|---|
| CCM | Change and Configuration Management application |
| JTS | Jazz Team Server |
| DB2 | IBM® Database Management System |
| WebSphere | WebSphere Application Server |