+

Search Tips   |   Advanced Search

Request-reply messaging through a WebSphere 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 link as either point-to-point or publish/subscribe messages.

The following combinations are possible for request-reply exchanges:

  1. Publication messages (for publish/subscribe messaging).

    1. Queue type reply-to destination.

    2. Topic type reply-to destination. This can be a permanent reply-to topic, which is defined to the publish/subscribe bridge on the WebSphere MQ link, or a temporary topic reply, where the topic name is assigned at runtime.

  2. Point-to-point messages.

    1. Queue type reply-to destination.

    2. Topic type reply-to destination. The reply-to destination must be a permanent reply-to topic; we cannot have a temporary topic reply for a point-to-point request message.

When the producer is a WAS 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.

When the producer is a WebSphere MQ JMS application, the reply-to destination is a WebSphere MQ JMS destination that typically either points to a WebSphere MQ queue or is a topic string.


Subtopics