WebSphere Message Brokers
File: ae28550_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:28:56

WebSphere Message Broker and WebSphere MQ setup verification

Whenever a component (that is a broker, User Name Server, or Configuration Manager) starts, a basic component verification runs automatically. This verification checks:
  • Basic WebSphere MQ information
  • DB2 information
  • Registry information
  • Setup verification
If an error is found the component does not start. All output from the verification step is written to the component's JOBLOG.

You also need to validate that the entire WebSphere Message Broker system you installed is running correctly; that is, there are no errors in the system and that the system is performing as expected. This is especially important where you are installing WebSphere Message Broker for the first time.

You should download and review WebSphere Message Broker SupportPac IP13.

This SupportPac provides:
  • Tools to help test WebSphere Message Broker flows running on z/OS. These tools provide:
    • Put and get user messages
    • Measurement of the elapsed time
    • CPU time used to process the messages
    • Recommendations on the environment configuration.
  • Recommendations on designing flows for evaluation, to reduce the need for applications outside of the WebSphere Message Broker environment.
  • WebSphere Message Broker flows, which allow you to compare the throughput you achieve in your environment with that achieved at IBM. Using the tools supplied in WebSphere Message Broker SupportPac IP13 can give suggestions as to why the results might be different.
Select the following link to access WebSphere Message Broker SupportPac IP13 - IP13.
Related concepts
Brokers
Configuration Manager
User Name Server
Related tasks
Customizing the z/OS environment
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:28:56

ae28550_ This topic's URL is: