IBM


2.1.1 Hardware-based high availability

Using a WAS multiple machine or LPAR configuration eliminates a given appserver process as a single point of failure. In IBM WAS ND V6, there are basically no dependencies on the administrative server process for security, naming, and transactions. Thus, a single process failure normally does not disrupt application processing.

In fact, the only single point of failure in a WebSphere cell is the Deployment Manager, where all central administration is performed. However, a failure of the Deployment Manager only impacts the ability to change the cell configuration, to run the Tivoli Performance Viewer (which is included in the Administrative Console in WebSphere V6), or to perform a failover for EJBs using a backup cluster (Backup cluster support).

A number of alternatives exist to provide high availability for the Deployment Manager, including the possible use of an external High Availability solution, though the minimal impact of a Deployment Manager outage typically does not require the use of such a solution. Some customers even choose to run their production environment without an active Deployment Manager. See Part 5, Using external clustering software for more information about using clustering software to make the Deployment Manager highly available.


Redbooks ibm.com/redbooks

Next