Registering and Configuring Sun Cluster HA for WebSphere MQ Integrator

This section contains the procedures you need to configure Sun Cluster HA for WebSphere MQ Integrator.

How to Register and Configure Sun Cluster HA for WebSphere MQ Integrator

This procedure assumes that you installed the data service packages during your initial Sun Cluster installation.

If you did not install the Sun Cluster HA for WebSphere MQ Integrator packages as part of your initial Sun Cluster installation, go to How to Install the Sun Cluster HA for WebSphere MQ IntegratorPackages by Using the scinstall Utility.

The WebSphere MQ Integrator Broker component is dependent on WebSphere MQ and an RDBMS. All resources for the WebSphere MQ Integrator Broker component, WebSphere MQ components, and the RDBMS must reside within the same Resource Group. For example, refer to Example 1–2.

The WebSphere MQ Integrator UserNameServer component is dependent only on WebSphere MQ. All resources for the WebSphere MQ Integrator UserNameServer component, WebSphere MQ components and the RDBMS must reside within the same Resource Group, For example, refer toExample 1–2

Currently only local RDBMS support for DB2 or Oracle is supported. Refer to Configuration Restrictions, in particular to Sun Cluster HA for WebSphere MQ Integrator RDBMS for a description of this restriction.

Become superuser on one of the nodes in the cluster that will host WebSphere MQ Integrator.

Create a failover resource group.

# scrgadm -a -g WebSphere MQ-failover-resource-group

Create a resource for the WebSphere MQ Integrator Disk Storage.

# scrgadm -a -j WebSphere MQ Integrator-has-resource  \
-g WebSphere MQ-failover-resource-group   \
-t SUNW.HAStoragePlus  \
-x FilesystemMountPoints=WebSphere MQ Integrator- instance-mount-points

Enable the failover resource group that now includes the WebSphere MQ Integrator Disk Storage resource.
# scswitch -Z -g WebSphere MQ-failover-resource-group

Create and register each required WebSphere MQ Integrator component.

Note –

This section requires that you have installed the Sun Cluster HA for WebSphere MQ and RDBMS data services and that their resources are online within Sun Cluster. Ensure that you have done this before you continue with this step.

Perform this step for the Broker component (sib), then repeat for the optional UserNameServer component, replacing sib with:

siu - UserNameServer

# cd /opt/SUNWscmqi/sib/util

Edit the sib_config file and follow the comments within that file. For example:

# These parameters can be customized in (key=value) form
#
#        RS - name of the resource for the application
#        RG - name of the resource group containing RS
#      QMGR - name of the Queue Manager
#      PORT - name of the Queue Manager port number
#        LH - name of the LogicalHostname SC resource
#    HAS_RS - name of the Queue Manager HAStoragePlus SC resource
#    SC3_IN - name of the Test Message Flow (Inbound)
#   SC3_OUT - name of the Test Message Flow (Outbound)
#   MQSI_ID - name of the WebSphere MQI userid
#    BROKER - name of the WebSphere MQI Broker
#  RDBMS_ID - name of the WebSphere MQI RDBMS userid
#   QMGR_RS - name of the Queue Manager SC resource
#  RDBMS_RS - name of the RDBMS SC resource and listener (if Oracle)
#             e.g. RDBMS_RS=<ora-rs>,<lsr-rs>
#

The following is an example for WebSphere MQ Integrator Broker XXX, with WebSphere Integrator MQ Manager qmgr1.

RS=wmq-broker-res
RG=wmq-rg
QMGR=qmgr1
PORT=1414
LH=wmq-lh-res
HAS_RS=wmqi-has-res
SC3_IN=SC3_IN
SC3_OUT=SC3_OUT
MQSI_ID=mqsi1
BROKER=XXX
RDBMS_ID=db2
QMGR_RS=wmq-qmgr-res
RDBMS_RS=wmq-rdbms-res

After editing sib_config, you must register the resource.

# ./sib_register

Enable each WebSphere MQ Integrator resource.

Repeat this step for each WebSphere MQ Integrator component.
# scstat
# scswitch -e -j WebSphere MQ Integrator-resource