JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for WebSphere Message Broker Guide
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring Oracle Solaris Cluster HA for WebSphere Message Broker

Oracle Solaris Cluster HA for WebSphere Message Broker Overview

Overview of Installing and Configuring Oracle Solaris Cluster HA for WebSphere Message Broker

Planning the Oracle Solaris Cluster HA for WebSphere Message Broker Installation and Configuration

Configuration Restrictions

Restriction for the supported configurations of Oracle Solaris Cluster HA for WebSphere Message Broker

Restriction for the location of WebSphere Message Broker files

Restriction for the WebSphere Message Broker additional software

Restriction for multiple WebSphere Message Broker instances

Configuration Requirements

Determine which Solaris zone WebSphere Message Broker will use

Installing and Configuring WebSphere Message Broker

How to Install and Configure WebSphere Message Broker

Verifying the Installation and Configuration of WebSphere Message Broker

How to Verify the Installation and Configuration of WebSphere Message Broker

Installing the Oracle Solaris Cluster HA for WebSphere Message Broker Packages

How to Install the Oracle Solaris Cluster HA for WebSphere Message Broker Packages

Registering and Configuring Oracle Solaris Cluster HA for WebSphere Message Broker

How to Register and Configure Oracle Solaris Cluster HA for WebSphere Message Broker

Verifying the Oracle Solaris Cluster HA for WebSphere Message Broker Installation and Configuration

How to Verify the Oracle Solaris Cluster HA for WebSphere Message Broker Installation and Configuration

Upgrading Oracle Solaris Cluster HA for WebSphere Message Broker

How to Upgrade to the New Version of Oracle Solaris Cluster HA for WebSphere Message Broker

Understanding the Oracle Solaris Cluster HA for WebSphere Message Broker Fault Monitor

Resource Properties

Probing Algorithm and Functionality

Operations of the Broker probe

Operations of the Configuration Manager probe

Operations of the UserNameServer probe

Debug Oracle Solaris Cluster HA for WebSphere Message Broker

How to turn on debug for Oracle Solaris Cluster HA for WebSphere Message Broker

A.  Deployment Example: Installing WebSphere Message Broker in Zones

Index

Registering and Configuring Oracle Solaris Cluster HA for WebSphere Message Broker

This section contains the procedures you need to configure Oracle Solaris Cluster HA for WebSphere Message Broker.

Some procedures within this section require you to use certain Oracle Solaris Cluster commands. Refer to the relevant Oracle Solaris Cluster command man page for more information about these command and their parameters.

The Oracle Solaris Cluster HA for WebSphere Message Broker data service

How to Register and Configure Oracle Solaris Cluster HA for WebSphere Message Broker

Perform this procedure on one node of the cluster only.

This procedure assumes that you installed the data service packages during your initial Oracle Solaris Cluster installation.

If you did not install the Oracle Solaris Cluster HA for WebSphere Message Broker packages as part of your initial Oracle Solaris Cluster installation, go to How to Install the Oracle Solaris Cluster HA for WebSphere Message Broker Packages.


Note - This procedure requires that WebSphere MQ and a broker database have been installed and that the Oracle Solaris Cluster HA for WebSphere MQ data service and database data service have been registered and configured.

The registration and configuration of Oracle Solaris Cluster HA for WebSphere Message Broker must use the same resource group that WebSphere MQ and the broker database use.

