Configure a destination reverse routing path
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.
In the following figure, a producing application 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 where a consuming application retrieves the messages.
Figure 1. Example of a routing path
For each destination that is to be part of a reverse routing path back to the producer application, we can specify the name of a reply destination, which is the next destination in the reverse routing path. For example in the diagram, if reply messages are to retrace the forward routing path back to the producing application, we would set reverse routing path as follows:
| Destination | Reply destination bus |
|---|---|
| D4 | D3 |
| D3 | D2 |
| D2 | D1 |
| D1 | Destination |
We 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, we can configure the reverse routing path when we configure the forward routing path, as described in Configure a destination forward routing path. Otherwise, we can configure (or change) the reverse routing path as described in this topic.
To configure a reverse routing path, we only have to change the properties of the destinations we want to use. This topic contains optional steps to create destinations, in case we have not already done so.
To configure a reverse routing path for a destination, use the administrative console to complete the following steps:
Tasks
- Optional: If we have not yet done so, create the destination to which the producer applications attaches. For this destination, we can create a queue or create a topic space.
- Optional: If we have not already done so, create each destination in the path.
- Optional: If we have not already done so, assign mediations to the destinations in the path. We can include a destination without mediations in a routing path, to provide a future option to apply a mediation assigned to that destination.
- On each destination in the reverse routing path, specify
the name of the next destination in the path:
- Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations -> destination_name.
- In the Reply destination field, type the name of the next destination in the reverse routing path.
- In the Reply destination bus field, type the name of the next destination in the reverse routing path.
- Save changes to the master configuration.
Related: