This topic describes the broker profile, on the WebSphere
MQ link, that enables a connection for publishing and subscribing with a message
broker in a WebSphere MQ network.
You can define a broker profile to enable you to:
- Publish messages to a message broker in a WebSphere MQ network which will,
in turn, publish the messages to subscribers in the WebSphere MQ network.
- Subscribe to a message broker in a WebSphere MQ network, enabling messages
published to the message broker to be received by subscribers in a WebSphere
Application Server.
The broker profile, along with its topic mappings, forms what is known
as a publish/subscribe bridge with a WebSphere MQ network.
- A broker profile contains information that is particular to a single broker.
On a single WebSphere MQ link messaging engine you can have multiple broker
profiles to connect to multiple brokers in the WebSphere MQ network.
- If you have more than one broker profile you must set the broker queue
manager to the one where the input queues for the required publication message
flows are located. This does not need to be the same as the WebSphere MQ gateway
queue manager if your broker is connected to another queue manager that can
be reached from the WebSphere MQ gateway queue manager.
- When defining topic mapping for the broker profile you can chose if messages
are to flow from WebSphere MQ to WebSphere Application Server,
or from WebSphere Application Server to WebSphere
MQ, or if the flow is two-way.
- When you have created a broker profile you must ensure that the service
integration bus has sufficient authority on the message broker instance to
send subscription requests. See Defining permission for a publish/subscribe broker profile to work with a broker.
Once you have created a broker profile, follow the steps to create topic
mappings in Defining topic mappings.