How to propagate a global transaction between Oracle WebLogic 11g and IBM WebSphere 8.0 using WS-AT – part 2

This post is a follow up on the post where we described how to propagate a transaction from WebLogic 11g (WLS) to WebSphere 8 (WAS). Post is located here: http://www.soa.si/2011/12/20/how-to-propagate-a-global-transaction-between-oracle-weblogic-11g-and-ibm-websphere-8-0-using-ws-at/. It is describing transaction propagation in the opposite direction from WLS to WAS using WS-Atomic Transactions.

In this follow up I will describe transaction propagation from WAS to WLS using WS-AT.  I am using the same two JAX-WS Web Services as are used in the previous post. One is deployed on WAS and one on WLS. They both contain operation insert() which we use for inserting a record in a database table. For this each environment uses a separate database and has configured a corresponding XA Data Source. We implemented additional JAX-WS Web Service facade. Its role is to start a global transaction and invoke other two services inside this transaction.

Main steps:

• From the previous post we use XA-enabled data source and both web services that participate in a global transaction.
• Next step is to configure WAS transaction service for interoperability and proper WS-AT version (we used WS-AT version 1.2) using WAS administrative console.
• We can also configure WAS to use Secure Socked Layer connection for WS-AT coordination or disabling it in case we do not want to use it.
• Implement the facade Web Service. There we are calling both web services in one global transaction which is controlled using Java Transaction API (JTA). Both service clients must have attached proper WS-AT policy. We also recommended using WS-Addressing.

No tags