test

Sun Cluster Data Service for WebSphere MQ Integrator Guide for Solaris OS

Installing and Configuring Sun Cluster HA for WebSphere MQ Integrator

Installing and Configuring Sun Cluster HA for WebSphere MQ Integrator

Table 1–1 lists the tasks for installing and configuring Sun Cluster HA for WebSphere MQ Integrator. Perform these tasks in the order that they are listed.

Table 1–1 Task Map: Installing and Configuring Sun Cluster HA for WebSphere MQ Integrator

Task 

For Instructions, Go To 

Plan the installation 

Sun Cluster HA for WebSphere MQ Integrator Overview

Planning the Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration

Install and configure WebSphere MQ Integrator 

How to Install and Configure WebSphere MQ Integrator

Verify installation and configuration 

How to Verify the Installation and Configuration of WebSphere MQ Integrator

Install Sun Cluster HA for WebSphere MQ Integrator Packages 

How to Install the Sun Cluster HA for WebSphere MQ IntegratorPackages by Using the scinstall Utility

Register and Configure Sun Cluster HA for WebSphere MQ Integrator 

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

Verify Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration 

How to Verify the Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration

Understand Sun Cluster HA for WebSphere MQ Integrator fault monitor 

Understanding Sun Cluster HA for WebSphere MQ Integrator Fault Monitor

Debug Sun Cluster HA for WebSphere MQ Integrator 

Debug Sun Cluster HA for WebSphere MQ Integrator

Sun Cluster HA for WebSphere MQ Integrator Overview

WebSphere MQ Integrator works with WebSphere MQ messaging, extending its basic connectivity and transport capabilities to provide a powerful message broker solution. Messages are formed, routed, and transformed according to the rules defined by an easy-to-use graphical user interface (GUI).

The Sun Cluster HA for WebSphere MQ Integrator data service provides a mechanism for orderly startup and shutdown, fault monitoring and automatic failover for the WebSphere MQ Integrator service. The WebSphere MQ Integrator components are protected by the Sun Cluster HA for WebSphere MQ Integrator data service.

Table 1–2 Protection of Components

Component 

Protected by 

Broker 

Sun Cluster HA for WebSphere MQ Integrator 

User Name Server 

Sun Cluster HA for WebSphere MQ Integrator 

Planning the Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration

This section contains the information you need to plan your Sun Cluster HA for WebSphere MQ Integrator installation and configuration.

Configuration Restrictions

This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for WebSphere MQ Integrator only.

Caution – Caution –

Your data service configuration might not be supported if you do not observe these restrictions.

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

Configuration Requirements

Use the requirements in this section to 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.

Caution – Caution –

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

Installing and Configuring WebSphere MQ Integrator

How to Install and Configure WebSphere MQ Integrator

Use this procedure to install and configure WebSphere MQ Integrator.

Note –

For this section, follow IBM's WebSphere MQ Integrator for Sun Solaris — Installation Guide to install and create a Broker and UserNameServer.

  1. Mount the WebSphere MQ Integrator Cluster File Systems.

    Before installing WebSphere MQ Integrator within Sun Cluster, ensure that the Cluster File System /var/mqsi, or /global/mqsi if you have setup a symbolic link, is mounted as a Global File System.

  2. Install WebSphere MQ Integrator onto all nodes within Sun Cluster.

    It is recommended that you install WebSphere MQ Integrator binaries onto local disks on /opt/mqsi. 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.

  3. Create your WebSphere MQ Integrator Broker.

    After you have installed WebSphere MQ Integrator onto all nodes within Sun Cluster that will run WebSphere MQ Integrator, create your WebSphere MQ Integrator Broker.

Verifying the Installation and Configuration of WebSphere MQ Integrator

This section contains the procedure you need to verify the installation and configuration.

Note –

Refer to IBM's WebSphere MQ Intercommunication and IBM's WebSphere MQ Command Reference manuals to create queues and channels for communication between the Broker(s) and UserNameServer within Sun Cluster and the Configuration Manager on Windows NT.

How to Verify the Installation and Configuration of WebSphere MQ Integrator

Use this procedure to verify the installation and configuration. This procedure does not verify that your application is highly available because you have not installed your data service yet.

Note –

The Sun Cluster HA for WebSphere MQ Integrator data service requires that a message flow has been setup within the Broker.

