A broker profile on a WebSphere® MQ
link defines a connection through a WebSphere MQ link to a WebSphere MQ queue manager, for the purpose
of publish/subscribe messaging with a WebSphere MQ network.
A broker profile applies to the connection between
WebSphere Application Server and a single
WebSphere MQ queue manager or separate
publish/subscribe broker. It contains the following information:
- The name of the WebSphere MQ link.
- The name of the service integration bus in WebSphere Application Server.
- The name of the messaging engine in WebSphere Application Server.
- The name of the queue manager in WebSphere MQ. This queue manager does
not have to be the same as the WebSphere MQ gateway
queue manager, provided that it can be reached from the WebSphere MQ gateway queue manager. If
you are using a separate publish/subscribe broker, this queue manager
is the WebSphere MQ queue manager
to which the message broker is connected. You must ensure that the
service integration bus has sufficient authority to send subscription
requests to the queue manager or separate publish/subscribe broker.
You can define multiple broker profiles on a single
WebSphere MQ link, to connect to multiple
queue managers in the
WebSphere MQ network.
You define one or more topic mappings for a broker profile. A topic
mapping links a specific topic in the WebSphere Application Server service integration bus
with its equivalent in the WebSphere MQ network.
For more information about topic mappings, see Topic mapping on a WebSphere MQ link.
The broker profiles, along with their topic mappings, form a publish/subscribe
bridge with the WebSphere MQ network.
The publish/subscribe bridge connects as a subscriber to receive messages
from the WebSphere MQ network and
pass them to applications in WebSphere Application Server,
and it connects as a publisher to publish messages on topics in the WebSphere MQ network. For a description
of how the publish/subscribe bridge operates, see Publish/subscribe bridge on a WebSphere MQ link.