The WebSphere MQ Properties page allows you to view and modify the configuration details for a specific WebSphere MQ resource via the properties panel if it is enabled. Specific WebSphere MQ resource configuration properties can also be modified via the Resource Context Menu.

To edit configuration details via the WebSphere MQ Configuration Properties page from the LifeKeeper GUI Properties Panel, you must first ensure the GUI Properties Panel is enabled. To enable the GUI Properties Panel, select View, then Properties Panel (must have a check mark to indicate it is enabled). Once enabled, left-click on the WebSphere MQ resource to display its configuration details in the LifeKeeper GUI Properties Panel.

Below is an example of the properties page that will appear in the LifeKeeper GUI Properties Panel for a WebSphere MQ resource.

The properties page contains four tabs. The first tab, labeled IBM WebSphere MQ Recovery Kit Configuration, contains configuration information that is specific to WebSphere MQ resources and allows modification via the resource specific icons. The remaining three tabs are available for all LifeKeeper resource types and their content is described in the topic Resource Properties Dialog in the LifeKeeper for Linux Technical Documentation.

The following table displays the WebSphere MQ resource specific icons and the configuration component that can be modified when clicking on the icon.

Listener Protection Configuration Allows you to specify whether protection of the IBM WebSphere MQ listener is included with the other IBM WebSphere MQ queue manager components being protected.
PUT/GET Test Queue Configuration Allows you to change the name of the queue that the IBM WebSphere MQ Recovery Kit will use to perform PUT/GET tests for the queue manager being protected.
Logging Level Configuration Allows you to modify the log level that the IBM WebSphere MQ Recovery Kit will use for the queue manager being protected.
Shutdown Timeout Configuration Allows you to modify the timeout in seconds for the immediate shutdown and preemptive shutdown timers for the IBM WebSphere MQ queue manager being protected.
Server Connection Channel Configuration Allows you to modify the server connection channel that is used for client connection and the PUT/GET testing for the IBM WebSphere MQ queue manager being protected.
Command Server Protection Configuration Allows you to specify the protection/recovery level for command server component of the IBM WebSphere MQ queue manager being protected.

More details on each of these configuration options can be found below.

Listener Management Specifies whether you want LifeKeeper to protect the listener for the queue manager or not. If listener management is disabled (value of NO), LifeKeeper will not monitor the listener and you can stop the listener without causing LifeKeeper recovery actions. If listener management is enabled (value of YES), LifeKeeper will monitor the listener and restart the listener if the listener is not running. If the recovery fails, a failover of the WebSphere MQ hierarchy to the backup server is initiated.
LifeKeeper Test Queue LifeKeeper performs PUT/GET test to monitor queue manager operations. The WebSphere MQ Recovery Kit uses a dedicated test queue to put messages in and retrieve messages again. In case a failure is detected, no recovery or failover is performed. Instead, the Recovery Kit sends an event that you can register to receive. The events are called putgetfail and putgetcfail. You can add a notification script to the directories /opt/LifeKeeper/events/mqseries/putgetfail and /opt/LifeKeeper/events/mqseries/putgetcfail to react to those events.

Note 1: If the LifeKeeper test queue is not configured in the queue manager, the PUT/GET test is skipped. No recovery or failover takes place.

Note 2: If the listener is protected, a second client connect check will be done. If this check fails, a recovery or failover of the queue manager is attempted.
Logging Level You can set the logging level of the WebSphere MQ Recovery Kit to four presets:


    In this log level, only errors are logged. No informational messages are logged.

  • INFORMATIONAL (default)

    In this log level, LifeKeeper informational messages about start, stop and recovery of resources are logged.


    In this log level, the informational LifeKeeper messages and the command outputs from all WebSphere MQ commands in the restore, remove and recovery scripts are logged.

  • FINE

    In this log level, all command outputs from WebSphere MQ commands issued in start, stop, recovery and quickCheck scripts are logged. Additional debug messages are also logged.

    It is recommended to set this debug level only for debugging purpose. As quickCheck actions are also logged, this fills up the log files each time a quickCheck for the WebSphere MQ queue manager runs.

    The default is INFORMATIONAL. This is equivalent to normal LifeKeeper logging of other recovery kits.

Note: Independent of the logging level setting, WebSphere MQ errors during start, stop, recovery or during the check routine are always logged with the complete command output of the last command run.
Stop Timeout Values The WebSphere MQ Recovery Kit stops the queue manager in 3 steps:

  1. immediate stop

  2. preemptive stop

  3. kill all queue manager processes

    The timeout values specified determine the time the Recovery Kit waits in Steps 1 and 2 for a successful completion. If this timeout is reached, the next step in the shutdown process is issued. The default for the immediate and preemptive shutdown timeouts is 20 seconds.
Server Connection Channel The WebSphere MQ Recovery Kit allows the specification of the server connection channel. By default, the kit will use the channel SYSTEM.DEF.SVRCONN, but an alternate channel can be specified during resource creation or at any time after resource creation.
Command Server The WebSphere MQ Recovery Kit allows two levels of protection and recovery for the command server component for the protected queue manager. The levels are Full and Minimal.

With Full protection, the command server will be started, stopped, monitored and recovered or failed over if recovery is unsuccessful. The recovery steps with Full protection are:

  • Attempt to restart just the command server process.

  • If that fails, attempt a full restart of the queue manager including the command server process.

  • If both attempts are unsuccessful at restarting the command server, then initiate a failover to the standby node.

    With Minimal protection, the command server will only be started during restore or stopped during remove. No monitoring or recovery of the command server will be performed.

NOTE: Starting the command server will only be performed by the Recovery Kit during restore if the queue manager SCMDSERV parameter is set for manual startup. During a recovery, a failed command server restart will always be attempted regardless of the SCMDSERV setting unless the Command Server Protection Level is set to Minimal.

As previously noted, these WebSphere MQ resource configuration components can be modified using the resource specific icons in the properties panel or via the Resource Context Menu.

The parameters above can be set for each queue manager separately either via the LifeKeeper GUI or via a command line utility.

To set the parameters via the command line, use the script:



Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment