You can configure an external high availability framework,
such as IBM HACMP, to manage a messaging engine as
if it were a resource in the external high availability framework's
resource group.
To allow a messaging engine to
be managed by an external high availability framework,
you must configure a 'No operation' policy for the messaging engine.
Once the correct policy has been configured, HAManager will
only activate or deactivate a messaging engine when
instructed to by the external high availability framework.
The following situations require the use of an external
high availability framework:
- Connecting a messaging engine to
WebSphere MQ using a WebSphere MQ link.
WebSphere MQ uses a connection name, containing an IP address and a port number,
to reach the messaging engine. If
the messaging engine fails over to
another cluster server then the IP address and port number needed to reach
it can change. To enable WebSphere MQ to continue communicating with the messaging engine, it is important that
the messaging engine uses a floating
IP address that will be collocated with the messaging engine.
You can achieve this collocation using an external HA cluster framework.
- Using an external database for the messaging engine's data store to persist its data.
In this case, the database must be accessible by the server that is running
the messaging engine. This can be
achieved by including the database and the messaging engine
in the same external cluster resource group, resulting in the database being
collocated with the messaging engine.