See Also:
■
“Transactions in Java EE Technology” on page 144
■
“Conguring Transactions” on page 145
Transactions in Java EETechnology
Transaction processing involves the following ve participants:
■
Transaction Manager
■
Enterprise Server
■
Resource Manager(s)
■
Resource Adapter(s)
■
User Application.
Each of these entities contribute to reliable transaction processing by implementing the
dierent APIs and functionalities, discussed below:
■
The Transaction Manager provides the services and management functions required to
support transaction demarcation, transactional resource management, synchronization,
and transaction context propagation.
■
The Enterprise Server provides the infrastructure required to support the application
runtime environment that includes transaction state management.
■
The Resource Manager (through a resource adapter) provides the application access to
resources. The resource manager participates in distributed transactions by implementing a
transaction resource interface used by the transaction manager to communicate transaction
association, transaction completion and recovery work. An example of such a resource
manager is a relational database server.
■
A Resource Adapter is a system level software library that is used by the application server or
client to connect to a Resource Manager. A Resource Adapter is typically specic to a
Resource Manager. It is available as a library and is used within the address space of the
client using it. An example of such a resource adapter is a JDBC driver.
■
A Transactional User Application developed to operate in an application server
environment looks up transactional data sources and, optionally, the transaction manager,
using JNDI. The application may use declarative transaction attribute settings for enterprise
beans or explicit programmatic transaction demarcation.
See Also:
■
“What is a Transaction?” on page 143
■
“Conguring Transactions” on page 145
AboutTransactions
SunGlassFishEnterpriseServer2.1AdministrationGuide • December2008144