test

Sun Cluster 3.1 Data Service for WebSphere MQ Guide

Registering and Configuring Sun Cluster HA for WebSphere MQ

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

How to Register and Configure Sun Cluster HA for WebSphere MQ

Use this procedure to configure Sun Cluster HA for WebSphere MQ as a failover data service. 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 packages as part of your initial Sun Cluster installation, go to How to Install the Sun Cluster HA for WebSphere MQ Packages by Using the scinstall Utility.

Otherwise, use this procedure to configure the Sun Cluster HA for WebSphere MQ data service.

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

  2. Register the SUNW.gds resource type.


    # scrgadm -a -t SUNW.gds

  3. Register the SUNW.HAStoragePlus resource type.


    # scrgadm -a -t SUNW.HAStoragePlus

  4. Create a failover resource group .


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

  5. Create a resource for the WebSphere MQ Disk Storage.


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

  6. Create a resource for the WebSphere MQ Logical Hostname.


    # scrgadm -a -L -j WebSphere MQ-lh-resource  \
-g WebSphere MQ-failover-resource-group  \
-l WebSphere MQ-logical-hostname

  7. Enable the failover resource group that now includes the WebSphere MQ Disk Storage and Logical Hostname resources.


    # scswitch -Z -g WebSphere MQ-failover-resource-group

  8. Create and register each required WebSphere MQ component.

    Perform this step for the Queue Manager component (mgr), then repeat for each of the optional WebSphere MQ components that are used, replacing mgr with one of the following,

    chi - Channel Initiator

    csv - Command Server

    Note –

    The lsr component allows for multiple ports. To specify multiple ports you must specify multiple port numbers separated by / for each port entry required for the PORT parameter within /opt/SUNWscmqs/lsr/util/lsr_config. This will cause the lsr component to start multiple runmqlsr programs for different port entries. However, if multiple port entries are required, before running /opt/SUNWscmqs/lsr/util/lsr_register you must amend the PORT_LIST entry within the lsr_register file to only contain one port number, for example PORT_LIST=1414/tcp. This will be fixed in subsequent releases.

    lsr - Dedicated Listener

    Note –

    The trm component allows for multiple trigger monitors. To specify multiple trigger monitors you must specify file for the TRMQ parameter within /opt/SUNWscmqs/trm/util/trm_config before you run /opt/SUNWscmqs/trm/util/trm_register. This will cause the trm component to start multiple trigger monitor entries from /opt/SUNWscmqs/trm/etc/<qmgr>_trm_queues, which must contain trigger monitor queue names, where <qmgr> is the name of your Queue Manager. This file is required on each node within Sun Cluster that will run Sun Cluster HA for WebSphere MQ, alternatively this could be a symbolic link to a Global File System.

    trm - Trigger monitor


    # cd /opt/SUNWscmqs/mgr/util

    Edit the mgr_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
#

    The following is an example for WebSphere MQ Manager qmgr1.


    RS=wmq-qmgr-res
RG=wmq-rg
QMGR=qmgr1
PORT=1414
LH=wmq-lh-res
HAS_RS=wmq-has-res

    After editing mgr_config you must now register the resource.


    # ./mgr_register

  9. Enable WebSphere MQ Manager protection (if required).

    You should only implement WebSphere MQ Manager protection if you have deployed WebSphere MQ onto a Global File System. Refer back to Configuration Requirements for more details to implement WebSphere MQ Manager protection and in particular to Example 1–5. Otherwise skip to the next step.

    Furthermore, you must repeat this on each node within Sun Cluster that will host Sun Cluster HA for WebSphere MQ.

  10. Enable each WebSphere MQ resource.

    Repeat this step for each WebSphere MQ component as in the previous step.


    # scstat 


    # scswitch -e -j WebSphere MQ-resource