WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer service integration buses > Configure buses > Connect buses

Modify a routing definition

We can view or change the routing definition of an existing foreign bus connection between a local bus and a foreign bus. The routing definition defines the virtual link between two buses that enables them to exchange messages. The routing definition can define properties for a virtual service integration bus link, a virtual WebSphere MQ link, or an indirect foreign bus connection. We create a routing definition when we create a foreign bus connection. For a direct foreign bus connection, the routing definition, or virtual link, has a corresponding physical link on a messaging engine.

To change the properties of the routing definition, use the dmgr console to complete the following steps:

1. In the navigation pane, click Service integration -> Buses. A list of service integration buses is displayed.
2. In the Buses pane, click the service integration bus that is connected to another bus, that is, the local bus you require.
3. In the content pane, under Topology, click Foreign bus connections. A list of buses that have a foreign bus connection from the local bus is displayed.

4. Select the required foreign bus.
5. In the content pane, under Additional properties, click the routing properties option. The routing properties option depends on the type of routing definition and is one of the following:
   • Service integration bus link routing properties
   • WebSphere MQ link routing properties
   • Indirect routing properties

6. Optional: Specify the new routing properties:

   • For a virtual service integration bus link or a virtual WebSphere MQ link, specify properties as follows:

     Inbound user ID

     The user name used to authenticate inbound message flows from the foreign bus.

     When the local bus is secure, the inbound user ID replaces the user ID in messages from the foreign bus that arrive at the local bus and is used to authorize whether those messages can access their destinations. Specify an inbound user ID for the local service integration bus under the following circumstances:

     • The foreign bus is in a different security domain, so user IDs in the foreign bus are not recognized in the local bus.
     • You want local control of access to inbound messages to the local bus.

     If the local bus is not secure, the inbound user ID has no effect on messages. If the local bus is secure, the foreign bus is not secure, and an inbound user ID is not 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 foreign bus connection, select the name of the next foreign bus you require in the chain of intermediate buses. For a bus to be available for selection, it must already have a direct foreign bus connection from the local bus.

7. Click OK.

8. Save your changes to the master configuration.
   

Related concepts:

Direct and indirect routing between service integration buses

+

Search Tips   |   Advanced Search