Use this task to add a foreign bus, and create a routing definition.
Before you begin
Why and when to perform this task
A
foreign bus is a bus with which the local bus can exchange messages. The foreign
bus must be an existing service integration bus, or a WebSphere MQ gateway
queue manager.
To add a foreign bus for the local bus, use the administrative console to complete the following steps:
Steps for this task
- In the navigation pane, click . A list of buses is displayed in the content pane.
- In the content pane, select
the bus for which you want to add the foreign bus.
- In the content pane, under Additional properties, click Foreign
buses. A list of foreign buses is displayed.
- Click New.
- Specify the properties for the new foreign bus:
- Name
- The name of the bus with which this bus will exchange messages. This
name must match exactly the name of the existing service integration bus that
is defined as the foreign bus.
- Description
- An optional description for the foreign bus, for administrative purposes.
- Send allowed
- Clear this option (setting it to false) to stop producers from being able to send messages to this foreign bus.
- Click Next.
- Select the routing definition type (the virtual link) for the foreign
bus. The options available are:
- Direct, service integration bus link
- Use this routing definition type when the foreign bus represents another
service integration bus.
- Direct, WebSphere MQ Link
- Use this routing definition type when the foreign bus represents a WebSphere
MQ gateway queue manager.
- Indirect
- Use this routing definition type when the foreign bus represents an intermediate
service integration bus which is used as a bridge to a third service integration
bus.
- Click Next.
- Specify the routing definition properties for the foreign bus:
- For a direct link, specify properties as follows:
- Inbound user ID
- The user name used to authenticate inbound message flows from the foreign bus.
The
inbound user ID is used to authorize individual messages arriving from the
foreign bus to destinations in this bus. When set, this property replaces
the user Id in messages entering this bus from the foreign bus. If this is
not a secure bus, this property has no affect on messages. You may wish to
specify an inbound user ID:
- if the foreign bus is in a different security domain from this bus and
user IDs from the foreign bus are not recognized in this bus
- to locally-control access of inbound messages to this bus.
If this is a secure bus and the foreign bus is not secure, and no inbound
user ID is set, any inbound messages from the foreign bus will only be authorized
to destinations that allow unauthenticated users access.
- Outbound user ID
- The user name used to authenticate outbound message flows to the foreign bus.
The
outbound user ID replaces the user ID that identifies the source of a message
in all messages being sent to the foreign bus. When set, this property replaces
the user Id in messages leaving this bus for the foreign bus. This user ID
is also be used by the foreign bus to authorize the message to its destination
if both buses are secure buses and the foreign bus has not overridden the
user ID with its own inbound user ID.
- For an indirect link, select the name of the intermediate foreign bus.
- Review the summary and click Finish to create
the foreign bus.
- Save your changes to the master configuration.
After you have created a foreign bus and its routing definition,
you must create a foreign bus definition. You must also create service integration bus links between
messaging engines in the local bus and foreign bus. If the foreign bus is
a WebSphere MQ gateway queue manager, create a WebSphere MQ link.