WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when using the WebSphere Message Broker Explorer
Work through the advice provided to help you to deal with problems that can arise when you are using the WebSphere® Message Broker Explorer.
Tracing problems with accounting and statistics
- Scenario: When you view accounting and statistics data using the WebSphere Message Broker Explorer you encounter a problem, and you want to collect trace.
- Explanation: The WebSphere Message Broker Explorer uses the Java™ Message Service (JMS) to retrieve the accounting and statistics data from the broker. To trace problems with this connection, you must turn on JMS tracing in WebSphere MQ.
- Solution: See the WebSphere MQ documentation for information about how to turn on JMS tracing. You can find this information in the following part of the information center: .
The Brokers folder is missing
- Scenario: You have opened the WebSphere MQ Explorer to work with brokers and associated resources, but you cannot see the Brokers folder.
- Explanation: The WebSphere Message Broker Explorer is an extension to the WebSphere MQ Explorer, and provides the Brokers folder and Broker Archive Files folder, and related actions. You must install the WebSphere Message Broker Explorer component on all computers on which you want to use the WebSphere MQ Explorer to manage WebSphere Message Broker resources, including brokers, execution groups and BAR files.
- Solution: Close your MQ Explorer session, follow the instructions to install the WebSphere Message Broker Explorer, then start the MQ Explorer again.
You cannot open the information center on Red Hat Enterprise Linux
- Scenario: You are using the WebSphere Message Broker Explorer on Red Hat Enterprise Linux Server 5.2 or Red Hat Enterprise Linux Server 5.3 but you cannot open the information center from inside WebSphere Message Broker Explorer.
- Solution: Set the environment variable MOZILLA_FIVE_PATH then run the strmqcfg command. For more information, see the question about running the SWT browser inside Eclipse at: Eclipse SWT FAQ