IBM BS029ML Self Help Guide - Page 39
Two independent HTTP Server clusters HTTP Cluster A and HTTP Cluster B, consisting
![]() |
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 39 highlights
community data between different Portal clusters, and the cluster members that participate in each, ensures consistency at the user interaction level (new to Portal Server V6.0.x). That is, any user customization made against one Portal cluster member, by a user, is now available to the same user, as and when that user accesses any of the other cluster members participating in the same or different Portal cluster. Each Portal cluster, in turn, maintains a separate release repository, which provides a mechanism for maintaining all Portal resource definitions, rules, and rights specific to that cluster. Again, this is an acknowledged product improvement from the limitations associated with WebSphere Portal Server V5.1.x and earlier. Failing to implement such an architecture would otherwise necessitate deploying a single clustered instance of WebSphere Portal Server and adopting either the IBM documented 24x7 Portal maintenance procedure or the use of a secondary maintenance environment. Figure 2-3 illustrates the system topology needed for a Portal Server V6.0.x dual cluster architecture. Firewall Load Balancer HTTP Cluster A Line of Production A HTTP Server node: ebizWS01 HTTP Server node: ebizWS02 Firewall Load Balancer HTTP Server node: ebizWS01 HTTP Server node: ebizWS02 HTTP Cluster B Line of Production B Portal Cluster A Line of Production A WAS Cell A WebSphere_Portal_3 WebSphere_Portal_2 WebSphere_Portal_1 WebSphere_Portal WebSphere_Portal_7 WebSphere_Portal_6 WebSphere_Portal_5 WebSphere_Portal_4 node: PORTAL01 node: PORTAL02 WebSphere_Portal_3 WebSphere_Portal_2 WebSphere_Portal_1 WebSphere_Portal WebSphere_Portal_7 WebSphere_Portal_6 WebSphere_Portal_5 WebSphere_Portal_4 node: PORTAL03 node: PORTAL04 Portal Cluster B Line of Production B WAS Cell B WAS Cell A Deployment Manager Shared DMGR Instance: PSPROD ReleaseAusr ReleaseBusr Customization (shared) Community (shared) wmm (shared) fdbkusr (shared) fdbkusr (shared) jcr (shared) Instance: JCRPROD node: PORTDB01 node: PORTDB02 Figure 2-3 Dual cluster architecture illustrating two lines of production WAS Cell B Deployment Manager node: WSND01 Key features of this architecture are: Two independent HTTP Server clusters (HTTP Cluster A and HTTP Cluster B), consisting of at least two physical nodes per cluster (so that each cluster is highly available in its own right). Two independent WebSphere Portal Server clusters (Portal Cluster A and Portal Cluster B), one per WebSphere Cell. Chapter 2. Architecture and planning 25
![](/manual_guide/products/ibm-bs029ml-self-help-guide-6d3dd71/39.png)