WebSphere MQ resources for brokers

Each broker depends on a number of WebSphere MQ resources; some are always required; others depend on the broker domain setup:
  1. Each broker must be associated with a queue manager to host its services. Specify a queue manager name when you create the broker. If this queue manager does not exist, it is created for you. (For WebSphere Business Integration Event 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.)

    The broker cannot share a queue manager with any other broker. It can share a queue manager with the Configuration Manager, or the User Name Server, or both if the broker is on a Windows platform.

    The broker and its queue manager can share the same name, subject to naming restrictions for both products.

  2. Each broker must have a number of fixed-name queues on its queue manager. These allow it to exchange information with other components in the broker domain. These queues are defined for you when the broker is created. The use of these fixed-name queues dictates that each broker must be hosted by a unique queue manager.
  3. Each broker must communicate with the Configuration Manager. If the broker and the Configuration Manager do not share a queue manager, you must define the channels and transmission queues that support communications between the two queue managers.
  4. If you have included a User Name Server in your broker domain, each broker must communicate with it. If the broker and the User Name Server do not share a queue manager, you must define transmission queues and channels that support two-way communications between the two queue managers.
  5. The broker's queue manager must have a listener to receive messages from other components that do not share its queue manager, and from clients on other physical systems. Create a listener for every protocol used for connections to the broker. If any connection uses the TCP/IP protocol, you must decide which port the listener must listen on.
  6. If the broker is connected to other brokers, either in a collective or to communicate with another collective, the queue manager needs transmission queues and channel definitions to support two-way communications with each of the other brokers' queue managers.

Related concepts
Broker domain

Related tasks
Creating a broker on z/OS

Related reference
Designing the WebSphere MQ infrastructure
WebSphere MQ resources for the Configuration Manager
WebSphere MQ resources for the User Name Server