Configuring a destination reverse routing path

Use this task to configure a reverse routing path between two bus destinations. The reverse routing path identifies the list of destinations to which a reply message should be sent when the consumer of a request message sends a reply message back to the producer of the reply message.

About this task

The following figure shows a producing application that sends messages to a bus destination. Unknown to the application, the messages are then passed along a forward routing path of other bus destinations to a target destination from which a consuming application retrieves the messages.


This figure is described in the surrounding text.

For each destination that is to be part of a reverse routing path back to the producer application, you can specify the name of a reply destination, which is the next destination in the reverse routing path. For example in the above diagram, if reply messages are to retrace the forward routing path back to the producing application, you would set reverse routing path as follows:
Destination Reply destination bus
D4 D3
D3 D2
D2 D1
D1 Destination

You can specify a different reverse routing path to the forward routing path, to enable more mediations to be applied to reply messages, or to apply mediations in a different destination sequence.

If the same destinations are used for both the forward and reverse routing paths, you can configure the reverse routing path when you configure the forward routing path, as described in Configuring a destination forward routing path. Otherwise, you can configure (or change) the reverse routing path as described in this topic.

To configure a reverse routing path, you only need to change the properties of the destinations you want to use. This topic contains optional steps to create destinations, in case you have not already done so.

To configure a reverse routing path for a destination, use the administrative console to complete the following steps:

Procedure

  1. Optional: If you have not yet done so, create the destination to which the producer applications attaches. For this destination, you can create a queue or create a topic space.
  2. Optional: If you have not already done so, create each destination in the path.
  3. Optional: If you have not already done so, assign mediations to the destinations in the path. You can include a destination without mediations in a routing path, to provide a future option to apply a mediation assigned to that destination.
  4. On each destination in the reverse routing path, specify the name of the next destination in the path:
    1. In the navigation pane, click Service integration > Buses.
    2. In the content pane, click the name of the bus on which the destination exists.
    3. In the content pane, under Destination resources, click Destinations
    4. Click the destination name.
    5. In the Reply destination field, type the name of the next destination in the reverse routing path.
    6. In the Reply destination bus field, type the name of the next destination in the reverse routing path.
    7. Save your changes to the master configuration.



In this information ...


Related concepts

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: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tjo0025_
File name: tjo0025_.html