Use of XA-Compliant Resource to Interoperate with Object Transaction Service
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2005-Mar-30
Holdsworth, SA: AUTHOR [+1]
A technique for enabling an existing XA-compliant Resource Manager to operate with an OMG compliant Object Transaction Service. The technique utilizes the OMG Resource class from the OMG specified Transactions module to pass XA operations to an XA-compliant Resource Manager.
Use of XA-Compliant Resource to Interoperate with Object
for enabling an existing XA-compliant Resource
Manager to operate with an OMG compliant Object Transaction Service.
The technique utilizes the OMG Resource class from the OMG specified
Transactions module to pass XA operations to an XA-compliant Resource
technique allows an existing XA-compliant Resource Manager
implementation to be extended to conform to the OMG standard and be
used by client code using a new object interface, as well as being
accessible to existing procedural client code, possibly within the
same transaction. The technique does not require changes to the
existing Resource Manager.
move forward from the procedural application base
they are currently running with to new object-oriented applications,
some significant transitions must be made. Because of the scope of
transition, customers will not be moving over to the object-oriented
environment immediately and will likely begin introducing
object-oriented applications and Resource Managers that must
interoperate with procedural applications and resources (i.e., OO
applications using existing data bases).
Management Group (OMG) has recently adopted the
final specification of a standard for Object Transactions called the
Object Transaction Service (OTS).
specification defines a framework of cooperating
classes for implementing object transaction capability. It is
designed to allow for transactional behavior in a distributed
heterogeneous environment based on the OMG CORBA architecture.
specification defines the Resource interface, which is
used by Resource Managers for involvement in transactions. A
Resource object is registered with the Coordinator for each
transaction that the Resource Manager wishes to be involved in; the
Resource encapsulates the interaction between the Coordinator and the
Resource Manager for completion of a transaction.
The problem that
must be solved is building the object
transaction services and making them interoperate with procedural
based resources. As Resource Manager (RM) vendors have created their
products, writing them to operate against standard interfaces allows
them to more easily use their RMs on multiple operating systems. The
XA interface defined by the X/Open Distributed Transaction Processing
(DTP) model is one of the commonly used protocols that RM vendors
described here enables XA-compliant Resource
Managers to operate with th...