WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Adding a service integration bus link

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

  1. Display the list of messaging engines.
  2. In the content pane, select the messaging engine to which you want to add the service integration bus links.
  3. In the content pane, under Additional properties, click Service integration bus links. A list of service integration bus links is displayed.
  4. Click New.
  5. 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.
  6. Click OK.
  7. 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.
Related concepts
Foreign buses
Multiple bus topology
Administering foreign bus roles
Configuring a WebSphere MQ link
Related tasks
Managing J2EE Connector Architecture authentication data entries
Related information
JMS connection factory settings

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjj0082_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)