US 7,743,083 B2Granted

Common transaction manager interface for local and global transactions

AssigneeOracle America, Inc.

InventorsSankara R. Bhogi, Ajay Kumar, Bala Dutt, Venugopal Rao K, Senthil K. Krishnan, Srinivasan Kannan

Life of this patent

Estimating the term…

Loading patent…

Abstract

A system and method for implementing a common transaction manager interface. A system may implement an application server with a transaction manager module configured to provide a common application interface to a local transaction manager and a global transaction manager. The transaction manager module may be configured to determine if a transaction initiated by an application component should be managed by the local transaction manager or the global transaction manager. The local transaction manger may be configured to create a local transaction object for each transaction managed by the local transaction manager, and the global transaction manger may be configured to create a global transaction object for each transaction managed by the global transaction manager. The local transaction objects and the global transaction objects may provide a common application interface for implementing their respective transactions.

Claims48

Dependent claims

A system, comprising:

one or more processors;
memory coupled to the one or more processors and configured to store program instructions executable by the one or more processors to implement an application server configured to support one or more application components, wherein the application server comprises:
a transaction manager module configured to provide a common interface for both local and global transactions during a same execution instance of the application server, wherein the common interface comprises a common application interface to a local transaction manager within the application server and to a global transaction manager within the application server;
wherein, during the same execution instance of the application server, the transaction manager module is further configured to provide runtime logic to:
determine a given one of said transactions initiated by a given application component is to be managed by the local transaction manager, and determine an other one of said transactions issued by a given application component is to be managed by the global transaction manager;
wherein, during the same execution instance of the application server, the one or more application components use the common application interface to initiate said transactions regardless of a transaction manager type for transactions;
and
wherein one or more of the local transactions initiated via the common application interface are not part of any global transaction, do not involve any communication between the application component and the global transaction manager, and are not controlled by the global transaction manager.

5 more elements

A method, comprising:

an application component invoking runtime logic in an application server during an execution instance of the application server to determine a transaction manager type for a global or local transaction to be initiated by the application component;
in response to being invoked by the application component, the runtime logic accessing a transaction type specified for the application component at a component, module, or instance-wide level and returning the transaction manager type to the application component;
to initiate said transaction, the application component calling a common transaction manager interface that is configured to initiate both global and local transactions in response to calls;
wherein, during the same execution instance of the application server, the application component uses the same common transaction manager interface to initiate the transaction regardless of the transaction manager type returned by the runtime logic;
wherein the common transaction manager interface is configured to communicate with a global transaction manager and a local transaction manager;
if the runtime logic returns the transaction manager type of said transaction initiated by the common transaction manager interface as global, managing the transaction using said global transaction manager without utilizing said local transaction manager for that transaction;
and
if the runtime logic returns the transaction manager type of said transaction initiated by the common transaction manager interface as local, managing the transaction using said local transaction manager without utilizing said global transaction manager for that transaction.

5 more elements

A computer readable storage medium, comprising program instructions, wherein the program instructions are computer-executable to:

invoke runtime logic, by an application component, in an application server to determine a transaction manager type for a global or local transaction to be initiated by the application component during an execution instance of the application server;
in response to the runtime logic being invoked, access a transaction type specified for the application component at a component, module, or instance-wide level and return the transaction manager type, by the runtime logic, to the application component;
to initiate said transaction, call a common transaction manager interface via the application component;
wherein said common transaction manager interface is configured to initiate both global and local transactions in response to calls;
wherein, during the same execution instance of the application server, the application component uses the same common transaction manager interface to initiate the transaction regardless of the transaction manager type returned by the runtime logic;
wherein the common transaction manager interface is configured to communicate with a global transaction manager and a local transaction manager;
manage the transaction initiated by the common transaction manager interface using said global transaction manager without utilizing said local transaction manager for that transaction, if the runtime logic returns the transaction manager type as global;
manage the transaction initiated by the common transaction manager interface using said local transaction manager without utilizing said global transaction manager for that transaction, if the runtime logic returns the transaction manager type as local;
wherein if the transaction manager type returned by the runtime logic is global, the global transaction manager creating a global transaction object to implement the transaction;
wherein if the transaction manager type returned by the runtime logic is local, the local transaction manager creating a local transaction object to implement the transaction;
and
wherein the global and local transaction objects provide a common application interface for the transaction during the same execution instance of the application server.

9 more elements

Dependencies are inferred from the claim text.