Understanding Sun Cluster HA for WebSphere MQ Integrator Fault Monitor

This section describes the Sun Cluster HA for WebSphere MQ Integrator fault monitor's probing algorithm or functionality, states the conditions, messages, and recovery actions associated with unsuccessful probing.

For conceptual information on fault monitors, see the Sun Cluster Concepts Guide.

Resource Properties

Sun Cluster HA for WebSphere MQ Integrator fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.

Probing Algorithm and Functionality

• WebSphere MQ Integrator Broker

  • Sleeps for Thorough_probe_interval.

  • Test the RDBMS or Queue Manager has been restarted. If the RDBMS has been restarted, then the whole Resource Group will be restarted. If the Queue Manager has been restarted, then the Broker is stopped and waits until the Queue Manager is restarted, after which the Broker is restarted.

  • If the RDBMS and Queue Manager have not been restarted, then a check against bipservice is made. If bipservice is lost, then the probe will restart the Broker.

  • If bipservice is available, then the probe checks that the queue names for SC3_IN and SC3_OUT are valid and empty, puts a test message to SC3_IN, and checks that the message flows to SC3_OUT by checking that the CURDEPTH for SC3_OUT is equal to 1. If this test fails, then the probe will restart the Broker.

  • If the Broker is repeatedly restarted and subsequently exhausts the Retry_count within the Retry_interval, then a failover is initiated for the Resource Group onto another node.

• WebSphere MQ Integrator UserNameServer

  • Sleeps for Thorough_probe_interval

  • If bipservice for the UserNameServer is lost, then the probe will restart the UserNameServer.

  • If the UserNameServer is repeatedly restarted and subsequently exhausts the Retry_count within the Retry_interval then a failover is initiated for the Resource Group onto another node.