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 Integrator Packages using the scinstall Utility.

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

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

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.

Steps

Become superuser on one of the nodes in the cluster that will host Sun Cluster.

Create a failover resource group.

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

Create a resource for the Sun Cluster Disk Storage.

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

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

Create and register each required Sun Cluster 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:

#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
# 
# This file will be sourced in by sib_register and the parameters
# listed below will be used.
#
# 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>
#
#       +++ Optional parameters +++
#
# START_CMD - pathname and name of the renamed strmqm program
#  STOP_CMD - pathname and name of the renamed endmqm program
#
#
# Note 1: Optional parameters
#
#       Null entries for optional parameters are allowed if not used.
#
# Note 2: Renamed strmqm/endmqm programs
#       
#       This is only recommended if WebSphere MQ is deployed onto 
#       Global File Systems for qmgr/log files. You should specify 
#       the full pathname/program, i.e. /opt/mqm/bin/<renamed_strmqm>
#
#

The following is an example for Sun Cluster 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
START_CMD=
STOP_CMD=

After editing sib_config, you must register the resource.

# ./sib_register

Enable each Sun Cluster resource.

Repeat this step for each Sun Cluster component.
# scstat
# scswitch -e -j Sun Cluster-resource