Request-reply messaging through a IBM MQ link
When a JMS producer sends a message, it can provide a reply-to destination. The reply-to destination is a JMS destination defined using the producer's messaging provider. This style of messaging is known as request-reply, or request and response. Request-reply messages can be exchanged across the WebSphere® MQ 鏈結 as either point-to-point or publish/subscribe messages.
The following combinations are possible for request-reply exchanges:
- Publication messages (for publish/subscribe messaging).
- Queue type reply-to destination.
- Topic type reply-to destination. This can be a permanent reply-to topic, which is defined to the publish/subscribe bridge on the IBM MQ 鏈結, or a temporary topic reply, where the topic name is assigned at runtime.
- Point-to-point messages.
- Queue type reply-to destination.
- Topic type reply-to destination. The reply-to destination must be a permanent reply-to topic; you cannot have a temporary topic reply for a point-to-point request message.
When the producer is a WebSphere Application Server
application that uses the default messaging provider, the reply-to
destination is a service integration JMS destination that typically
either points to a service integration queue, or comprises a topic
string and a service integration topic space.
- If the reply-to destination is a service integration queue, it is normally a queue in the same bus as the WebSphere Application Server application, so that the WebSphere Application Server application can consume the reply message from that reply-to queue.
- If the reply-to destination is a topic and the consumer is a IBM MQ program, you must configure the publish/subscribe bridge to ensure that the reply message can be routed back to the service integration bus so that the WebSphere Application Server application can receive it. Note that although IBM MQ JMS applications can reply to a topic, most other IBM MQ applications cannot.
When the producer is a IBM MQ JMS
application, the reply-to destination is a IBM MQ JMS destination that typically
either points to a IBM MQ queue
or is a topic string.
- If the reply-to destination is a IBM MQ queue, it is normally a queue in the queue manager, or shared queue in the queue-sharing group, that the IBM MQ application is using, so that the IBM MQ application can consume the reply message from that reply-to queue.
- If the reply-to destination is a topic and the consumer is a WebSphere Application Server application, you must configure the publish/subscribe bridge to ensure that the reply message can be routed back to IBM MQ so that the IBM MQ application can receive it.