This section requires that the WebSphere MQ queue manager Logical Hostname IP address be available. This should have been setup if you have completed the Sun Cluster HA for IBM WebSphere MQ data service installation. Ensure that you have completed the installation of the Sun Cluster HA for IBM WebSphere MQ data service before you continue with the next steps.

  1. Create the communication links between the Broker queue manager and Configuration Manager queue manager.

    Set up queues and channels between the Broker queue manager(s) and the Configuration Manager queue manager, so that the message flows and rules setup on the Configuration Manager can be deployed from the Configuration Manager to the Broker queue manager(s) within Sun Cluster.

    See Chapter 4 in IBM's WebSphere MQ Integrator for Sun Solaris — Installation Guide. Refer to the section Starting your broker domain.

  2. Create the communication links between the Broker queue manager and UserNameServer (UNS) queue manager.

    If you are using a UNS, then you need to setup queues and channels between the Broker queue manager(s) and the UserNameServer.

  3. Test the communication links between the queue managers.

    After you setup all queues and channels between the Broker, UserNameServer and Configuration Manager, test that all the queue managers can communicate with each other.

  4. Create and deploy a message flow on the Configuration Manager.

    After you setup and test all queues between the Broker, UserNameServer and Configuration Manager, create a message flow and deploy it to the Broker queue manager. You will need a separate message flow for each Broker queue manager.

    1. Create a message flow.

      Create a simple message flow, that uses two queues, to receive a message from an input queue and put it to an output queue. Within the Control Center on Windows NT, you can use the IBMPrimitives MQInputand MQOutput to achieve this message flow.

      See Chapter 5 — Verifying your installation within IBM's WebSphere MQ Integrator for Sun Solaris — Installation Guide . In particular, refer to the section Building and using a message flow.

    2. Deploy the message flow to the broker.

      Note –

      The message flow and message flow queues that you create will be used by the Sun Cluster HA for WebSphere MQ Integrator data service to probe WebSphere MQ Integrator Broker.

Installing the Sun Cluster HA for WebSphere MQ Integrator Packages

If you did not install the Sun Cluster HA for WebSphere MQ Integrator packages during your Sun Cluster installation, perform this procedure to install the packages. Perform this procedure on each cluster node where you are installing the Sun Cluster HA for WebSphere MQ Integrator packages. To complete this procedure, you need the Sun Java Enterprise System Accessory CD Volume 3.

If you are installing more than one data service simultaneously, perform the procedure in “Installing the Software” in Sun Cluster 3.1 10/03 Software Installation Guide.

Install the Sun Cluster HA for WebSphere MQ Integrator packages using one of the following installation tools:

Note –

The Web Start program is not available in releases earlier than Sun Cluster 3.1 Data Services 10/03.

How to Install the Sun Cluster HA for WebSphere MQ IntegratorPackages Using the Web Start Program

You can run the Web Start program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the Web Start program, see the installer(1M) man page.

  1. Become superuser on the cluster node where you are installing the Sun Cluster HA for WebSphere MQ Integrator packages.

  2. (Optional) If you intend to run the Web Start program with a GUI, ensure that your DISPLAY environment variable is set.

  3. Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

    If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

  4. Change to the Sun Cluster HA for WebSphere MQ Integrator component directory of the CD-ROM.

    The Web Start program for the Sun Cluster HA for WebSphere MQ Integrator data service resides in this directory.


    # cd /cdrom/cdrom0/components/SunCluster_HA_MQI_3.1

  5. Start the Web Start program.


    # ./installer

  6. When you are prompted, select the type of installation.

    • To install only the C locale, select Typical.

    • To install other locales, select Custom.

  7. Follow instructions on the screen to install the Sun Cluster HA for WebSphere MQ Integrator packages on the node.

    After the installation is finished, the Web Start program provides an installation summary. This summary lets you view logs that the Web Start program created during the installation. These logs are located in the /var/sadm/install/logs directory.

  8. Exit the Web Start program.

  9. Unload the Sun Java Enterprise System Accessory CD Volume 3 from the CD-ROM drive.

    1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.

    2. Eject the CD-ROM.


      # eject cdrom

How to Install the Sun Cluster HA for WebSphere MQ IntegratorPackages by Using the scinstall Utility

