Abstract: A transaction manager virtualization layer is provided for supporting multiple active transaction managers in a cluster or node. By virtualizing the transaction managers, applications and services are enabled to migrate across cluster nodes or even outside a cluster that includes relevant recovery mechanisms for transactions that are not completed at the time of migration. Multiple implementations of a transaction manager may be enabled to run side-by-side in a node or cluster allowing a rolling upgrade of transaction managers in clusters.

Abstract: The present invention extends to methods, systems, data structures, and computer program products for maintaining correct transaction results when transaction management configurations change. An intermediate transaction manager is transparently interposed between one or more resource managers and a plurality of transaction managers. The intermediate transaction manager multiplexes and intercepts calls and notifications between the one or more resource managers and the plurality of transaction managers. The intermediate transaction manager is configured to wrap recovery cookies with transaction manager type information and identity information that identify transaction managers. The information can be used to re-attach to the transaction manager to recover the correct outcome of the transaction. The intermediate transaction manager can also intercept recovery-complete calls directed to a specific transaction manager and send the recovery-complete call to each of the plurality of transaction managers.

Abstract: The present invention extends to methods, systems, and computer program products for synchronizing ambient state among multiple transaction managers. A coordinating transaction manager establishes transaction ambient state for an application initiated transaction. The coordinating transaction manager sends and a subordinate transaction manager receives a pointer to an ambient state delegate. The subordinate transaction manager sends a request to invoke the ambient state delegate to the coordinating transaction manager in response to receiving an operation. The coordinating transaction manager invokes the ambient state delegate to format the transaction ambient state for the subordinate transaction manager. The coordinating transaction manager sends and the subordinate transaction manager receives the formatted transaction ambient state such that the subordinate transaction manager can appropriately process the operation within the scope of the transaction.

Abstract: A computer system with a command shell that supports execution of commands within transactions. The command shell responds to commands that start, complete or undo transactions. To support transactions, the command shell may maintain and provide transaction state information. The command shell may interact with a transaction manager that interfaces with resource managers that process transacted instructions within transacted task modules to commit or roll back transacted instructions from those task modules based on transaction state information maintained by the shell. Parameters associated with commands can control behavior in association with transaction process, including supporting nesting transactions and non-nested transactions and bypassing transacted processing in some instances of a command.

Abstract: A transaction manager virtualization layer is provided for supporting multiple active transaction managers in a cluster or node. By virtualizing the transaction managers, applications and services are enabled to migrate across cluster nodes or even outside a cluster that includes relevant recovery mechanisms for transactions that are not completed at the time of migration. Multiple implementations of a transaction manager may be enabled to run side-by-side in a node or cluster allowing a rolling upgrade of transaction managers in clusters.

Abstract: A Registration protocol is used in transaction processing for normal operations. If an error occurs, the system reverts to a Full Broadcast protocol. The Registration Protocol reduces the number of messages that are sent among CPUs in a cluster thereby permitting performance improvements in the system. The Registration Protocol has Begin, DP2 Check, Phase 1 Flush and Phase 2 (lock release) phases just as does the Full Broadcast Protocol, thereby permitting the Full Broadcast protocol to step in at any phase after an error is detected.

Abstract: A Registration protocol is used in transaction processing for normal operations. If an error occurs, the system reverts to a Full Broadcast protocol. The Registration Protocol reduces the number of messages that are sent among CPUs in a cluster thereby permitting performance improvements in the system. The Registration Protocol has Begin, DP2 Check, Phase 1 Flush and Phase 2 (lock release) phases just as does the Full Broadcast Protocol, thereby permitting the Full Broadcast protocol to step in at any phase after an error is detected.