This text describes how reply-to topics, a feature of WebSphere® MQ, are handled by WebSphere MQ link.
A WebSphere Application Server JMS application can publish a message to a topic space with a reply-to topic which is received by the publish/subscribe bridge on the WebSphere MQ link and passed to a message broker in a WebSphere MQ network. The WebSphere MQ JMS application receives the message from the message broker, obtains the reply destination and publishes a message to the message broker on the reply topic. In order for the reply message to be routed back to WebSphere Application Server subscribers, the administrator must have configured a topic mapping from WebSphere MQ to WebSphere Application Server on the reply topic (unless it is a temporary reply topic, as described below.)
A WebSphere MQ JMS application can publish a message to a broker with a reply-to topic which is received by the WebSphere Application Server application. An example is a WebSphere MQ JMS application publishing to a message broker in the WebSphere MQ network, on "myTopic" with a reply topic of "myReplyTopic". A mapping must have already been specified on the publish/subscribe bridge so that the publish/subscribe bridge is subscribing to "myTopic" on the message broker. When the message is sent over the WebSphere MQ link it is translated into the correct format, and delivered to the publish/subscribe bridge subscriber queue where it is processed and then sent on to the topic space as specified in the publish/subscribe topic mapping. It is then received by the WebSphere Application Server JMS application, which sends a reply message back to the message broker on the WebSphere MQ network by way of the publish/subscribe bridge. You must already have created a mapping to forward messages published on "myReplyTopic" from WebSphere Application Server to the WebSphere MQ broker.