Setting up a JMS local transaction - 7.3

JMS (Mediation)

Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
Talend Studio
Data Governance > Third-party systems > Messaging components (Mediation) > JMS components (Mediation)
Data Quality and Preparation > Third-party systems > Messaging components (Mediation) > JMS components (Mediation)
Design and Development > Third-party systems > Messaging components (Mediation) > JMS components (Mediation)
Last publication date

This scenario applies only to Talend Open Studio for ESB, Talend ESB, Talend Data Services Platform, Talend MDM Platform, Talend Real Time Big Data Platform, and Talend Data Fabric.

For more technologies supported by Talend, see Talend Mediation Components.

In this scenario, a local transaction with three steps is performed to send, test and consume a JMS message:

  1. The first Route is used to send a "hello world!" message to feed the queue.hello JMS queue.

  2. The second Route is used to test the received JMS message. This message is redelivered six times to the queue.hello queue and is then moved to the Dead Letter JMS queue. The Route is programmed to throw an exception every time an exchange is processed by the Route.

  3. The last Route is used to consume the "hello world!" message from the Dead Letter JMS queue.

In this use case, we use the local ActiveMQ server to handle messages between different Routes. The ActiveMQ server need to be started before executing the Routes. For more information on installing and launching ActiveMQ server, see the Apache Web site