JMS Snap Pack

Overview

Messaging is a method of communication between software components or applications. The Java Message Service (JMS) API is a Message Oriented Middleware (MOM) that allows applications to create, send, receive, and read messages using reliable, asynchronous, loosely coupled communication. This approach allows software components to communicate indirectly with each other. The benefits of this message include senders not needing to have precise knowledge of their receivers.

This Snap Pack contains the following Snaps:
  • JMS Acknowledge: You can use this Snap to acknowledge the Java Message Service (JMS) messages read by a JMS consumer used in the upstream Snap.
  • JMS Consumer: You can use this Snap to fetch the Java Message Service (JMS) messages.
  • JMS Producer: You can use this Snap to create JMS messages from incoming JSON documents and put them into a JMS destination.

Prerequisites

Supported versions

  • JMS version 5.15.0
  • JMS providers:
    • Apache ActiveMQ v5.15.9
    • JBOSS HornetQ v2.4

Supported models

The JMS specification supports two models:

  • Point-to-point

  • Publish and subscribe

Point-to-Point
A point-to-point (PTP) product or application is built on the concept of message queues, senders, and receivers. Each message is addressed to a specific queue, and receiving clients extract messages from the queues established to hold their messages. Queues retain all messages sent to them until the messages are consumed or expire.

PTP messaging has the following characteristics:

  • Each message has only one consumer.

  • A sender and a receiver of a message have no timing dependencies. The receiver can fetch the message whether or not it was running when the client sent the message.

  • The receiver acknowledges the successful processing of a message.

Publish and Subscribe
In a publish/subscribe (pub/sub) product or application, clients address messages to a topic, which functions somewhat like a bulletin board. Publishers and subscribers are generally anonymous and can dynamically publish or subscribe to the content hierarchy. The system takes care of distributing the messages arriving from a topic’s multiple publishers to its multiple subscribers. Topics retain messages only as long as it takes to distribute them to current subscribers.

Pub/sub messaging has the following characteristics:

  • Each message can have multiple consumers.

  • Publishers and subscribers have a timing dependency. A client that subscribes to a topic can consume only messages published after the client has created a subscription, and the subscriber must continue to be active in order for it to consume messages.

JMS Building Blocks

JMS building blocks contains:

  • Connection

  • Message producers

  • Message consumers