Skip to main content

JMS Activities

Use the JMS activity group to connect workflows to Java Message Service brokers through queues or topics. JMS activities support inbound event sources, outbound sends, request/reply exchanges, manual acknowledgement, and replies to an incoming message.

Available activities​

ActivityPurpose
JMS ConnectionDefines the broker URL, credentials, client options, and optional JNDI mode used by other JMS activities
JNDIDefines a JNDI context for looking up a connection factory and destinations
JMS ReceiverConsumes messages from a queue or topic and starts a workflow
JMS SenderSends a mapped message to a queue or topic
JMS Request ReplySends a request and waits for a correlated reply
AcknowledgeAcknowledges a message when the receiver uses manual acknowledgement
Reply To MessageSends a response to the reply destination associated with an incoming message

Configure a JMS flow​

  1. Add a JMS Connection resource and configure the broker connection.
  2. If your provider requires directory lookup, configure JNDI and reference it from the connection.
  3. Add JMS Receiver, JMS Sender, or JMS Request Reply to the workflow.
  4. Select the connection and specify the destination name and queue or topic type.
  5. Map the message body, headers, and properties required by the receiving system.
  6. Test in Development with a non-production destination.

For manual acknowledgement, add Acknowledge only after the workflow has completed the work that must succeed before the broker removes the message. Use Reply To Message when the incoming request supplies a reply destination and correlation context.

Operational guidance​

  • Preserve correlation IDs for request/reply and distributed tracing.
  • Use durable subscriptions only when the broker and integration require them.
  • Configure redelivery and dead-letter behavior on the broker and account for duplicate delivery in the workflow.
  • Do not acknowledge a message before downstream processing succeeds.
  • Monitor queue depth, dead-letter counts, and consumers from Messaging.