WebSphere Portal Server Gold Availability standard

When you have a requirement for 24*7 availability you should WebSphere Portal Server Gold Availability standard. In the WebSphere Portal Gold Availability standard you will have two distinct websphere portal server clusters each deployed within separate websphere cells. This makes it possible to perform maintenance on one portal cluster while other continues to service user requests. This architecture can also be called as multiple lines of productions.

In case of Gold avalability standard customization and community data is shared between different portal clustes and the cluster members that participate in each, this ensures consistency at the user interaction level. Tha is if any user customization is made against one portal cluster member, by a user then it is available to same user as when the user accesses any of the other cluster members participating in same or different portal cluster. Each cluster however maintains a separate release repository which provides a mechanism for maintinaing all portal resources definition, rules and rights specific to that cluster.




Key features of this architecture are:
 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.
  node:


• Two independent WebSphere Cells (Cell A and Cell B).


• Each WebSphere Portal Server cluster consists of at least two physical nodes per cluster or cell (so that each cluster is in highly available its own right).


• The WebSphere Plug-in resident in each HTTP Server only routes requests to the cluster members for the immediate Portal Cluster.


• Two independent WebSphere Network Deployment Manager (Deployment Manager) instances, one per WebSphere Cell, are collocated on the same physical node.


• A separate release database domain (releaseAusr and releaseBusr) exists for each WebSphere Portal Server cluster or Lines of Production (Portal Cluster A and PortalCluster B), maintaining indenpendant configuration data for each.



• The remaining database domains (communityusr, customizationusr, wmmusr, fdbkusr,lmdbusr, and jcr) are shared between each WebSphere Portal Server cluster or Lines of Production to maintain a consistent user experience. Note that the JCR Repository exists in a different database.


• The environment also hosts a LDAP directory server (not shown), which is highly available, for maintaining the registered user base.