Verifying the Installation and Configuration of WebSphere Message Broker

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

How to Verify the Installation and Configuration of WebSphere Message Broker

This procedure does not verify that your application is highly available because you have not yet installed your data service.

Perform this procedure on one node or zone of the cluster unless a specific step indicates otherwise.

1. Ensure the zone is booted, if a zone is being used.

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

   Boot the zone if it is not running.

   # zoneadm list -v # zoneadm -z zonename boot

2. Login to the zone, if a zone is being used.

   # zlogin zonename

3. Start the WebSphere Message Broker, Configuration Manager or UserNameServer.

   # su - message-broker-userid $ mqsistart message-broker

4. List all WebSphere Message Brokers that are running.

   Perform this step as the message-broker-userid.

   $ mqsilist

5. Stop the WebSphere Message Broker, Configuration Manager or UserNameServer.

   Perform this step as the message-broker-userid.

   $ mqsistop -i message-broker $ exit

6. Logout from the zone, if a zone is being used.

   # exit

7. Unmount the highly available local file system.

   Perform this step in the global zone only.

   You should unmount the highly available file system you mounted in Step 7 in How to Install and Configure WebSphere Message Broker

   1. If a non 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.

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

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

         Unmount the highly available local file system from the zone.

         # umount /zonepath/root/websphere-message-broker-highly-available-local-file-system

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

      # zpool export -f HAZpool

8. Relocate the shared storage to other node.

   Perform this step on another node of the cluster.

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

      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.

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

         # zlogin zonename mkdir websphere-message-broker-highly-available-local-file-system # # 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 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

9. Login to the zone, if a zone is being used.

   Perform this step on the other node of the cluster.

   # zlogin zonename

10. Start the WebSphere Message Broker, Configuration Manager or UserNameServer.

    Perform this step on the other node or zone of the cluster.

    # su - message-broker-userid $ mqsistart message-broker

11. List all WebSphere Message Brokers that are running.

    Perform this step as the message-broker-userid.

    $ mqsilist

12. Stop the WebSphere Message Broker, Configuration Manager or UserNameServer.

    Perform this step as the message-broker-userid.

    $ mqsistop -i message-broker $ exit

13. Logout from the zone, if a zone is being used.

    # exit

14. Unmount the highly available local file system.

    Perform this step in the global zone only.

    You should unmount the highly available file system you mounted in Step 7 in How to Install and Configure WebSphere Message Broker

    1. If a non 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.

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

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

          Unmount the highly available local file system from the zone.

          # umount /zonepath/root/websphere-message-broker-highly-available-local-file-system

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

       # zpool export -f HAZpool