This topic gives a choice of ways to ensure that a service integration bus has
authority with a message broker (in a WebSphere MQ network) to send subscription
requests.
Before you start this task, you must have created a broker profile,
part of a publish/subscribe bridge on a WebSphere MQ link.
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. You can do this
either by:
- Modifying the message broker configuration in the WebSphere MQ network
if you are a WebSphere MQ administrator. Or
- Modifying the service integration bus configuration
if you are a WebSphere Application Server administrator.
To ensure authority, do one of the following steps:
- Modify the message broker configuration by
granting WebSphere MQ permissions for the user "SIBServer", which is the user
name under which the publish/subscribe bridge control messages will be published.
- Modify the service integration bus by
setting the OutboundUserID of the foreign bus that represents the WebSphere
MQ network (which you defined as part of the WebSphere MQ link configuration).
The OutboundUserID should be set to a user ID that already has the relevant
WebSphere MQ permissions on the message broker install image. By doing this
you can be sure the publish/subscribe bridge control messages will arrive
at the message broker in the WebSphere MQ network with the appropriate userID
set in them.