Working with global transactions and quality of service

This recipe will show the different error scenarios, which we can have with XA and non XA enabled resources and how QoS can influence this.

Getting ready

For this recipe, we will use a setup with three queues from the standard environment, a proxy service that consumes messages from a JMS queue, and a business service that sends th messages to another JMS queue:

You can import the OSB project into Eclipse from \chapter-10\getting-ready\working-with-global-transactions-and-qos.

How to do it...

First, we will show you the behaviour of the service without a global transaction.

In Eclipse OEPE, perform the following steps:

1. Navigate to the proxy service JMSConsumer.

2. Navigate to the Transport tab.

3. Change the Endpoint URI to use the non-XA JMS Connection Factory : jms://[OSBServer]:[Port]/weblogic.jms.ConnectionFactory/jms.SourceQueue

   

4. Navigate to the Message Flow tab.

5. The message flow contains a Pipeline Pair node and a Route node with a Routing action...