Fully distributed Rational® Requirements Composer 3.0.1 enterprise topology example

This topology example is for a fully distributed enterprise deployment with IBM WebSphere® Application Server and an enterprise database management system, such as IBM 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 it so that you can keep the data in case you decide to move to another deployment.

The following figure shows a fully distributed enterprise topology with one instance of the Requirements Management application installed on a separate application server.
Important: Two instances of the Requirements Management application cannot be merged onto the same Jazz Team Server. They must be deployed on separate team servers.

Fully distributed Rational Requirements Composer enterprise topology example

Table 1. Key for abbreviations
Abbreviation Name
CCM Change and Configuration Management application
JTS Jazz Team Server
DB2 IBM® Database Management System
WebSphere WebSphere Application Server
RM Requirements Management application
Note: Latest entries in the jazz.net library on installing Rational Requirements Composer

Feedback