Edit
Attach
P
rintable
r17 - 2019-08-09 - 18:53:20 -
TimFeeney
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
StandardTopologyPatternsOverview
<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/uc.png" alt="uc.png" width="50" height="50" align="right"/> Standard deployment topology patterns overview %DKGRAY% Authors: Main.StevenBeard, Main.TimFeeney, Main.BreunReed, Main.PaulEllis, Main.ShubjitNaik <br> Build basis: CE/CLM 6.x (with some restrictions) %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> This page complements the [[Deployment.StandardTopologiesOverview][Standard Topologies Overview]] by providing diagrams and description of the main patterns that can be used for specific reasons within a CE/CLM deployment topology. They include only the parts of the deployment topology needed to present the pattern and not all of the other nodes that can be deployed within the wider topology. ---++ Rational Team Concert (RTC) clustering * RTC clustering topology pattern for CE/CLM 6.0.5 and beyond: <br /> <img src="%ATTACHURLPATH%/RTCClustering.png" alt="RTCClustering.png" width="1000" height="600" /> This patterns shows just the CE/CLM nodes required to cluster RTC. *Please Note:* The Jazz Authorization Server (JAS) is required for RTC clustering. In the topic [[ChangeAndConfigurationManagementClusteredEnvironmentVersion605][Setting up a Change and Configuration Management application clustered environment version 6.0.5 and later]] we provide specific guidance on setting-up a [[ChangeAndConfigurationManagementClusteredEnvironmentVersion605#Distributed_Cache_Microservice_D][Distributed Cache Microservice (DCM) for clustered applications]]: _The microservice must be installed and run on a machine that is accessible by all nodes of the clustered application. By default, the microservice is installed on the Jazz Team Server (JTS) machine under the server/clustering/cache directory and is started as part of the JTS startup sequence (on demand, only when a clustered application asks for it)._ _Note: For optimal performance, the DCM should be moved to a dedicated machine. The size of this machine will depend on the number of users in your RTC cluster and their usage. DCM can be deployed on a machine as small as 2 core, 4gb RAM and 100GB disk, but you will need to monitor the system and increase its size based on your load. We found that a 4 core, 8gb ram, 200gb disk virtual machine handled 500 users (but it will vary based on what your users do with the system)._ ---++ IBM HTTP Server (IHS) and Jazz Authorization Server (JAS) Clustering * IHS and JAS clustering topology pattern for CE/CLM 6.0.2 and beyond: <br /> <img src="%ATTACHURLPATH%/IHSAndJASClustering.png" alt="IHSAndJASClustering.png" width="800" height="1000" /> __An application delivery controller (ADC) is a computer network device in a datacenter, often part of an application delivery network, that helps perform common tasks, such as those done by web accelerators to remove load from the web servers themselves.__ Many customer are already using an ADC e.g. F5 BIG-IP, CITRIX !NetScaler, A10. We have quite a few customers using a combination of an ADC and an IHS Reverse Proxy. We have a few customers using multiple ADCs load balancing clustered IHS Reverse Proxies. Recently published best practice: [[CompareProxyServers][Reverse Proxies and Load Balancers in CLM Deployment]]. If you have an active Jazz deployment using Jazz Security Architecture (JSA) Single Sign-On, you can reduce the risk of outages by clustering a single Jazz Authorization Server with multiple replicas. If you only have a single JAS instance, then all authenticate requests will fail if that instance goes offline. If you have a JAS cluster, then login requests will succeed since they will automatically fall over to active JAS replicas. Refer to the following Jazz Deployment article for additional guidance on configuring JAS Clustering: [[PerformanceClusteredJAS][Setting up a cluster of Jazz Authorization Servers]]. #ModifiedDepartmental ---++ Modified Departmental patterns * Modified Departmental topology pattern for CE/CLM 6.0.2 and beyond: <br /> <img src="%ATTACHURLPATH%/ModifiedDepartmental.png" alt="ModifiedDepartmental.png" width="900" height="800" /> ---++ Multiple application servers of the same product * Multiple application servers topology pattern for CE/CLM 6.x: <br /> <img src="%ATTACHURLPATH%/MultipleApplicationServers.png" alt="MultipleApplicationServers.png" width="700" height="500" /> There has been clear guidance for several releases of CE/CLM on using multiple instances of the same application server: * [[PlanForMultipleJazzAppInstances][Planning for multiple Jazz server instances]] * [[MultipleCCMAppsUserPerspective][Multiple CCM Applications - A User Perspective]] In CE/CLM 6.0.6 ifix003 we added [[https://jazz.net/pub/new-noteworthy/rdng/6.0.6/6.0.6/index.html#10][Support for cross-server links with system and custom link types for RDNG]]. ---++ Multiple database servers * Multiple database servers topology pattern for CE/CLM 6.x: <br /> <img src="%ATTACHURLPATH%/MultipleDatabaseServers.png" alt="MultipleDatabaseServers.png" width="700" height="500" /> ---++ Security (SAML, Kerberos, OIDC, SCIM) * SAML topology pattern for CE/CLM 6.0.1 and beyond: <br /> <img src="%ATTACHURLPATH%/SAML.png" alt="SAML.png" width="1000" height="700" /> ---+++++!! Related topics: * [[Deployment.StandardTopologiesOverview][Standard Topologies Overview]] * [[Deployment.DeploymentPlanning][Deployment planning]] * [[Deployment.DeploymentPlanningAndDesign][Deployment planning and design]] ---+++++!! Additional contributors: <sticky></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r40
|
r19
<
r18
<
r17
<
r16
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
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
.