There are three types of transaction resource managers:
Databases - Use of transactions prevents databases from being left in inconsistent states due to incomplete updates. For information about JDBC transaction isolation levels, see Using JDBC Transaction Isolation Levels.
The Application Server supports a variety of JDBCTM XA drivers. For a list of the JDBC drivers currently supported by the Application Server, see the Sun Java System Application Server Enterprise Edition 8.2 Release Notes. For configurations of supported and other drivers, see Configurations for Specific JDBC Drivers.
Java Message Service (JMS) Providers - Use of transactions ensures that messages are reliably delivered. The Application Server is integrated with Sun Java System Message Queue, a fully capable JMS provider. For more information about transactions and the JMS API, see Chapter 14, Using the Java Message Service.
J2EETM Connector Architecture (CA) components - Use of transactions prevents legacy EIS systems from being left in inconsistent states due to incomplete updates. For more information about connectors, see Chapter 9, Developing Connectors.
For details about how transaction resource managers, the transaction service, and applications interact, see the Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.
In the Application Server, the transaction manager is a privileged interface. However, applications can access UserTransaction. For more information, see Naming Environment for J2EE Application Components.