You need the Sun Java Enterprise System Accessory CD Volume 3 to perform this procedure. This procedure assumes that you did not install the data service packages during your initial Sun Cluster installation.

If you installed the Sun Cluster HA for WebSphere MQ Integrator packages as part of your initial Sun Cluster installation, proceed to Registering and Configuring Sun Cluster HA for WebSphere MQ Integrator.

Perform this procedure on all nodes that can run Sun Cluster HA for WebSphere MQ Integrator data service.

  1. Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

  2. Run the scinstall utility with no options.

    This step starts the scinstall utility in interactive mode.

  3. Choose the menu option, Add Support for New Data Service to This Cluster Node.

    The scinstall utility prompts you for additional information.

  4. Provide the path to the Sun Java Enterprise System Accessory CD Volume 3.

    The utility refers to the CD as the “data services cd.”

  5. Specify the data service to install.

    The scinstall utility lists the data service that you selected and asks you to confirm your choice.

  6. Exit the scinstall utility.

  7. Unload the CD from the drive.

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.

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

  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 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

  6. Enable the failover resource group that now includes the WebSphere MQ Integrator Disk Storage resource.


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

  7. 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

  8. Enable each WebSphere MQ Integrator resource.

    Repeat this step for each WebSphere MQ Integrator component.


    # scstat 


    # scswitch -e -j WebSphere MQ Integrator-resource

Verifying the Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration

This section contains the procedure you need to verify that you installed and configured your data service correctly.

How to Verify the Sun Cluster HA for WebSphere MQ Integrator Installation and Configuration

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

  2. Ensure all the WebSphere MQ Integrator resources are online with scstat.


    # scstat

    For each WebSphere MQ Integrator resource that is not online, use the scswitch command as follows.


    # scswitch -e -j WebSphere MQ Integrator- resource

  3. Run the scswitch command to switch the WebSphere MQ Integrator resource group to another cluster node, such as node2.


    # scswitch -z -g WebSphere MQ Integrator-failover-resource-group -h node2

Understanding Sun Cluster HA for WebSphere MQ Integrator Fault Monitor

This section describes the Sun Cluster HA for WebSphere MQ Integrator fault monitor's probing algorithm or functionality, states the conditions, messages, and recovery actions associated with unsuccessful probing.

For conceptual information on fault monitors, see the Sun Cluster Concepts Guide.

Resource Properties

Sun Cluster HA for WebSphere MQ Integrator fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.

Probing Algorithm and Functionality

Debug Sun Cluster HA for WebSphere MQ Integrator

Sun Cluster HA for WebSphere MQ Integrator can be used by multiple WebSphere MQ Integrator instances. However, it is possible to turn on debug for all WebSphere MQ Integrator instances or for a particular WebSphere MQ Integrator instance.

Each WebSphere MQ Integrator component has a DEBUG file under /opt/SUNWscmqi/xxx/etc, where xxx is a three-character abbreviation for the respective WebSphere MQ Integrator component.

These files allow you to turn on debug for all WebSphere MQ Integrator instances or for a specific WebSphere MQ Integrator instance on a particular node with Sun Cluster. If you require debug to be turned on for Sun Cluster HA for WebSphere MQ Integrator across the whole Sun Cluster, you will need to repeat these steps on all nodes within Sun Cluster.

How to turn on debug forSun Cluster HA for WebSphere MQ Integrator

  1. Edit /etc/syslog.conf and change daemon.notice to daemon.debug 


    # grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                     operator
#

    Change the daemon.notice to daemon.debug and restart syslogd. The output below, from the command grep daemon /etc/syslog.conf, shows that daemon.debug has been set.


    # grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.debug;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                    operator
#
# pkill -1 syslogd
#

  2. Edit /opt/SUNWscmqi/sib/etc/config

    Perform this step for the Broker component (sib), then repeat for the optional UserNameServer (siu) that requires debug output, on each node of Sun Cluster.

    Edit /opt/SUNWscmqi/sib/etc/config and change DEBUG= to DEBUG=ALL or DEBUG=resource 


    # cat /opt/SUNWscmqi/sib/etc/config
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# Usage:
#       DEBUG=<RESOURCE_NAME> or ALL
#
DEBUG=ALL
#
    Note –

    To turn off debug, reverse the steps above.