r24 - 2014-06-27 - 20:02:52 - GrantCovellYou are here: TWiki >  Deployment Web > DeploymentPlanningAndDesign > AlternativeSSEDeploymentTopologies

new.png Alternative SSE deployment topologies

Authors: ThomasPiccoli, StevenBeard, CarlosFerreira
Build basis: The Rational solution for systems and software engineering (SSE), version 3.x, 4.x

Standard topologies overview

This page describes the Alternate SSE Deployment Topologies for versions 3.x and 4.x. Refer to Standard deployment topologies overview for high-level description of the standard topologies, how they are categorized and their key characteristics.

These alternative deployment topologies for the Rational solution for systems and software engineering (SSE) are a subset of the standard SSE deployment topologies. For the rest of the standard topologies, see Recommended SSE deployment topologies.

(SSE-E3) Enterprise distributed Red Hat Enterprise Linux (RHEL) with DB2 and DOORS/DWA

This enterprise topology uses Linux for the server operating systems. It includes DOORS/DWA as the RM application. 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.

Note: There have been incidences of the DWA Interops core dumping when processing an RQM Reconcile operation on Linux. To avoid this issue the DWA Interops should be run on a Windows server. This issue is currently under investigation in APAR PI08809 (http://www.ibm.com/support/docview.wss?uid=swg1PI07809)

Metadata Variable Value
Operating System RHEL
Database Management System DB2
Application Server WAS
License Management System Floating
User Management System Tivoli Directory Server and Microsoft Active Directory
Other technologies Reverse Proxy

ent_redhat_linux_db2.png

(SSE-E3) Enterprise distributed Red Hat Enterprise Linux (RHEL) with DB2 and DOORS

Server Software
1 RDM, VVC, WAS
2 RELM, WAS
3 CCM, WAS
4 QM, WAS
5 JTS, WAS
6 DB2
7 DWA, Broker, Tomcat
8 DOORS DB
9 LDAP Server
10 LQE, WAS
11 Reverse Proxy Server
12 License Server
13 DOORS Interops (1..n)

(SSE-D1) Departmental Windows with DB2 and DOORS/DWA

dept_windows_with_db2.png

Departmental Windows with DB2 and DOORS

(SSE-D2) Departmental Windows with DB2 and DNG

dept_windows_with_db2_dng.png

Departmental Windows with DB2 and DNG

(SSE-D5) Departmental Red Hat Enterprise Linux (RHEL) with Oracle and DOORS/DWA

Note: There have been incidences of the DWA Interops core dumping when processing an RQM Reconcile operation on Linux. To avoid this issue the DWA Interops should be run on a Windows server. This issue is currently under investigation in APAR PI08809 (http://www.ibm.com/support/docview.wss?uid=swg1PI07809)

dept_redhat_linux_with_oracle.png

Departmental Red Hat Enterprise Linux (RHEL) with Oracle DOORS

(SSE-D6) Departmental Red Hat Enterprise Linux (RHEL) with Oracle and DNG

dept_redhat_linux_with_oracle_dng.png

Departmental Red Hat Enterprise Linux (RHEL) with Oracle DNG

(SSE-V1) Evaluation

evaluation.png

Evaluation

Applying the topologies

Every customer's environment is different with unique, necessary and often immutable requirements and constraints. We recognize that these standard topologies may not provide enough detail to make them immediately implementable in some customer environments, but we wanted to describe several topologies with enough variability to give an indication of what is possible and where our recommendations start.

While we recommend customers start with a standard topology that is most applicable to them, we recognize they will need to make changes and customizations to support their own unique requirements and constraints. IBM will support your own implementations, but may ask you to describe which topology is most applicable to your deployment and ask you to document what is unique in your environment to expedite any potential support situation.

To aid you in documenting your chosen deployment topology, we have made the following Rational Software Architect (RSA) model files available:

These may be imported into RSA then further modified or expanded to represent your environment. Look at the Installation_Instructions.txt file for information on how to import the models into RSA.

Datasheets and sizing guidelines

Find CLM-specific performance datasheets, sizing guidelines and performance-related case studies on the Performance datasheets and sizing guidelines page.

Next steps

This topic is meant to briefly introduce these standard topologies and describe how they might be applied. Work is already underway to build upon and apply them. Subsequent updates to this topic and supporting topics will provide additional insight into their usage.

Future updates to this topic or supporting topics may cover:

  • Deeper look at select topologies
  • Provide suggested tuning parameters
  • Consider high availability database topologies
  • Begin to expand this topology model into other domains
  • Discussion of strategic integrations with other Rational and non-Rational products.

Related topics: Deployment planning and design, Recommended SSE deployment topologies

External links:
  • None

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r24 < r23 < r22 < r21 < r20 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project