WebSphere MQ resources for the Configuration Manager
The Configuration Manager depends
on a number of WebSphere MQ resources: some must
be available, others depend on the broker domain setup: - The Configuration Manager must
be associated with a queue manager to host its services. Specify a queue manager name
when you create the Configuration Manager. If this queue manager does not exist,
it is created for you.
The Configuration Manager can share a queue manager with
a component (broker, or the User Name Server, or both) if they are on Windows platforms.
- The Configuration Manager 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 Configuration Manager is created.
- The Configuration Manager must communicate with every
broker in the broker domain. Define transmission queues and channels to support
two-way communications between the Configuration Manager and
every broker, except the one (if defined) that shares its queue manager.
- If you have included a User Name Server in your
broker domain, the Configuration Manager must communicate
with it. If the Configuration Manager and the User Name Server do
not share a queue manager, you must define transmission queues and channels
to support two-way communications between the two queue managers.
- The Configuration Manager's queue manager must have
a listener to receive messages from the workbench,
and from other components and clients that do not share its queue manager.
You must create a listener for every protocol used for the intercomponent
connections. If the connection is TCP/IP, you must also decide which port
the listener must listen on; no other listener must be active on this port.
- The Configuration Manager's queue manager must have
a server connection. This is defined for you when the Configuration Manager is
created. Every workbench client can use this
single definition.