7
Transaction Handling

This chapter covers transaction management for CORBA applications. The CORBA developer can choose to use one of the following transactional APIs provided:

• Java Transaction API (JTA) by Sun Microsystems is a method for creating global transactions in a pure Java environment. JTA can be used in either a single or two-phase commit transaction. In addition, it can be demarcated either from the client or the server object.

• Java Transaction Service (JTS) is a mapping of a subset of the OMG Object Transaction Service (OTS) API that is supplied with Oracle8i JServer. The CORBA developer invokes a transaction service to enable transactional properties for distributed objects in either a Java or non-Java environment. JTS can only be used in a single-phase commit transaction. In addition, it only supports client-side demarcation.

In Oracle8i, Java Transaction API (JTA) 1.0.1 for managing transactions. This chapter assumes that you have a working knowledge of JTA. The discussion focuses mostly on examples and explaining the differences between the Sun Microsystems JTA specification and the Oracle JTA implementation. See http://www.javasoft.com for the Sun Microsystems JTA specification.

• Transaction Overview

• JTA Server-Side Demarcation

• JTA Client-Side Demarcation

• Configuring Two-Phase Commit Engine

• Creating DataSource Objects Dynamically

• Setting the Transaction Timeout

• Java Transaction Service

• Transaction Service Interfaces

• JDBC Restrictions

---