JMS Egress Connector

In order to use the JMS Egress Connector you must first select the “Spring JMS” dependency from the connector list when you are creating an empty Ultra project. If you have already created a project, you can add the “Spring JMS” dependency via Component Registry. From Tools menu, select Ultra Studio → Component Registry and from the Connectors list, select the “Spring JMS” dependency.

After that you need to specify a JMS Template to send messages to the destination. For this example let’s use ActiveMQ and if you have not already installed ActiveMQ please follow the installation guide.

Now if you open the project.xpml file in your project under Design view, there is a dropdown button names “Custom Template” and under that you will see an item named “ActiveMQ JMS” as shown below.

Select that and fill the required parameters and click save button. Now Ultra Studio will add all the resource beans required to handle JMS messages with minimum configuration to the project.xpml file.

In-order to send a message to a destination queue, first we need to inject a message to the UltraESB and for that let’s first add a JMS Ingress Connector to obtain a message into the UltraESB. If you are not familiar with JMS Ingress Connector, refer JMS Ingress Connector.

Next add a JMS Egress Connector and specify the Active MQ JMS Template and the destination queue name as shown below

After that connect JMS Ingress/Egress connectors as shown below.

Now after creating a run configuration [link to creating a run configuration] and running the project, you will be able to see that the message has been obtained from the remote JMS queue and sent it to the destination queue.

In this example let’s see how we can send a message obtained from a remote JMS queue can be sent to multiple destination queues as an atomic operation through a transaction. First create the flow as shown below

As you can see, there is one JMS Ingress Connector with a transaction manager specified and within the transaction scope there are two JMS Egress Connectors to sent the message to two destination queues after cloning the original message. If you run the project, you can see that the original message has been sent to both destination queues.

Now if we add an “Exceptional Flow End” element to the Clone Message as shown below and run the project, you will see that the message does not goes to the destination and rollback to the original source queue.

This happens because when we specify the transaction manager to the JMS Ingress Connector and include the egress connectors within the same transaction scope, all JMS queueing/de-queuing operations are bounded with a singe transaction and if the message flow fails within the transaction scope, the transaction will be rolledback.