Reply-to queue alias example
This example illustrates the use of a reply-to alias to select a different route (transmission queue) for returned messages. The use of this facility requires the reply-to queue name to be changed in cooperation with the applications.
As shown in Figure 1, the return route must be available for the reply messages, including the transmission queue, channel, and queue manager alias.
Figure 1. Reply-to queue alias example
This example is for requester applications at ‘QM1’ that send messages to server applications at ‘QM2’. The servers’ messages are to be returned through an alternative channel using transmission queue ‘QM1_relief’ (the default return channel would be served with a transmission queue ‘QM1’).
The reply-to queue alias is a particular use of the remote queue definition named ‘Answer_alias’. Applications at QM1 include this name, ‘Answer_alias’, in the reply-to field of all messages that they put on queue ‘Inquiry’.
Reply-to queue definition ‘Answer_alias’ is defined as ‘Answer at QM1_relief’. Applications at QM1 expect their replies to appear in the local queue named ‘Answer’.
Server applications at QM2 use the reply-to field of received messages to obtain the queue and queue manager names for the reply messages to the requester at QM1.
- Definitions used in this example at QM1
- Definitions used in this example at QM2
- Put definition at QM1
- Put definition at QM2
Parent topic:
Reply-to queue
ic10960_
Home
