|
|
The high availability capabilities of WebSphere V6 have been further improved compared to previous versions. WAS V6 can be used as part of an overall 99.999% availability solution. However, to achieve this, your environment has to be highly available. For that reason, you also need to consider the surrounding services. We cover some WebSphere V6 settings for interacting with typical enterprise services.
You should modify some parameters in the WebSphere V6 configuration to leverage the benefits of using external clustering software in your environment. These settings are driven by the systems architecture and thus valid for all flavours of external clustering software. We discuss the settings for:
| Node Agent and appserver HA |
|
| Deployment Manager HA |
|
| Configure JMS resources |
|
| Configure JDBC/data sets |
|
| Configure security |
Platform-clustering software packages can be used to enhance the availability of the entire WebSphere system. The unit of failover usually includes a collection of network definitions and disk storage, and one or more services such as the DB2 database server (or other database servers), the HTTP server, firewalls, LDAP server, WAS, WebSphere Node Agent or Deployment Manager. However, it is not standardized, and different vendors use different terms. For example, the unit of failover in IBM HACMP or HACMP/ES Cluster is called an appserver, while the unit of failover in IBM Tivoli System Automation (TSA) is called resource group. Sun Cluster calls its failover unit a logical host, and the unit of failover in VERITAS Cluster Server is called Service Group.
