test

Sun Cluster Data Service for WebSphere Message Broker Guide for Solaris OS

ProcedureHow to Install and Configure WebSphere Message Broker

This section contains the procedures you need to install and configure WebSphere Message Broker.

  1. Determine how many WebSphere Message Broker instances will be used.

    Refer to Restriction for multiple WebSphere Message Broker instances for more information.

  2. Determine which Solaris zone to use.

    Refer to Determine which Solaris zone WebSphere Message Broker will use for more information.

  3. If a zone will be used, create the whole root zone.

    Refer to System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for complete information about installing and configuring a zone.

    Note –

    When creating a zone for use by the cluster, autoboot=true must be used.

  4. If a zone is being used, ensure the zone is booted.

    Repeat this step on all nodes of the cluster if a zone is being used.

    Boot the zone if it is not running.


    # zoneadm list -v
# zoneadm -z zonename boot

  5. Determine how WebSphere Message Broker should be deployed in the cluster.

    The WebSphere Message Broker files can be deployed onto a cluster file system or highly available file system in the cluster. The following discussion will help you determine the correct approach to take.

    Within this section, a single instance or multiple instances of WebSphere Message Broker will be considered within a global zone or zone.

    In each scenario, file system options for the WebSphere Message Broker files (/var/mqsi) will be listed together with a recommendation where appropriate.

    1. Single Instance of WebSphere Message Broker

      1. Global zone deployment

        /var/mqsi

        Can be deployed on a cluster file system, however you are recommend to deploy on a highly available local file system.

      2. Zone deployment

        /var/mqsi

        Must be deployed on a highly available local file system.

    2. Multiple Instances of WebSphere Message Broker

      1. Global zone deployment

        /var/mqsi

        Must be deployed on a cluster file system.

      2. Zone deployment

        /var/mqsi

        Must be deployed on a highly available local file system.

    Note –

    Refer to Appendix A, Deployment Example: Installing WebSphere Message Broker in Zones for Deployment Example: Installing a WebSphere Message Broker in zones for an example on how to set up the WebSphere Message Broker files.

  6. Create a cluster file system or highly available local file system for the WebSphere Message Broker files.

    Within this step you will create a file system for the WebSphere Message Broker files (/var/mqsi). Once you have determined how WebSphere Message Broker should be deployed in the cluster, you can choose one of the sub steps below.

    • Create the WebSphere Message Broker files on a cluster file system by using Step a.

    • Create the WebSphere Message Broker files on a highly available local file systems by using Step b.

    1. WebSphere Message Broker files on a cluster file system.

      Within this deployment:

      • The WebSphere Message Broker files (/var/mqsi) are deployed on a cluster file system.

      • However, /var/mqsi/local or /var/mqsi/common/local requires a symbolic link to a local file system. This is required as WebSphere Message Broker generates specific locks that require the locks directory to be located on local storage within each node.

        If WebSphere Business Integration Message Broker v5 is being deployed you must create a symbolic link for /var/mqsi/locks to a local file system, e.g. /local/mqsi/locks on each node in the cluster.

        If WebSphere Message Broker v6 is being deployed you must create a symbolic link for /var/mqsi/common/locks to a local file system, e.g. /local/mqsi/locks on each node in the cluster.

    2. WebSphere Message Broker files on a highly available local file system.

      Within this deployment:

      • The WebSphere Message Broker files (/var/mqsi) are deployed on a highly available local file system.

      • Highly available local file systems can include the Zettabyte File System (ZFS).

      • A symbolic link for the locks directory is not required, regardless if you are deploying WebSphere Business Integration Message Broker v5 or WebSphere Message Broker v6.

  7. Mount the highly available local file system

    Perform this step on one node of the cluster.

    1. If a non ZFS highly available local file system is being used for the WebSphere Message Broker.

      Ensure the node has ownership of the disk set or disk group.

      For Solaris Volume Manager.


      # metaset -s disk-set -t

      For Veritas Volume Manager.


      # vxdg -C import disk-group
# vxdg -g disk-group startall

      1. If the global zone is being used for WebSphere Message Broker.


        # mount websphere-message-broker-highly-available-local-file-system

      2. If a zone is being used for WebSphere Message Broker.

        Create the mount point on all zones of the cluster that are being used for WebSphere Message Broker.


        # zlogin zonename mkdir websphere-message-broker-highly-available-local-file-system

        Mount the highly available local file system on one of the zones being used.


        # mount -F lofs websphere-message-broker-highly-available-local-file-system \
> /zonepath/root/websphere-message-broker-highly-available-local-file-system

    2. If a ZFS highly available local file system is being used for WebSphere Message Broker.

      1. If the global zone is being used for WebSphere Message Broker.


        # zpool import -R / HAZpool

      2. If a zone is being used for WebSphere Message Broker.


        # zpool import -R /zonepath/root HAZpool
        Note –

        If you are repeating this step to mount the ZFS highly available local file system on another node or zone before installing the WebSphere Message Broker software, you must first export the ZFS pool from the node that currently has the ZFS pool imported.

        To export the ZFS pool, issue the following,


        # zpool export -f HAZpool

  8. Install WebSphere Message Broker on all nodes or zones of the cluster.

    After you have created and mounted the appropriate file system for the WebSphere Message Broker files, you must install WebSphere Message Broker on each node of the cluster, either in the global zone or zone as required.

    For compatibility reasons, the Sun Cluster HA for WebSphere Message Broker data service requires that /opt/mqsi exists on all nodes or zones in the cluster, even if WebSphere Message Broker v6 is being deployed. Therefore you must create the directory /opt/mqsi.

    Follow IBM's WebSphere Message Broker Installation Guide to install WebSphere Message Broker.

    Note –

    If the WebSphere Message Broker files will use a highly available local file system, you will need to mount the highly available local file system on each node or zone before installing the WebSphere Message Broker software.

    Repeat Step 7 as required.

  9. Ensure that WebSphere MQ and the appropriate database are running.

    WebSphere Message Broker requires that a queue manager and appropriate database are running when creating a Broker, Configuration Manager or UserNameServer. You must ensure that the queue manger and database are running on the node where you will create a Broker, Configuration Manager or UserNameServer.

  10. Create the WebSphere Message Broker, Configuration Manager or UserNameServer as required.

    Follow IBM's WebSphere Message Broker Installation Guide to create a WebSphere Message Broker.