AMQP Egress Connector

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

After that you need to specify a Connection Factory to connect to the AMQP Server. For this example let’s use Rabbit MQ and if you have not already installed Rabbit MQ, please follow the Installation Guide

In-order to use the transaction mode, you must first add the required resources in the project.xpml file. In the design view of the project.xpml file, under the "Custom Template" dropdown menu, select the "RabbitMQ with Transactions" item and fill the required properties in the pop-up modal and save it.

After that you will be able to see the required resources are added to the project.xpml file as shown below

After that, 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 AMQP Ingress Connector to obtain a message into the UltraESB. If you are not familiar with AMQP Ingress Connector, refer AMQP Ingress Connector.

Then, You need to specify the “rabbitMQ-UltraTxnManager” as the transaction manager and enable Channel transacted in the Ingress Connector apart from specifying the connection factory and source queue name.

After that, add a transaction scope and connect it to a Logger processing element to log the payload of the received message. Next add an AMQP Egress Connector and specify the Rabbit MQ Template and the destination queue name as shown below for the Egress Connector.

The full integration flow should be 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 and the payload is logged into the console as well.

Next, let’s add a Clone Message Processor and a "Exceptional Flow End" element as show below. Specify Keep Original as the "Exchange Pattern" and On Completion of Both as the "Completion Procedure" properties of the Clone Message Processor. Now the flow should look as below

Now if you run the project, you can see that the message does not get delivered to the destination queue even though the payload has been logged in the console. This happens because the message flow within the transaction scope fails since we are ending the flow by throwing an exception. Hence, the transaction will be rolledback and the message will be available on the original source queue for re-delivery.

When using the confirmation mode, you need to add a callback handler. In the project.xpml file in Design view select "RabbitMQ with Callback" from the "Custom Template" drop down menu. Specify the required properties and save the pop-up modal. Now you can see that the required resources are added as shown below

Now let’s create a simple flow as shown below

Now if you run this flow and send a message you will see an error message similar to below one

This means that the rabbit server has failed to find the destination queue and the message delivery has failed which results in a message flow failure.