Use this task to configure a reverse routing path between two bus destinations. The reverse routing path identifies the list of destinations that any reply message should sent to from the consumer back to the producer.
If producing and consuming applications both attach directly to the destination that is to host and process their messages, you do not need to use routing paths. You can still use mediations assigned to the destination to manipulate messages. However, if you want a more flexible architecture, you can assign mediations to several destinations then specify those destinations as the forward routing path for another destination.
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: