Introduction and Roadmap

This section describes the contents and organization of this guide—Programming WebLogic JTA.

Document Scope and Audience

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™ 2, Enterprise Edition (J2EE) programming, and transaction processing concepts.

Guide to this Document

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.
Java Transaction API and BEA 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 Third-Party 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.

Related Documentation

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 with WebLogic Server is a guide to developing WebLogic Server applications.
Deploying Applications to WebLogic Server is the primary source of information about deploying WebLogic Server applications.

Samples and Tutorials

In addition to this document, BEA Systems 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 Start menu on Windows machines. For Linux and other platforms, you can start the Examples server from the WL_HOME\samples\domains\wl_server directory, where WL_HOME is the top-level installation directory for WebLogic Platform.

Avitek Medical Records Application (MedRec) and Tutorials

MedRec is an end-to-end sample J2EE 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 J2EE features, and highlights BEA-recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Platform.

New and Changed Features in This Release

The following sections describe new features and changes for JTA in WebLogic Server 9.2:

LLR Support for Transaction Recovery Service Migration
For a comprehensive listing of the new WebLogic Server features introduced in release 9.2, see “ What's New in WebLogic Server 9.2” in Release Notes.

LLR Support for Transaction Recovery Service Migration

This feature allows the Logging Last Resource (LLR) transaction optimization to use transaction recovery service migration after a failover. See Failover Considerations for LLR.