Each broker depends on a number of WebSphere MQ resources:
some must be available, others depend on the broker domain setup. Some of
these resources are created for you: you must define others yourself.
WebSphere MQ resources that you
must create yourself
Depending on the setup of your broker, you
might need to create some
WebSphere MQ resources
yourself. You can create
WebSphere MQ resources
using commands and utilities such as runmqsc and the PCF interface, or you
can use
WebSphere MQ Services (with
WebSphere MQ Version
5) or
WebSphere MQ Explorer (with
WebSphere MQ Version
6).
- For WebSphere Message Broker on z/OS, you must create
a queue manager in WebSphere MQ for your broker.
See Creating a broker on z/OS for more details.
- If the broker and Configuration
Manager do
not share a queue manager, you must define the channels and transmission queues
to support communication between the broker's queue manager and the Configuration
Manager's queue manager.
- If the broker and User
Name Server do
not share a queue manager, you must define the channels and transmission queues
to support communication between the broker's queue manager and the Configuration
Manager's queue manager.
- You must define listener connections on the broker's queue manager. You
must define one listener connection for every protocol used.
- For connection between brokers, you must define the channels and transmission
queues to permit two-way communication between them.
For more information about creating WebSphere MQ resources,
see WebSphere MQ Intercommunication,
available on the WebSphere MQ library Web page.