Use this task to add a foreign bus for an existing bus in a network
of buses. The existing bus can be either a service integration bus, or a WebSphere
MQ queue manager. Extending a bus network in this way enables all the buses
in the network to exchange messages. When a bus is added, a routing definition,
or virtual link, between the buses, is also created.
A
foreign bus is a bus with which an existing bus can exchange messages. In
this context, the existing bus is referred to as the local bus. By adding
a foreign bus for a local bus, the local bus can exchange messages with the
foreign bus. In this way, a network of buses can be extended. When you add
a foreign bus, you define a routing definition type. This determines whether
the foreign bus represents a 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:
- 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 Topology, click Foreign
buses. A list of foreign buses is displayed.
- Click New.
- Specify the following properties for the new foreign bus:
- Name
- This
name must match exactly the name of the existing local bus that is defined
as the foreign bus.
- Description
- Send allowed
- Click Next.
- Select the routing definition type (the virtual link) for the foreign
bus:
- Direct, service integration bus link
- Use this routing definition type when the foreign bus represents a 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
inbound user ID is used to authorize individual messages arriving from the
foreign bus to destinations in the local bus. Where it is defined, the inbound
user ID supersedes the user ID in messages arriving at the local bus from
the foreign bus. If the local bus is not secure, the inbound user ID has no
affect on messages. You may want to specify an inbound user ID for the local
bus when:
- The foreign bus is in a different security domain, user IDs in the foreign
bus are not recognized in the local bus
- You want to control locally access to inbound messages to the local bus.
In the case where the local bus is secure, the foreign bus is not secure,
and an inbound user ID has not been set, an inbound message from the foreign
bus is only authorized to destinations that allow unauthenticated users access.
- Outbound user ID
The
outbound user ID replaces the user ID that identifies the message source in
every message sent to the foreign bus. Where it is defined, the outbound user
ID replaces the user ID in messages sent by the local bus to the foreign bus.
If the local bus and the foreign bus are both secure, and the foreign bus
has not overridden the user ID with its own inbound user ID, the foreign bus
also uses the outbound user ID to authorize the message to its destination.
- 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.
You have added a foreign bus for an existing local bus, and you have
created a routing definition.
Next, you must create links, in both directions, between
the messaging engine in the local bus and the messaging engine in the foreign
bus. If the foreign bus is a WebSphere MQ gateway queue manager, you must
create a WebSphere MQ link. If the foreign bus is a service integration bus,
you must create a service integration link.