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

Document Information

Preface

1.  Installing and Configuring Solaris Cluster HA for WebSphere MQ

A.  Deployment Example: Installing a WebSphere MQ Queue Manager in Non-Global Zones

Target Cluster Configuration

Software Configuration

Assumptions

Installing and Configuring WebSphere MQ

Example: Prepare the Cluster for WebSphere MQ

Example: Configure two Non-Global Zones

Example: Install WebSphere MQ in the Non-Global Zones

Example: Verify WebSphere MQ

Example: Configure Cluster Resources for WebSphere MQ

Example: Enable the WebSphere MQ Software to Run in the Cluster

Example: Verify the HA for WebSphere MQ Resource Group

Example: Creating Multiple Instances

B.  Deployment Example: Installing aWebSphere MQ Queue Manager in an HA Container

Index

Example: Configure two Non-Global Zones

Perform all steps within this example in the global zone.

  1. On local storage create a directory for the non-global zones root path.
    Vigor5# mkdir /zones
  2. Create a temporary file for the whole root zones, for example /tmp/z1 and /tmp/z2, and include the following entries:
    Vigor5# cat > /tmp/z1 <<-EOF create -b set zonepath=/zones/z1 EOF
    Vigor5# cat > /tmp/z2 <<-EOF create -b set zonepath=/zones/z2 EOF
  3. Configure the non-global zones, using the files you created.
    Vigor5# zonecfg -z z1 -f /tmp/z1
    Vigor5# zonecfg -z z2 -f /tmp/z2
  4. Install the zones.

    Open two windows and issue the following command in each window.

    Vigor5# zoneadm -z z1 install
    Vigor5# zoneadm -z z2 install
  5. Boot the zones.

    Perform this step after the installation of the zones are complete.

    Vigor5# zoneadm -z z1 boot
    Vigor5# zoneadm -z z2 boot
  6. Log in to the zones and complete the zone system identification.
    Vigor5# zlogin -C z1
    Vigor5# zlogin -C z2
  7. Close the terminal window and disconnect from the zone consoles.

    After you have completed the zone system identification, disconnect from the window your previously opened.

    Vigo5# ~.
  8. Create the appropriate mount points and symlinks for the queue manager in the zone.
    Vigor5# zlogin z1 mkdir -p /var/mqm/log /var/mqm/qmgrs
    Vigor5# zlogin z1 ln -s /ZFSwmq1/log /var/mqm/log/qmgr1
    Vigor5# zlogin z1 ln -s /ZFSwmq1/qmgrs /var/mqm/qmgrs/qmgr1
    Vigor5#
    Vigor5# zlogin z2 mkdir -p /var/mqm/log /var/mqm/qmgrs
    Vigor5# zlogin z2 ln -s /ZFSwmq1/log /var/mqm/log/qmgr1
    Vigor5# zlogin z2 ln -s /ZFSwmq1/qmgrs /var/mqm/qmgrs/qmgr1
  9. Create the WebSphere MQ userid in the zones.
    Vigor5# zlogin z1 groupadd -g 1000 mqm
    Vigor5# zlogin z1 useradd -u 1000 -g 1000 -d /var/mqm mqm
    Vigor5#
    Vigor5# zlogin z2 groupadd -g 1000 mqm
    Vigor5# zlogin z2 useradd -u 1000 -g 1000 -d /var/mqm mqm
  10. Add the logical host name to /etc/hosts and /etc/inet/ipnodes in the zones.

    The following output shows the logical host name entry for qmgr1 in zones z1 and z2.

    Vigor5# zlogin z1 grep qmgr1 /etc/hosts /etc/inet/ipnodes
    192.168.1.150    qmgr1
    Vigor5# zlogin z2 grep qmgr1 /etc/hosts /etc/inet/ipnodes
    /etc/hosts:192.168.1.150    qmgr1
    /etc/inet/ipnodes:192.168.1.150    qmgr1