You must therefore have completed the installation of the Oracle Solaris Cluster Data Service for WebSphere MQ data service and the database data service before continuing with this procedure.


  1. On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
  2. Create a resource for the WebSphere Message Broker Disk Storage.
    1. If a ZFS highly available local file system is being used.
      # clresource create -g websphere-mq-resource-group  \
      > -t SUNW.HAStoragePlus \
      > -p Zpools=websphere-message-broker-zspool \
      > websphere-message-broker-hastorage-resource

      Alternatively, you can simply add the websphere-message-broker-zspool to the existing websphere-mq-hastorage-resource.

      # clresource set \
      > -p Zpools=websphere-mq-zspools,websphere-message-broker-zspool 
      > websphere-mq-hastorage-resource
    2. If a cluster file system or a non ZFS highly available local file system is being used.
      # clresource create -g websphere-mq-resource-group  \
      > -t SUNW.HAStoragePlus \
      > -p FilesystemMountPoints=websphere-message-broker-filesystem-mountpoint \
      > websphere-message-broker-hastorage-resource

      Alternatively, you can simply add the websphere-message-broker-filesystem-mountpoint to the existing websphere-mq-hastorage-resource.

      # clresource set \
      > -p FilesystemMountPoints=mq-filesystem-mountpoints,message-broker-filesystem-mountpoint \
      > websphere-mq-hastorage-resource
  3. Enable the Disk Storage resource.
    # clresource enable websphere-message-broker-hastorage-resource
  4. Create and register a resource for the Broker.

    Edit /opt/SUNWscmqi/sib/util/sib_config and follow the comments within that file. After you have edited sib_config, you must register the resource.

    If you require the broker probe to perform a simple message flow test, you must create a message flow and specify the inbound queue in the SC3_IN variable and the outbound queue in the SC3_OUT variable.

    Refer to IBM's WebSphere Message Broker Message Flows to create a simple message flow.

    Alternatively, the default values for SC3_IN and SC3_OUT are set to NONE which will cause the broker probe to not perform a simple message flow and just check that the bipservice program is running.

    A value for the RDBMS_RS parameter is not required if WebSphere Message Broker v6 is being deployed. This implies that a remote database can be used for WebSphere Message Broker v6 and that the broker does not need to be restarted if the broker database is restarted.

    # cd /opt/SUNWscmqi/sib/util
    # vi sib_config
    # ./sib_register

    The following listing has been taken from the deployment example, Step 2, which can be found in Appendix A, Deployment Example: Installing WebSphere Message Broker in Zones and shows /opt/SUNWscmqi/sib/util/sib_config that has been edited to configure a broker resource.

    Vigor5# cat > /var/tmp/brk_config <<-EOF RS=wmq1-brk RG=wmq1-rg QMGR=qmgr1 LH=wmq1-lh HAS_RS=wmq1-ZFShas SC3_IN=NONE SC3_OUT=NONE MQSI_ID=mqsiuser BROKER=brk QMGR_RS=wmq1-qmgr RDBMS_RS= START_CMD= STOP_CMD= EOF
    Vigor5# /opt/SUNWscmqi/sib/util/sib_register -f /var/tmp/brk_config
  5. Enable the Broker resource.

    Note - Before you enable the Broker resource, ensure that /opt/mqsi exists.

    For compatibility reasons, the Oracle Solaris Cluster HA for WebSphere Message Broker data service requires that /opt/mqsi exists on all nodes or zones in the cluster.


    # clresource enable websphere-message-broker-resource
  6. (Optional) Create and register a resource for the Configuration Manager.

    Edit /opt/SUNWscmqi/sib/util/sib_config and follow the comments within that file. After you have edited sib_config, you must register the resource.

    The configuration manager resource must specify NONE for the SC3_IN and SC3_OUT variables.

    A value for the RDBMS_RS parameter is not required if WebSphere Message Broker v6 Configuration Manager is being deployed.

    # cd /opt/SUNWscmqi/sib/util
    # vi sib_config
    # ./sib_register

    The following listing has been taken from the deployment example, Step 4, which can be found in Appendix A, Deployment Example: Installing WebSphere Message Broker in Zones and shows /opt/SUNWscmqi/sib/util/sib_config that has been edited to configure a configuration manager resource.

    Vigor5# cat > /var/tmp/cmg_config <<-EOF RS=wmq1-cmg RG=wmq1-rg QMGR=qmgr1 LH=wmq1-lh HAS_RS=wmq1-ZFShas SC3_IN=NONE SC3_OUT=NONE MQSI_ID=mqsiuser BROKER=cmg QMGR_RS=wmq1-qmgr RDBMS_RS= START_CMD= STOP_CMD= EOF
    Vigor5# /opt/SUNWscmqi/sib/util/sib_register -f /var/tmp/cmg_config
  7. (Optional) Enable the Configuration Manager resource.
    # clresource enable websphere-message-broker-configuration-manager-resource
  8. (Optional) Create and register a resource for the UserNameServer.

    Edit /opt/SUNWscmqi/siu/util/siu_config and follow the comments within that file. After you have edited siu_config, you must register the resource.

    # cd /opt/SUNWscmqi/siu/util
    # vi siu_config
    # ./siu_register

    The following listing has been taken from the deployment example, Step 6, which can found in Appendix A, Deployment Example: Installing WebSphere Message Broker in Zones and shows /opt/SUNWscmqi/siu/util/siu_config that has been edited to configure a UserNameServer resource.

    Vigor5# cat > /var/tmp/cmg_config <<-EOF RS=wmq1-uns RG=wmq1-rg QMGR=qmgr1 LH=wmq1-lh HAS_RS=wmq1-ZFShas MQSI_ID=mqsiuser QMGR_RS=wmq1-qmgr START_CMD= STOP_CMD= EOF
    Vigor5# /opt/SUNWscmqi/siu/util/siu_register -f /var/tmp/uns_config
  9. (Optional) Enable the UserNameServer resource.
    # clresource enable websphere-message-broker-usernameserver-resource