When to use a high availability manager

A high availability manager consumes valuable system resources, such as CPU cycles, heap memory, and sockets. These resources are consumed both by the high availability manager and by product components that use the services that the high availability manager provides. The amount of resources that both the high availability manager and these WebSphere Application Server components consume increases exponentially as the size of a core group increases.

For large core groups, the amount of resources that the high availability manager consumes can become significant. Disabling the high availability manager frees these resources. However, before you disable the high availability manager, you should thoroughly investigate the current and future needs of your system to ensure that disabling the high availability manager does not also disable other functions that you use that require the high availability manager. For example, both memory to memory session replication, and remote request dispatcher (RRD) require the high availability manager to be enabled.

The capability to disable the high availability manager is most useful for large topologies where none of the high availability manager provided services are used. In certain topologies, only some of the processes use the services that the high availability manager provides. In these topologies, you can disable the high availability manager on a per-process basis, which optimizes the amount of resources that the high availability manager uses.

Do not disable the high availability manager on administrative processes, such as node agents and the deployment manager, unless the high availability manager is disabled on all application server processes in that core group.

Some of the services that the high availability manager provides are cluster based. Therefore, because cluster members must be homogeneous, if you disable the high availability manager on one member of a cluster, you must disable it on all of the other members of that cluster.

When determining if you must leave the high availability manager enabled on a given application server process, consider if the process requires any of the following high availability manager services:

Memory-to-memory replication

Memory-to-memory replication is a cluster-based service that you configure or enable at the application server level. If memory-to-memory replication is enabled on any cluster member, then the high availability manager must be enabled on all of the members of that cluster. Memory-to-memory replication is automatically enabled if:

Singleton failover

[AIX HP-UX Linux Solaris Windows] [iSeries] Singleton failover is a cluster-based service. The high availability manager must be enabled on all members of a cluster if:
  • The cluster is configured to use the high availability manager to manage the recovery of transaction logs.
  • One or more instances of the default messaging provider are configured to run in the cluster. The default messaging provider that is provided with the product is also referred to as the service integration bus.

[z/OS] Singleton failover is a cluster-based service. The high availability manager must be enabled on all members of a cluster if one or more instances of the default messaging provider are configured to run in the cluster. The default messaging provider that is provided with the product is also referred to as the service integration bus.

Workload management routing

Workload management (WLM) propagates routing information for the default IBM Java Messaging Service (JMS) provider, which is also referred to as the messaging engine.

[iSeries] [AIX HP-UX Linux Solaris Windows] It also propagates routing information for enterprise bean Internet Inter-ORB Protocol (IIOP) traffic.

WLM uses the high availability manager to both propagate the routing information and make it highly available. Although WLM routing information normally applies to clustered resources, it can also apply to non-clustered resources, such as standalone messaging engines. Under normal circumstances, you must leave the high availability manager enabled on any application server that produces or consumes either IIOP or messaging engine routing information. For example if:
  • The routing information producer is an enterprise bean application that resides in cluster 1.
  • The routing information consumer is a servlet that resides in cluster 2.

When the servlet in cluster 2 calls the enterprise bean application in cluster 1, the high availability manager must be enabled on all servers in both clusters.

Workload management provides an option to statically build and export route tables to the file system. Use this option to eliminate the dependency on the high availability manager. See Enabling static routing for a cluster for more information about the Export route table option.

On-demand configuration routing

In a Network Deployment system, the on-demand configuration is used for proxy server routing. If you want to use on-demand configuration routing in conjunction with your Web services, you must make sure that the high availability manager is enabled on the proxy server and on all of the servers to which the proxy server will route work.




Related concepts
Core groups (high availability domains)
Core group scaling considerations
High availability manager
Related tasks
Disabling or enabling a high availability manager
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=crun_ha_ham_required
File name: crun_ha_ham_required.html