Broker profile on an IBM MQ link

A broker profile on a WebSphere® MQ link defines a connection through a IBM MQ link to an IBM MQ queue manager, for the purpose of publish/subscribe messaging with an IBM MQ network.

A broker profile applies to the connection between WebSphere Application Server and a single IBM MQ queue manager or separate publish/subscribe broker. It contains the following information:
  • The name of the IBM 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 IBM MQ. This queue manager does not have to be the same as the IBM MQ gateway queue manager, provided that it can be reached from the IBM MQ gateway queue manager. If you are using a separate publish/subscribe broker, this queue manager is the IBM 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 IBM MQ link, to connect to multiple queue managers in the IBM 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 IBM MQ network. For more information about topic mappings, see Topic mapping on an IBM MQ link.

The broker profiles, along with their topic mappings, form a publish/subscribe bridge with the IBM MQ network. The publish/subscribe bridge connects as a subscriber to receive messages from the IBM MQ network and pass them to applications in WebSphere Application Server, and it connects as a publisher to publish messages on topics in the IBM MQ network. For a description of how the publish/subscribe bridge operates, see Publish/subscribe bridge on an IBM MQ link.