WebSphere MQ resources for the Configuration Manager

Each Configuration Manager 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 created for you

When you create a Configuration Manager, the following WebSphere MQ resources are created for you:
  • The Configuration Manager's queue manager. Each Configuration Manager must be associated with a queue manager. Specify a queue manager name when you create the Configuration Manager. If this queue manager does not exist, it is created for you. (For WebSphere Message Broker on z/OS, you must create a queue manager in WebSphere MQ for your Configuration Manager. See Creating a Configuration Manager on z/OS for more details.)
  • Fixed-name queues on the Configuration Manager's queue manager. These allow information to be exchanged with other components in the broker domain.
  • A server connection for use by the Workbench.

WebSphere MQ resources that you must create yourself

Depending on the setup of your Configuration Manager, 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 Configuration Manager. See Creating a Configuration Manager on z/OS for more details.
  • You must define the transmission queues and channels between the Configuration Manager and every broker in the domain (apart from the broker that shares a queue manager with the Configuration Manager).
  • If the Configuration Manager 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 Configuration Manager's queue manager for the Workbench and other components and clients that do not share the Configuration Manager's queue manager. You must define one listener connection for every protocol used.

For more information about creating WebSphere MQ resources, see WebSphere MQ Intercommunication, available on the WebSphere MQ library Web page.

Related concepts
Broker domains
Related tasks
Creating a broker
Related reference
Designing the WebSphere MQ infrastructure
WebSphere MQ resources for the broker
WebSphere MQ resources for the User Name Server