<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"/> Alternative SSE deployment topologies 5.0 %DKGRAY% Authors: Main.ThomasPiccoli, Main.GrantCovell <br> Build basis: The Rational solution for systems and software engineering (SSE), version 5.0, 5.0.1, 5.0.2 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> ---++ Standard topologies overview This page describes the Alternative SSE Deployment Topologies for version 5.x. Refer to [[StandardTopologiesOverview][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) 5.0 are a subset of the standard SSE deployment topologies. For the rest of the standard topologies, see [[RecommendedSSEDeploymentTopologies5][Recommended SSE deployment topologies 5.0]]. As of 5.0.1 new installs can share a single instance of JRS. !RELM no longer requires a separate instance of JRS installed with a context root of SPARQL_Gateway. As of 5.0.2 the Lifecycle Project Administration (LPA) application has been incorporated into the Jazz Team Server. It is no longer delivered as a separate WAR application. ---++ (SSE-E0) Enterprise - Middleware and OS not specified <b>Warning</b>: DCC should not be installed if DOORS is the RM provider as data warehouse conflicts will occur. Instead configure the standard ETL jobs for all tools that contribute to the data warehouse. %TABLE{ tablewidth="60%" cellpadding="4" cellspacing="3" }% | __Metadata Variable__ | __Value__ | | Operating System | not specified | | Database Management System | not specified | | Application Server | not specified | | License Management System | Floating | | User Management System | Tivoli Directory Server and Microsoft Active Directory | | Other technologies | Reverse Proxy | <div style="text-align:center;"><img src="%ATTACHURLPATH%/enterprise_502.png" alt="enterprise_502.png" width="90%"/><br><br> __(SSE-E0) Enterprise - Middleware and OS not specified__ </div> ---++ (SSE-E3) Enterprise distributed Red Hat Enterprise Linux (RHEL) with DB2 This enterprise topology uses Linux for the server operating systems. 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. <b>Note</b>: 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) <b>Warning</b>: DCC should not be installed if DOORS is the RM provider as data warehouse conflicts will occur. Instead configure the standard ETL jobs for all tools that contribute to the data warehouse. %TABLE{ tablewidth="60%" cellpadding="4" cellspacing="3" }% | __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 | <div style="text-align:center;"><img src="%ATTACHURLPATH%/sse_e3_rhel_db2_502.png" alt="sse_e3_rhel_db2_502.png" width="90%"/><br><br> __(SSE-E3) Enterprise distributed Red Hat Enterprise Linux (RHEL) with DB2__ </div> %TABLE{ tablewidth="60%" cellpadding="4" cellspacing="3" }% | __Server__ | __Software__ | |1|JTS, WAS| |2|CCM, WAS| |3|QM, WAS| |4|RM, WAS| |5|DCC, WAS| |6|RS, WAS| |7|DM, WAS| |8|!RELM, WAS| |9|VVC, WAS| |10|LQE, WAS| |11|DOORS DB| |12|DWA, Broker, Tomcat| |13|DOORS Interops (1..n)| |14|DB2| |15|IHS Reverse Proxy Server| |16|LDAP Server| |17|License Server| ---++ (SSE-D0) Departmental Middleware and OS not specified <div style="text-align:center;"><img src="%ATTACHURLPATH%/departmental_502.png" alt="departmental_502.png" width="75%"/><br><br> __(SSE D0) Departmental - Middleware and OS not specified__ </div> ---++ (SSE-D1) Departmental Windows with DB2 <div style="text-align:center;"><img src="%ATTACHURLPATH%/sse_d1_windows_db2_502.png" alt="sse_d1_windows_db2_502.png" width="75%"/><br><br> __(SSE D1) Departmental Windows with DB2__ </div> ---++ (SSE-D5) Departmental Red Hat Enterprise Linux (RHEL) with Oracle <b>Note</b>: 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) <div style="text-align:center;"><img src="%ATTACHURLPATH%/sse_d5_rhel_oracle_502.png" alt="sse_d5_rhel_oracle_502.png" width="75%"/><br><br> __(SSE-D5) Departmental Red Hat Enterprise Linux (RHEL) with Oracle DOORS__ </div> ---++ (SSE-V1) Evaluation Windows, Tomcat and Derby <b>Note</b>: The evaluation topology does not meet the demands of a typical production workload because of the limited scalability of the single application server. While this topology is ideal for evaluations, demonstrations, and training purposes realize that the data created in an evaluation topology cannot be transferred to a scalable production environment when the evaluation is complete. <div style="text-align:center;"><img src="%ATTACHURLPATH%/sse_v1_windows_derby_502.png" alt="sse_v1_windows_derby_502.png" width="90%" /><br><br> __(SSE-V1) Evaluation__ </div> %INCLUDE{"ApplyingTheToplogies"}% ---+++++!! Related topics: * [[DeploymentPlanningAndDesign][Deployment planning and design]] * [[RecommendedSSEDeploymentTopologies5][Recommended SSE deployment topologies]] ---+++++!! External links: * None ---+++++!! Additional contributors: None <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentPlanningAndDesign
>
AlternativeSSEDeploymentTopologies5
History: r11 - 2014-12-15 - 19:35:21 - Main.tomp
Copyright © by IBM and non-IBM 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
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.