International Business Machines Corporation

Simon Anthony Holdsworth

Stanley Alan Smith

Thomas James Freund

Iain Stuart Houston

Edward Ellis Cobb

George Prentice Copeland

A system and method for using the TRAN procedural transaction coordinator, from the Encina product produced by Transarc Corporation, as the core of an OMG-compliant Object Transaction Service. The method allows the object-oriented Object Transaction Service to interoperate with Encina procedural applications. The interoperation involves coordinated processing of both object oriented transactional requests and Encina procedural transactional requests. Both object oriented and procedural requests can be part of a single atomic transaction without requiring gateways between the products. A system of implementation classes are used to transform object-oriented method invocations into the necessary procedural calls. The implementation classes also accept upcalls from the procedural TRAN and transform them into the necessary Object Transaction Service method invocations.

System and method for creating an object oriented transaction service

An object oriented transaction processing system based on the Object Management Group Object Management Architecture provides effective transaction scheduling and servicing through a combination of Object Transaction Services and a Transactional Object Request Broker. The Object Transactional Services manage the information needed to provide reliability in transactions, including a two phase commit process to implement transaction atomicity. The transactional Object Request Broker includes a transaction monitor facility to schedule objects to respond to object transaction requests. The tunable transaction monitor increases the efficiency of transaction processing by optimizing use of computer system resources allocated to servicing transactions. The transaction monitor activates the objects necessary to satisfy a transaction request. Activation includes an ability to start new processes or threads of execution or to reuse existing processes or threads. The transaction monitor interfaces to the Object Request Broker are clearly defined allowing substitution of different transaction monitors as dictated by the application.

Object oriented transaction monitor for distributed transaction

A system and process for enhancing procedural software using object oriented classes. Implementation classes are constructed that provide a defined object oriented interface to applications and are able to invoke the procedural software using defined procedural application program interfaces (APIs). New function is added to the software by adding classes that interface to the implementation classes or directly to the procedural API. The new function builds upon the procedural software without accessing the procedural software source code or modifying that source code.

System and method for functionally enhancing procedural software using

A system and method for effectively synchronizing data in an object oriented distributed transaction processing system employing a multilevel data store. Each object that maintains first-level volatile data registers as a synchronization object if unsynchronized changes to that data exist. A register object at each node tracks synchronized objects registered for that node. Each registered synchronization object, in turn, registers with its superior node when registered synchronization objects are present. A hierarchy of registered synchronization objects and synchronization objects is thereby created. The transaction termination process transmits a pre-prepare message to the registered synchronization hierarchy providing each synchronization object an opportunity to flush its data to the second-level persistent data store. The hierarchical structure of registered objects ensures that the minimum number of messages are transmitted over the network.

Growing community of inventors

Andover, United Kingdom

Simon Anthony Holdsworth