Using JDBC XA Drivers with WebLogic Server 10-5
10.3.4 Known Sybase jConnect 5.5 and 6.0XA Issues
These are the known issues and Oracle workarounds:
10.4 Using Other XA Drivers
To use other XA-compliant JDBC drivers, you must include the path to the driver class libraries in your CLASSPATH and follow the configuration instructions provided by
the vendor.
Table 10–3 Sybase jConnect 5.5XA Driver: Java Client Connection Properties
Property Name Property Value
ds.setPassword password
ds.setUser username
ds.setNetworkProtocol Tds
ds.setDatabaseName database-name
ds.setResourceManagerName Lrm name in xa_config file
ds.setResourceManagerType 2
ds.setServerName machine host name
ds.setPortNumber port
Typically 4100
Table 10–4 Sybase jConnect 5.5 and 6.0 Known Issues and Workarounds
Description Sybase
Bug CommentsWorkarounds for
WebLogic Server When calling setAutoCommittrue the
following exception is thrown: java.sql.SQLException: JZ0S3: The
inherited method setAutoCommittrue cannot be used in this subclass.
10726192 No workaround. Vendor fixed in jConnect 6.0.
When driver used in distributed transactions, calling
XAResource.endTMSUSPEND followed
by XAResource.endTMSUCCESS results in XAER_RMERR.
10727617 WebLogic Server has provided an internal workaround for this bug:
Set the data source connection pool property XAEndOnlyOnce=true.
Vendor fix has been requested.
10-6 Programming JTA for Oracle WebLogic Server
11
Coordinating XAResources with the WebLogic Server Transaction Manager 11-1
11
Coordinating XAResources with the WebLogic Server Transaction Manager
External, third-party systems can participate in distributed transactions coordinated by the WebLogic Server transaction manager by registering a
javax.transaction.xa.XAResource implementation with the WebLogic Server
transaction manager. The WebLogic Server transaction manager then drives the XAResource as part of its Two-Phase Commit 2PC protocol. This is referred to as
exporting transactions.
By exporting transactions, you can integrate third-party transaction managers with the WebLogic Server transaction manager if the third-party transaction manager
implements the XAResource interface. With an exported transaction, the third-party transaction manager would act as a subordinate transaction manager to the WebLogic
Server transaction manager.
WebLogic Server can also participate in distributed transactions coordinated by third-party systems sometimes referred to as foreign transaction managers. The
WebLogic Server processing occurs as part of the work of the external transaction. The third-party transaction manager then drives the WebLogic Server transaction manager
as part of its commit processing. This is referred to as importing transactions.
Details about coordinating third-party systems within a transaction exporting transactions are described in this section. Details about participating in transactions
coordinated by third-party systems importing transactions are described in Chapter 12, Participating in Transactions Managed by a Third-Party Transaction
Manager. Note that WebLogic Server IIOP, WebLogic Tuxedo Connector WTC
gateway, and Oracle Java Adapter for Mainframe JAM gateway internally use the same mechanism described in these chapters to import and export transactions in
WebLogic Server.
The following sections describe how to configure third-party systems to participate in transactions coordinated by the WebLogic Server transaction manager:
■
Section 11.1, Overview of Coordinating Distributed Transactions with Foreign XAResources
■
Section 11.2, Registering an XAResource to Participate in Transactions
■
Section 11.3, Enlisting and Delisting an XAResource in a Transaction
■
Section 11.4, Commit processing
■
Section 11.5, Recovery
■
Section 11.6, Resource Health Monitoring
■
Section 11.7, Java EE Connector Architecture Resource Adapter
11-2 Programming JTA for Oracle WebLogic Server
■
Section 11.8, Implementation Tips
■
Section 11.9, Changes in the Resource Registration Name
■
Section 11.10, FAQs
■
Section 11.11, Additional Documentation about JTA
11.1 Overview of Coordinating Distributed Transactions with Foreign XAResources