Adding a foreign bus

You can add a foreign bus to 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.

About this task

You can configure a bus to connect to, and exchange messages with, other messaging networks. To do this, you must configure a foreign bus definition. A foreign bus definition encapsulates information related to the remote messaging network, such as the type of the foreign bus and whether messaging applications are allowed to send messages to the foreign bus. 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.
Note: The name of the foreign bus must match exactly the name of the existing bus that is defined as the foreign bus.

To add a foreign bus for the local bus, use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Service integration > Buses. A list of buses is displayed in the content pane.
  2. In the content pane, select the bus for which you want to add the foreign bus.
  3. In the content pane, under Topology, click Foreign buses. A list of foreign buses is displayed.
  4. Click New.
  5. Specify the following properties for the new foreign bus:
    Name
    The name of the bus with which this bus will exchange messages. This name must match exactly the name of the existing service integration bus that is defined as the foreign bus. This name must match exactly the name of the existing bus that is defined as the foreign bus.
    Description
    An optional description for the foreign bus, for administrative purposes.
    Send allowed
    Clear this option (setting it to false) to stop producers from being able to send messages to this foreign bus.
  6. Click Next.
  7. 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.
  8. Click Next.
  9. Specify the routing definition properties for the foreign bus:
    • For a direct link, specify properties as follows:
      Inbound user ID
      The user name used to authenticate inbound message flows from the foreign bus.
      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 user name used to authenticate outbound message flows to the foreign bus.

      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.
  10. Review the summary and click Finish to create the foreign bus.
  11. Save your changes to the master configuration.

Results

You have added a foreign bus for an existing local bus, and you have created a routing definition.

What to do next

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.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=tjj0072_
File name: tjj0072_.html