Recommended Application Lifecycle Management (ALM) deployment topologies 6.0

Standard topologies overview

This page describes the Recommended ALM Deployment Topologies for version 6.x. Refer to Standard deployment topologies overview for high-level description of the standard topologies, how they are categorized and their key characteristics.

These recommended deployment topologies for the Rational solution for Application Lifecycle Management (ALM) are a subset of the standard ALM deployment topologies. For the rest of the standard topologies, see alternative ALM deployment topologies (for version 6.x). Within this wiki, additional guidance and best practices will be developed about how to best instantiate these recommended topologies.

Introduction and approach

These recommended topologies were chosen based on the following criteria:

1. Those that are most commonly and successfully deployed to date by customers and internally within IBM
2. Those that are based upon the most commonly available platforms, operating systems and middleware
3. Those that are based upon technologies that customers, partners and the IBM Rational Field have the most experience with
4. Those that are the focus of testing within IBM Rational.

These recommended topologies represent only a few of the many permutations for deploying the Rational solution for ALM. The ALM systems requirements capture the full set of options for supported deployment permutations.

These topologies have been defined to capture good deployment patterns, which include additional guidance on building in flexibility, scalability, performance, and support for other non-functional requirements, such as high availability, disaster recovery, and security.

Recommended topologies

(ALM-E1) Enterprise - Distributed / Linux / DB2

This enterprise topology uses Linux for the server operating systems. It includes both DNG and DOORS/DWA as the RM applications. The applications are distributed across separate servers and WAS instances. A reverse proxy is used to ensure public URI stability. DB2 is used for the databases and is hosted on a separate server. Finally, licenses are served by a floating license server and Tivoli Directory Server provides the LDAP based user management, for all but DOORS/DWA, which uses Windows Active Directory Server.