You can add a service integration bus link to
messaging engines in different service integration buses, thereby extending
the network of buses.
Before you begin
You must create a foreign bus for the service integration bus to be
linked to, and a routing definition for that bus.
Why and when to perform this task
By
adding a
service integration bus link to a
messaging engine, you establish a link on a messaging engine in a different
service integration bus. The messaging engine is associated with the virtual
link. You need to add a link on both messaging engines that are being linked,
and you must use the same name for both links.
To add a service integration bus link to
a messaging engine, use the administrative console to complete the following steps:
Steps for this task
- Display the list of messaging engines. by following Listing the messaging engines in a bus
- In the content pane, select
the messaging engine to which you want to add the service integration bus links.
- In the content pane, under Additional properties, click Service
integration bus links. A list of service integration bus links is
displayed.
- Click New.
- Specify properties as follows:
- Name
- The name of the service integration bus link. In order to work, the name must be the same as the name of the corresponding service integration bus link configured on the target foreign bus.
- Description
- An optional description for the service integration bus link, for administrative purposes.
- Foreign bus name
- The foreign bus to which this link connects.
Note: The foreign
bus name must not be altered once it has been configured. If you alter it,
any messaging engines that already hold state information about the link will
not be able to use the link unless the foreign bus name is reset to its original
value.
- Foreign messaging engine
- The messaging engine on the foreign bus to which this link connects.
- Target inbound transport chain
- The type of transport chain used for communication with the foreign bus. The
transport chain name must be the name of the transport chain as defined on
the server on which the remote messaging engine is hosted.
- Bootstrap endpoints
- The comma-separated list of endpoints used to connect to a bootstrap server.
Note: If you want to connect your local bus to a foreign bus, and the
remote messaging engine is in a cluster, you must change the default values
to the correct Bootstrap server values.
This property is set in the same way as the Provider endpoint property in the JMS connection factory settings. For more information, see steps 1 and 2 of Configuring a connection to a non-default bootstrap server. Although this task primarily describes how to configure a JMS connection factory, it is also applicable to setting several bootstrap endpoint values if the remote messaging engine is in a cluster.
- Authentication alias
- The name of the authentication alias, used to autnenticate access to the foreign bus.
Authentication tip: To create a
service integration bus link between two secure
buses, you must add an authentication alias to both ends of the link. The
user ID you specify in the authentication alias on each side of the link must
be the same, and the user ID must exist in the user registries accessed by
the servers hosting each side of the link. This is because the user ID is
used for two purposes. Consider two messaging engines, A and B, connected
by a foreign bus link:
- The user ID is presented by Messaging Engine A (together with the password)
to Messaging Engine B, so that Messaging Engine B can authenticate Messaging
Engine A.
- The user ID is used by Messaging Engine A to authorize Messaging Engine
B.
Only the user ID needs to be the same. The passwords supplied in the
authentication aliases can be different, as long as the password sent matches
the information specified in the user registry at the receiving end of the
link. For example: An authentication alias is passed from Messaging Engine
A to Messaging Engine B. This user ID and password is then authenticated
by Messaging Engine B against its user registry. The user ID is authorized
for inter-bus connection if the following two conditions are met:
- The user ID exists in the user registries for both messaging engines.
- The password matches the password defined for that user ID on Messaging
Engine B.
- Initial state
- Whether the link is started automatically when the messaging engine is started. Until
started, the gateway link is unavailable. If this property is set to Started,
the service integration bus link is started
when the messaging engine is started.
- Click OK.
- Save your changes to the master configuration.
You must create another
service integration bus link on
a messaging engine in the foreign bus. Note that both links must have the
same name. When both
service integration bus links have
been created and started, the connection between the buses becomes active.