The information in this article applies to:
Product: PM4Data, MIM
Version: 8.x
Platform: Windows
Introduction
This document does not cover the advantages of HA nor does it discuss how to set up MQ in a high availability (HA) environment. For this information, see MQ SupportPac MC91 (http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24011869).
This document discusses at a high level the steps required to set up PM4Data in a highly available environment. Note that no PM4Data volatile information is stored on the disk. All state information is stored in Websphere MQ queues.
When performing file transfers using PM4Data, special consideration must be given to external applications for handling partially written files that will exist temporarily until the node has completed a failover. This scenario is not discussed here and must be addressed by each receiving application.
HACMP Configuration
Configure the HA Cluster, Shared Disks, Create the Queue Manager, Configure the Moveable Resources, Configure the MQ Application Server or Agent, Configure an MQ Application Monitor
See MQ SupportPac MC91 (http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24011869) for more information.
There is no PM4Data volatile information that must be stored on the shared disks. All state information is stored in the MQ queues.
Configure the PM4Data Application Server or Agent
You must create a start and stop script. See MQ SupportPac MC91 for sample scripts that may be modified for PM4Data purposes.
Start Script
The following script is to be called: /var/CQ/bin/xmstart.ksh.
Stop Script
The script must verify that all processes running under the xmuser ID are stopped. First, an orderly shutdown should be attempted by running the /var/CQ/bin/xmstop.ksh script. After a reasonable timeout period all processes running under the xmuser ID should be stopped.
If there are any xmuser processes still running after a reasonable timeout period, they should be killed.
Configure the PM4Data Application Monitor
The monitor should verify the following processes are running under the PM4Data user ID (typically, xmuser):
On the Enterprise Server:
- java (2 processes with this name)
- xmodbsrv (2 processes with this name)
- xmocoord (2 processes with this name)
- xmofts (3 processes with this name)
- xmosload
- xmoscrpt
- xmodirmn
- xmoxmsrv
- xmoecsrv
- xmosqsrv
- xmoswse
- xmoqsrv
- xmoxmitq
On a node:
- java
- xmofts (3 processes with this name)
- xmoxmsrv
- xmodirmn
