This chapter includes the following sections:
This document is written for application developers who are interested in building transactional Java applications that run in the WebLogic Server environment. It is assumed that readers are familiar with the WebLogic Server platform, Java Platform, Enterprise Edition (Java EE) programming, and transaction processing concepts.
This chapter, Introduction and Roadmap, introduces the organization of this guide.
Introducing Transactions introduces transactions in EJB and RMI applications running in the WebLogic Server environment. This chapter also describes distributed transactions and the two-phase commit protocol for enterprise applications.
Configuring Transactions describes how to administer transactions in the WebLogic Server environment.
Managing Transactions provides information on administration tasks used to manage transactions.
Transaction Service describes the WebLogic Server Transaction Service.
Transaction Recovery Spanning Multiple Sites or Data Centers describes best practices for XA transaction disaster recovery of WebLogic domains across physical sites to provide active-active disaster recovery (AADR).
Configuring Secure Inter-Domain and Intra-Domain Transaction Communication describes how to configure secure communication between servers during a transaction.
Java Transaction API and Oracle WebLogic Extensions provides a brief overview of the Java Transaction API (JTA).
Transactions in EJB Applications describes how to implement transactions in EJB applications.
Transactions in RMI Applications describes how to implement transactions in RMI applications.
Using JDBC XA Drivers with WebLogic Server describes how to configure and use third-party XA drivers in transactions.
Coordinating XAResources with the WebLogic Server Transaction Manager describes how to configure third-party systems to participate in transactions coordinated by the WebLogic Server transaction manager.
Participating in Transactions Managed by a Third-Party Transaction Manager describes the process for configuring and participating in foreign-managed transactions.
Troubleshooting Transactions describes how to perform troubleshooting tasks for applications using JTA.
This document contains JTA-specific design and development information. For comprehensive guidelines for developing, deploying, and monitoring WebLogic Server applications, see the following documents:
Developing Applications for Oracle WebLogic Server is a guide to developing WebLogic Server applications.
Deploying Applications to Oracle WebLogic Server is the primary source of information about deploying WebLogic Server applications.
In addition to this document, Oracle optionally provides a variety of code samples and tutorials for developing transactional applications. The examples and tutorials illustrate WebLogic Server in action, and provide practical instructions on how to perform key application development tasks. You can start the Examples server from the ORACLE_HOME
\user_projects\domains\wl_server
directory, where ORACLE_HOME
is the directory you specified as Oracle Home when you installed Oracle WebLogic Server. For more information, see "Sample Applications and Code Examples" in Understanding Oracle WebLogic Server.
MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.
MedRec demonstrates WebLogic Server and Java EE features, and highlights Oracle-recommended best practices. MedRec is optionally installed in the WebLogic Server installation. You can start MedRec from the ORACLE_HOME
\user_projects\domains\medrec
directory, where ORACLE_HOME
is the directory you specified as Oracle Home when you installed Oracle WebLogic Server. For more information, see "Sample Applications and Code Examples" in Understanding Oracle WebLogic Server.
This release includes the following new and changed JTA features:
XA transaction affinity improves performance by allowing server instances that are participating in a global transactions to service related requests rather than load-balancing these requests to other member servers. See XA Transaction Cluster Affinity.
Improved XA transaction performance by eliminating TLogs when XA transactions span a single Transaction Manager (TM). XA transaction resources (Determiners) are used during transaction recovery when a TLog is not present. See XA Transactions without Transaction TLog Write.
Support for XA transaction recovery of WebLogic domains across physical sites as part of a Disaster Recovery (DR) solution See Transaction Recovery Spanning Multiple Sites or Data Centers.
For a comprehensive listing of the new WebLogic Server features introduced in this release, see What's New in Oracle WebLogic Server 12.2.1.2.0.