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
A. Deployment Example: Installing WebSphere Message Broker in Zones
HA for WebSphere Message Broker can be used by multiple WebSphere Message Broker instances. It is possible to turn debug on for all WebSphere Message Broker instances or a particular WebSphere Message Broker instance.
A config file exists under /opt/SUNWscmqi/xxx/etc, where xxx can be sib (Broker or Configuration Manager) or siu (UserNameServer).
These files allow you to turn on debug for all WebSphere Message Broker instances or for a specific WebSphere Message Broker instance on a particular node or zone within the cluster. If you require debug to be turned on for HA for WebSphere Message Broker across the whole cluster, repeat this step on all nodes within the cluster.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator #
Change the daemon.notice to daemon.debug and restart syslogd. Note that the output below, from grep daemon /etc/syslog.conf, shows that daemon.debug has been set.
# grep daemon /etc/syslog.conf *.err;kern.debug;daemon.debug;mail.crit /var/adm/messages *.alert;kern.err;daemon.err operator
Restart the syslog daemon.
# svcadm disable system-log # svcadm enable system-log
Perform this step for each component that requires debug output, on each node of Oracle Solaris Cluster as required.
Edit /opt/SUNWscmqi/xxx/etc/config and change DEBUG= to DEBUG=ALL or DEBUG=resource.
# cat /opt/SUNWscmqi/sib/etc/config # # Copyright 2006 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # ##ident "@(#)config 1.2 06/03/21 SMI" # # Usage: # DEBUG=<RESOURCE_NAME> or ALL # DEBUG=ALL
Note - To turn off debug, reverse the steps above.