Abstract

OTS is a service under OMA that provides operations to control the scope and duration of a transaction. It allows multiple objects, potentially residing at different resource managers, to participate in a global atomic transaction and allows objects to associate their internal state changes with the transaction. OTS coordinates the completion of a distributed transaction by implementing presumed abort two phase commit (2PC) protocol across heterogeneous, autonomous, and distributed objects based systems. OTS is the object-oriented counterpart of the procedural transaction processing (TP) monitors in distributed environments. TP monitors provide transaction management (ACID properties and resource management, database connection management, load sharing between software servers, etc.) in procedural environments, whereas OTS only provides the transaction management function through its object interfaces. This chapter describes the main elements of the CORBA Object Transaction Service (OTS), including the OTS architecture and its different components. At the end of the chapter, an example of a CORBA OTS is given, followed by a comparison with the Microsoft transaction server.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.