Fully distributed enterprise topology with idle standby

clutteredreverandΔιαχείριση Δεδομένων

31 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

95 εμφανίσεις

Installing

>
Installing the Rational solution for CLM

>
Planning to deploy and install

>
Performance and high availability

>
Idle
standby deployment

Fully distributed enterprise topology with idle standby

This topic
shows an example of a fully distributed deployment of a Rational® solution for Collaborative Lifecycle
Management (CLM) enterprise topology with IBM® WebSphere® Application Server, configured for manual
failover for high availability.

This topology uses s
eparate hosts for each application and the
Jazz™ Team Server
, similar to the
Fully distributed
CLM enterprise topology example
, with standby servers for each application and the Jazz Team Server. It also uses
IHS as a
Reverse Proxy

in order to be able to redirect requests from the primary application servers to the
backups in the case a failover is needed. At most only one instance of the application (primary or backup)
should be acti
ve. The Change and configuration management (CCM) and Quality management (QM)
applications, and the
Jazz Team Server

(/ccm, /qm, /jts), can be configured for idle standby. The Lifecycle
Project Administration web application (/admin) and the Requirements M
anagement (RM) application (/rm)
should be configured for cold standby (installed into WebSphere but applications not started in the backup). See
the section
Differences between idle standby and cold standby

for details. If you can tolerate a slightly longer outage, you
should consider cold standby for all the applications.

This topology requires

a shared file server for the application file based indexes (such as the work item text
index and resource RDF and text indexes). The shared file server will be used by the CCM and QM applications,
and the
Jazz Team Server
.


This topology assumes an ente
rprise database management system, such as IBM DB2, DB2 for z/OS, and DB2
for i database. Separate application,
Jazz Team Server
, and data warehouse databases are assumed but not
shown.

In order to minimize the risk of a single point of failure, you should

also consider the database server and the
shared file server. For information about configuring the DB2 high availability database repository, see this
jaz
z.net article
. You should also ensure the storage solution for the shared files provides for redundancy; for
example, RAID 10 or other SAN solutions that provide HA.

For information about setting up a high availability environment, see this topic
Manual failover techniques
.

Table 1. Key for abbreviations

Abbreviation

Name

CCM

Cha nge and Confi gurati on Management appl i cati on

Table 1. Key for abbreviations

Abbreviation

Name

JTS

Jazz Team Server

QM

Qua l i ty Management a ppl i cation

RM

Re qui rements

Management a ppl i catio n

RRDI

Ra ti o nal Repo rti ng f or De velopment Intel l i gence

Rel ated concepts
:

Ins t al l proce ss exampl e

De pl oyment t opologie s

Compl e t ing t he i nst allat ion of Jazz Te am Se rve r and t he Rat ional s olution f or Col laborat ive Li f ecycle Management appl i cations

Cl us t ering f or hi gh avai labi lit y

Rel ated tasks
:

Ins t al l ing Jaz
z Te am Se rve r and t he Rat ional s oluti on f or Col laborat ive Li f ecycle Management appl i cati ons

Runni ng t he s et up by us ing Cust om s et up i n
t he s et up wi z ard