Jazz™ Team Server and
the associated Rational® solution
for systems and software engineering applications have typical deployment
topologies.
This product installation consists of Jazz Team Server and
one or more web applications: Quality Management (QM), Change and
Configuration Management (CCM), and Rational DOORS® or IBM® DOORS Next
Generation, Rational Rhapsody®, and Rational Rhapsody Design
Management. The applications can be deployed on the same application
server for small-scale evaluation purposes, or on different application
servers for greater scalability and flexibility for future growth.
There is one database for the data warehouse and one for each application,
including the Jazz Team Server.
To use the product integrations, all of the applications must share
a common Jazz Team Server or
create friend relationships between Jazz Team
Servers and configure OSLC services. By using a shared Jazz Team Server,
collaboration can occur among applications and a common set of users.
A shared server also provides common license administration and common
e-mail and LDAP settings. For more information about the advantages
of sharing a server, see Determining the number of Jazz Team Servers to use.
There are currently three typical example deployment topologies.
Deployment topologies
The example deployment
topologies for the Rational solution
for systems and software engineering are as follows:
- Evaluation topology: In this topology, applications are deployed
on a single application server with a shared Jazz Team Server.
This topology is ideal for evaluations, demonstrations, and training
purposes.
The evaluation topology does not meet the demands of
a typical production workload because of the limited scalability of
the single application server. Use a powerful computer with a lot
of memory and a fast disk drive to handle the load of both the application
servers and the database servers. This topology uses Apache Tomcat
as the application server and Apache Derby, which is limited to 10
users, as the database. For a diagram and examples, see the following
example topology:
- Departmental topology: In these topologies, applications are deployed
on one or more application servers with some shared Jazz Team Servers.
This topology is ideal for mid-size deployments, such as single departments
or teams. These topologies use Apache Tomcat for DOORS Web Access and IBM WebSphere® Application
Server for the Jazz-based products. WebSphere Application Server reduces the
need to authenticate as you access multiple application servers. These
topologies also use an enterprise database management system, such
as IBM DB2®, with a dedicated database server on a separate
system. For diagrams and examples, see the following example topologies:
- Enterprise topology: In these topologies, applications are deployed
on one or more application servers with shared Jazz Team Servers.
This topology is ideal for large deployments, such as teams. These
topologies use Apache Tomcat for DOORS Web
Access and IBM WebSphere Application Server for the Jazz-based
products. WebSphere Application
Server reduces the need to authenticate as you access multiple application
servers. These topologies also use a enterprise database management
system, such as IBM DB2, with a dedicated database server
on a separate system. For diagrams and examples, see the following
example topologies:
Deployment of multiple instances of applications
You
can also deploy multiple instances of an application, such as the
CCM application. If you deploy multiple instances of the same application
in the same application server, you must give each instance a separate
context root. For example, the context roots for two CCM instances
could be ccm1 and ccm2. To connect multiple instances of the CCM application
to a shared Jazz Team Server,
the instances must all be authenticated from the same authentication
realm and thus share the same set of users. In any deployment, the
licenses are managed by Jazz Team Server.
When
you choose a topology for your deployment, carefully consider both
the present and future needs of your team. While it is possible to
move applications to a different application server later, this change
requires the use of a proxy server to maintain links to that application.