This task adds a service integration bus link to
a selected messaging engine. By adding a link between service integration bus link messaging
engines, you can link messaging engines in different service integration buses,
and thereby extend the network of buses.
You must create a foreign bus for the service integration bus to be
linked to, and a routing definition for that bus.
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:
- 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
- Description
- Foreign bus name
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
- Target inbound transport chain
- 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
- 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.
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
Note: 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 must be the same
in the user registry on the messaging engines at each side of the link. For
example, user ID 1 (and its password) must be the same in the user registry
on messaging engine 1, and in the authentication alias on the other side of
the link on messaging engine 2. User ID 2 (and its password) must exist in
the user registry on messaging engine 2, and in the authentication alias on
the other side of the link on messaging engine 1.
- Initial state
- 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.