This section contains the information you need to plan your Sun Cluster HA for WebSphere MQ Integrator installation and configuration.
Your data service configuration might not be supported if you do not observe these restrictions.
Consider the restrictions in this section to plan the installation and configuration of Sun Cluster HA for WebSphere MQ Integrator. This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for WebSphere MQ Integrator only.
For restrictions that apply to all data services, see the Sun Cluster Release Notes.
The Sun Cluster HA for WebSphere MQ Integrator data service can only be configured as a failover service – WebSphere MQ Integrator cannot operate as a scalable service and therefore the Sun Cluster HA for WebSphere MQ Integrator data service can only be configured to run as a failover service.
Installing WebSphere MQ Integrator onto Cluster File Systems – Initially, the WebSphere MQ Integrator product is installed into /opt/mqs and /var/mqsi.
/var/mqsi must be mounted as a Global File System with a symbolic link for /var/mqsi/locks to a Local File System. It is recommended that /opt/mqsi be on a local disk, however 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
Mount /var/mqsi as a Global File System – WebSphere MQ Integrator makes use of several directories within /var/mqsi, which needs to be available on all nodes within Sun Cluster as a Global File System. However, generated locks need to be located within a Local File System. Because of this, /var/mqsi/locks must be setup as a symbolic link to a Local File System.
It is considered best practice when mounting Global File Systems to mount them with the /global prefix and to mount Failover File Systems with the /local prefix. However, be aware that this is simply viewed as best practice.
The following example shows WebSphere MQ Integrator with /var/mqsi mounted as a Global File system through a symbolic link to /global/mqsi, with /var/mqsi/locks setup as a symbolic link to /var/mqsi_locks on the root file system, that is local disk.
# ls -l /var/mqsi lrwxrwxrwx 1 root other 12 Sep 5 15:32 /var/mqsi -> /global/mqsi # # ls -l /global/mqsi/locks lrwxrwxrwx 1 root other 15 Sep 18 15:37 /global/mqsi/locks -> /var/mqsi_locks # # df -k /global/mqsi/locks Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 12731708 5792269 6812122 46% / # # more /etc/vfstab (Subset of the output) /dev/md/dg_d6/dsk/d60 /dev/md/dg_d6/rdsk/d60 /global/mqsi ufs 4 yes logging,global |
The Sun Cluster HA for WebSphere MQ Integrator RDBMS – Currently, the Sun Cluster HA for WebSphere MQ Integratordata service can only operate with a local RDBMS, ie not a remote RDBMS, and more specifically only with DB2 and Oracle.
This restriction is because the Sun Cluster HA for WebSphere MQ Integratordata service needs to manage the restart scenarios for WebSphere MQ Integrator, namely whenever the RDBMS restarts. However, this behavior is scheduled to be enhanced at a later date and also to include Sybase support.
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.
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.
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 |
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.
# 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 |