Configuration Requirements (Sun Cluster 3.1 Data Service for WebSphere MQ Integrator Guide)

Sun Cluster 3.1 Data Service for WebSphere MQ Integrator Guide

Configuration Requirements

Caution –

Your data service configuration might not be supported if you do not adhere to these requirements.

Use the requirements in this section to plan the installation and configuration of Sun Cluster HA for WebSphere MQ Integrator. These requirements apply to Sun Cluster HA for WebSphere MQ Integrator only. You must meet these requirements before you proceed with your Sun Cluster HA for WebSphere MQ Integrator installation and configuration.

WebSphere MQ Integrator components and their dependencies —The Sun Cluster HA for WebSphere MQ Integrator data service can be configured to protect a WebSphere MQ Integrator Broker and UserNameServer. These components and their dependencies are briefly described below.

Table 1–3 WebSphere MQ Integrator components and their dependencies (via -> symbol)


Componet	Description
Broker`(Mandatory)`	-> SUNW.HAStoragePlus resource -> WebSphere MQ Queue Manager and Listener resources -> RDBMS resource The SUNW.HAStoragePlus resource manages the WebSphere MQ Integrator File System Mount point, ie `/global/mqsi`. Dependency on the WebSphere MQ Queue Manager resource ensures that the WebSphere MQ Queue Manager is available. Dependency on the WebSphere MQ Listener resource is only required if runmqlsr is used instead of inetd. Dependency on the RDBMS resource ensures that the RDBMS is available. All these dependencies ensure that WebSphere MQ Integrator is not started until these services are available.
UserNameServer`(Optional)`	-> SUNW.HAStoragePlus resource -> WebSphere MQ Queue Manager and Listener resources The SUNW.HAStoragePlus resource manages the WebSphere MQ Integrator File System Mount point, ie `/global/mqsi`. Dependency on the WebSphere MQ Queue Manager resource ensures that the WebSphere MQ Queue Manager is available. Dependency on the WebSphere MQ Listener resource is only required if runmqlsr is used instead of inetd.

The WebSphere MQ Integrator Broker component and its dependencies must all reside within the same Resource Group. Likewise the WebSphere MQ Integrator UserNameServer and its dependencies must also all reside with the same Resource Group.

However, the WebSphere MQ Integrator Broker and UserNameServer do not have to reside within the same Resource Group, they can reside in separate Resource Groups. Likewise, multiple instances of the WebSphere MQ Integrator Broker can reside in separate Resource Groups. However, only one instance of the WebSphere MQ Integrator UserNameServer is allowed.

Example 1–2 Multiple WebSphere MQ Integrator Brokers and UserNameServer .

The following example shows two WebSphere MQ Integrator Brokers (XXXand YYY) and a WebSphere MQ Integrator UserNameServer within different Resource Groups.

The example also shows that all WebSphere MQ Integrator components (Broker and UserNameServer) use the same Global File System /global/mqsi.

Note –

The file system mount points for DB2 and Oracle in the example that follows are simply examples. For a discussion of the advantages and disadvantages of installing the software on local versus cluster file system, see “Determining the Location of the Application Binaries” on page 3 of the Sun Cluster Data Services Installation and Configuration Guide.

Resource Group 1 — with the following resources

SUNW.HAStoragePlus resource with
 -x FilesystemMountPoints=/local/db2,/global/mqm,/global/mqsi,
    /local/mqm/qmgrs/qmgr1,/local/mqm/log/qmgr1
RDBMS resource for DB2
WebSphere MQ resource for Queue Manager qmgr1
WebSphere MQ Integrator resource for Broker XXX

Resource Group 2— with the following resources

SUNW.HAStoragePlus resource with
 -x FilesystemMountPoints=/global/mqm,/global/mqsi
 -x AffinityOn=FALSE
SUNW.HAStoragePlus resource with
 -x FilesystemMountPoints=/local/oracle,
    /local/mqm/qmgrs/qmgr2,/local/mqm/log/qmgr2
RDBMS resource for Oracle
RDBMS resource for Oracle Listener
WebSphere MQ resource for Queue Manager qmgr2
WebSphere MQ Integrator resource for Broker YYY

Resource Group 3— with the following resources

SUNW.HAStoragePlus resource with
 -x FilesystemMountPoints=/global/mqm,/global/mqsi
 -x AffinityOn=FALSE
SUNW.HAStoragePlus resource with
 -x FilesystemMountPoints=/local/mqm/qmgrs/qmgr3,/local/mqm/log/qmgr3
WebSphere MQ resource for Queue Manager qmgr3
WebSphere MQ Integrator resource for UserNameServer

Note –

For more detailed information about these WebSphere MQ Integrator components, refer to IBM's WebSphere MQ Integrator Introduction and Planning manual.

Each WebSphere MQ Integrator component has a configuration and registration file under, /opt/SUNWscmqi/xxx/util, where xxx is a three character abbreviation for the respective WebSphere MQ Integrator component. These files allow you to register the WebSphere MQ Integrator components with Sun Cluster.

Within these files, the appropriate dependencies have already been applied.

Example 1–3 WebSphere MQ Integrator configuration and registration file for Sun Cluster

# cd /opt/SUNWscmqi
# 
# ls -l sib/util
total 6
-rwxr-xr-x   1 root     sys         1032 Dec 20 14:44 sib_config
-rwxr-xr-x   1 root     sys          720 Dec 20 14:44 sib_register
# 
# ls -l siu/util
-rwxr-xr-x   1 root     sys          733 Dec 20 14:44 siu_config
-rwxr-xr-x   1 root     sys          554 Dec 20 14:44 siu_register 
# 
# more sib/util/*
::::::::::::::
sib/util/sib_config
::::::::::::::
#
# 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>
#

RS=
RG=
QMGR=
PORT=
LH=
HAS_RS=
SC3_IN=
SC3_OUT=
MQSI_ID=
BROKER=
RDBMS_ID=
QMGR_RS=
RDBMS_RS=
::::::::::::::
sib/util/sib_register
::::::::::::::
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#

. `dirname $0`/sib_config

scrgadm -a -j $RS -g $RG -t SUNW.gds \
-x Start_command="/opt/SUNWscmqi/sib/bin/start-broker \
-R $RS -G $RG -Q $QMGR -I $SC3_IN -O $SC3_OUT \
-U $MQSI_ID -B $BROKER -D $RDBMS_ID " \
-x Stop_command="/opt/SUNWscmqi/sib/bin/stop-broker \
-R $RS -G $RG -Q $QMGR -I $SC3_IN -O $SC3_OUT \
-U $MQSI_ID -B $BROKER -D $RDBMS_ID " \
-x Probe_command="/opt/SUNWscmqi/sib/bin/test-broker \
-R $RS -G $RG -Q $QMGR -I $SC3_IN -O $SC3_OUT \
-U $MQSI_ID -B $BROKER -D $RDBMS_ID " \
-y Port_list=$PORT/tcp -y Network_resources_used=$LH \
-x Stop_signal=9 \
-y Resource_dependencies=$HAS_RS,$QMGR_RS,$RDBMS_RS