Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for WebSphere Message Broker Guide |
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
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 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
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
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
This section contains the procedure you need to verify that you installed and configured your data service correctly.
# cluster status
Enable any WebSphere Message Broker resources that are not online.
# clresource enable websphere-message-broker-resource
# clresourcegroup switch -n node[:zone] websphere-mq-resource-group