Configuring and using XA distributed transactions in WebSphere Studio
From the developerWorks archives
Date archived: July 7, 2017 | First published: June 01, 2004
This article describes distributed transactions and shows you how to configure a WebSphere Studio Application Developer test server with XA resources for DB2, Oracle, and JMS that can be used together in a distributed transaction. The article describes an example session bean that updates both databases and sends a JMS message, all in the same transaction. The Oracle database must also be configured to support XA transactions, so the article shows the Java exceptions that occur when it is not configured properly, and how to fix these problems.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.