Transactional processing with WAS

You must consider how your business requirements affect the way in which your applications interact with your company's data. One of the most basic considerations is whether or not the deployed application needs to support transactions.

Transactional processing requires that multiple database operations be performed as a single unit of work to avoid corrupting the database or databases. This single unit of work either succeeds or fails in its entirety.

For information about administering the transaction service for an application server, see Administer transactions in the Administration topic.

If your application has such requirements, refer to the following topics for an overview of transactions as well as details about how WAS and DB2 Universal Database (UDB) for iSeries support transactional processing:

Overview of transactions
This topic introduces the basic concepts of database transactions.

Distributed transactions and the two-phase commit protocol
This topic describes the two-phase commit protocol, which is used for distributed transactions.

Transaction log files
WAS uses transaction log files to track distributed transaction commit operations. This topic provides information about WebSphere transaction log files.

Transaction states
This topic is a reference for all possible transaction states.

Transaction locking and isolation considerations
DB2 UDB for iSeries supports five isolation levels. This topic discusses the implementation of isolation levels, including both shared and exclusive locks.

Use local transactions
This topic describes local transaction containment (LTC) support and how it relates to the settings of the local transaction extended deployment descriptors. This topic also describes points to consider to help you best configure transaction support for some example scenarios that use local transactions.

Local and global transaction considerations
Application resources can participate in global transactions, but how they do so depends on the underlying transaction support of the resource provider. This topic provides considerations for using local and global transactions in WAS.