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

Creating a routing definition

You can create a routing definition between a local bus and a foreign bus. This defines the virtual link between the two buses, enabling them to exchange buses.

Before you begin

Before you create a routing definition, you must create and save a foreign bus definition.

Why and when to perform this task

You would normally create a routing definition as part of the creation of the foreign bus. However if you have deleted the routing definition from the foreign bus, use this task to create a new routing definition.

To create a routing definition: use the administrative console to complete the following steps:

Steps for this task

  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 local bus associated with the foreign bus.
  3. In the content pane, under Topology, click Foreign buses. A list of foreign buses is displayed.
  4. Click the foreign bus for which you want to create a new routing definition.
  5. Under Additional Properties, click Create a routing definition.
  6. In the Create foreign bus routing definition wizard, select a routing type. You can select one of:
    Direct, service integration bus link
    Use this routing definition type when the foreign bus represents another 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.
  7. Click Next.
  8. Specify the routing definition properties:
    • 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 this bus. When set, this property replaces the user Id in messages entering this bus from the foreign bus. If this is not a secure bus, this property has no affect on messages. You may wish to specify an inbound user ID:
      • if the foreign bus is in a different security domain from this bus and user IDs from the foreign bus are not recognized in this bus
      • to locally-control access of inbound messages to this bus.
      If this is a secure bus and the foreign bus is not secure, and no inbound user ID is set, any inbound messages from the foreign bus will only be 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 source of a message in all messages being sent to the foreign bus. When set, this property replaces the user Id in messages leaving this bus for the foreign bus. This user ID is also be used by the foreign bus to authorize the message to its destination if both buses are secure buses and the foreign bus has not overridden the user ID with its own inbound user ID.

    • For an indirect link, select the name of the intermediate foreign bus.
  9. Click Next.
  10. Click Finish.
  11. Save your changes to the master configuration

A virtual link is created for the foreign bus.
Related concepts
Foreign buses
Direct and indirect routing between service integration buses

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjj0703_.html

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