Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for WebSphere Message Broker Guide Oracle Solaris Cluster |
1. Installing and Configuring HA for WebSphere Message Broker
HA for WebSphere Message Broker Overview
Overview of Installing and Configuring HA for WebSphere Message Broker
Planning the HA for WebSphere Message Broker Installation and Configuration
Restriction for the supported configurations of 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
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 HA for WebSphere Message Broker Packages
How to Install the HA for WebSphere Message Broker Packages
Registering and Configuring HA for WebSphere Message Broker
How to Register and Configure HA for WebSphere Message Broker
Verifying the HA for WebSphere Message Broker Installation and Configuration
How to Verify the HA for WebSphere Message Broker Installation and Configuration
Upgrading HA for WebSphere Message Broker
How to Upgrade to the New Version of HA for WebSphere Message Broker
Understanding the HA for WebSphere Message Broker Fault Monitor
Probing Algorithm and Functionality
Operations of the Broker probe
Operations of the Configuration Manager probe
Operations of the UserNameServer probe
Debug HA for WebSphere Message Broker
How to turn on debug for HA for WebSphere Message Broker
A. Deployment Example: Installing WebSphere Message Broker in Zones
This section contains the procedure you need to verify the installation and configuration.
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.
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
# zlogin zonename
# su - message-broker-userid $ mqsistart message-broker
Perform this step as the message-broker-userid.
$ mqsilist
Perform this step as the message-broker-userid.
$ mqsistop -i message-broker $ exit
# exit
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
# umount websphere-message-broker-highly-available-local-file-system
Unmount the highly available local file system from the zone.
# umount /zonepath/root/websphere-message-broker-highly-available-local-file-system
# zpool export -f HAZpool
Perform this step on another node of the cluster.
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
# mount websphere-message-broker-highly-available-local-file-system
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
# zpool import -R / HAZpool
# zpool import -R /zonepath/root HAZpool
Perform this step on the other node of the cluster.
# zlogin zonename
Perform this step on the other node or zone of the cluster.
# su - message-broker-userid $ mqsistart message-broker
Perform this step as the message-broker-userid.
$ mqsilist
Perform this step as the message-broker-userid.
$ mqsistop -i message-broker $ exit
# exit
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
# umount websphere-message-broker-highly-available-local-file-system
Unmount the highly available local file system from the zone.
# umount /zonepath/root/websphere-message-broker-highly-available-local-file-system
# zpool export -f HAZpool