WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Defining permission for a publish/subscribe broker profile to work with a broker

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 begin
Before you start this task, you must have created a broker profile, part of a publish/subscribe bridge on a WebSphere MQ link.
About this task
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:

To ensure authority, do one of the following steps:

Procedure

  1. 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.
  2. 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 user ID set in them.
What to do next
Now, you can define topic mappings for the broker, by following the steps in Defining topic mappings.

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjc0101_.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)