Maintenance procedure for single cluster portal

In case of single cluster environment maintenance must be performed as a multi-step process, these are the steps

• Disable the automatic file synchronization service from the Deployment Manager Administration consoel


• Stop the node agent on each of the node participating in the cluster.


• Perform maintenance on each node in turn starting with primary portal node by first gracefully quiescing user requests from each node by modifying the WebSphere Web Server plug-in load balancing weighting while remaining node or nodes in the cluster continue to honor user requests.


• The final steps is to synchronize and restart all of the nodes one at a time
• Re-enable automatic file synchronization service using Deployment manager administration console

Single cluster architecture

The single cluster architecture means when you have only one cluster under one cell and that cluster can have combination of horizontal and vertical cluster members.



Key features of this architecture are:


• A single load balanced HTTP Server cluster (HTTP Cluster) that spans two or more
  physical nodes.


•  A single WebShere Portal Server cluster (Portal Cluster) deployed in a single WebSphere Cell.


• The WebShere Portal Server cluster consists of two of more horizontal cluster members and any number of vertical cluster members per node (resources permitting).


• A dedicated stand-alone WebSphere Deployment Manager is responsible for the
  management of the entire WebSphere Cell (Cell A).


• As the environment only consists of a single WebShere Portal Server cluster, only a single release database domain is required. The remaining database domains (communityusr, customizationusr, wmmusr, fdbkusr,lmdbusr, and jcr) are deployed alongside the release database domain. 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.