Table of Contents
Just a second...

DEPRECATED: Receiving data from JMS

Diffusion™ clients can receive data from a Java Message Service (JMS) provider through the JMS adapter v5.1. A client can receive updates from a JMS topic or messages from a JMS queue.

Note: The JMS Adapter v5.1 is now deprecated. Use the new JMS adapter instead. For more information, see JMS.

Receiving updates from a JMS topic

This section shows how a client receives updates from the JMS topic XYZ.

  1. Diffusion client creates a subscription to the topic jms/topic/XYZ.
  2. Once a message has been sent from the source system into the JMS server, the Diffusion client receives an initial topic load message.
  3. Subsequent messages from the source system result in delta messages being delivered to the Diffusion client.
    Figure 1. Subscription flow The Diffusion client subscribes to "jms/topic/XYZ" on the Diffusion server. If the topic "XYZ" does not exist, the Diffusion server creates a consumer for "XYZ" on the JMS server. The JMS client sends a text message to the "XYZ" on the JMS server. The JMS server sends the test message to the Diffusion server. The Diffusion server creates the topic "jms/topic/XYZ" and subscribes the Diffusion client to it. The Diffusion server sends a topic message to the Diffusion client.

Receiving messages from a JMS queue

The same process occurs for receiving messages from JMS queues, with the following differences:

  • Other clients subscribing to the same JMS queue (either through Diffusion or directly using JMS) might receive the message instead of our client.
  • All messages originating from JMS queues are initial topic load messages. Since a sequence of messages from a JMS queue are unlikely to always be delivered to the same client, the concept of delta messages does not readily apply and the full message state must be supplied every time.