CORBA 2.6 Programmer's Guide for C++

Chapter 7. Managing Transactions

Components of Transaction Service Implementation

Use of TMF

Transaction Service Features Not Supported in NonStop CORBA

TransactionalObject Interface

Checked Transaction Behavior

Transaction Branches and the Diamond Access Problem

This section describes the NonStop CORBA implementation of the Transaction Service (formerly known

as the Object Transaction Service, or OTS) and explains programming considerations for transactions

in NonStop CORBA applications.

The Transaction Service components of NonStop CORBA for C++ applications are referred to

collectively as NSOTS. Together, they implement the CosTransactions module of the Transaction

Service to provide distributed transactional execution.

The OTS_Bank sample is a set of programs that illustrate the use of NSOTS. The Readme file for this

sample provides a description and walkthrough of these programs, including how to build and run them.

Components of Transaction Service

Implementation

NSOTS consists of the following components:

OTS, a special client stub that implements the OMG Transaction Service API●

NSotsTM, a process that collaborates with the Transaction Management Facility (TMF) on the

NonStop system to manage transactions and that can run as a TS/MP server pool

●

NSotsXID, a singleton process used to broker transaction identifiers (XIDs) when NSotsTM runs

as a TS/MP server pool with multiple processes

●

Use of TMF

NSOTS uses the NonStop Transaction Management Facility, or TMF, for transaction management.

NSOTS serves in both superior and subordinate roles to TMF.