Use this task to add a service integration bus link to
a messaging engine.
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. Adding a
service integration bus link does
not disrupt current message processing. 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.
- 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 by which the service integration bus link is known for administrative purposes.
- 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.
- Remote messaging engine name
- 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. 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 connection to a non-default bootstrap server.
- Authentication alias
- The name of the authentication alias, used to authenticate access to the foreign bus.
Note: In order to establish the SIB Link between two secure buses,
you must add an authentication alias to both ends of the link. The user ID
in the alias must exist on both hosts. User name and password 1 must exist
in the user registry on host 1, and also in the authentication alias at the
end of the link on host 2. User name and password 2 must exist in the user
registry on host 2, and in the alias at the end of the link on host 1.
- Initial state
- Whether the link is started automatically when the messaging engine is started. 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.
If you have not already done so, you must create a 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.