CORBA 2.3 Glossary (NonStop CORBA 2.3.7+)

trace facility
An object API that writes trace messages to an ASCII file. The Trace Facility can be used to
implement instrumentation in NonStop CORBA applications. You can add trace statements to
specific portions of NonStop CORBA applications or components to help troubleshoot program
code.
transaction
A series of logically related operations. A transaction is complete only when all operations in the
series have been performed. This manual makes a distinction between user or application
transactions, which are defined and controlled by application components, and services
transactions, which are defined and controlled by objects services such as the Naming Service.
transaction management
A set of tasks required to ensure satisfactory transaction processing. Transaction management
includes transaction control (the application logic that determines when a transaction starts and
stops, and when and how to abort a transaction), transaction protection, and auditing (logging the
progress of transactions to support request tracking and recovery). A NonStop CORBA application
controls transactions by using the Object Transaction Service (OTS).
Transaction Management Facility (TMF)
The facility that manages transactions on NonStop systems. TMF collaborates with the
transactional components of NonStop CORBA.
transaction protection
A feature that ensures consistency of databases and other stored data.
Transaction Service
A standard application service (one of the OMG Common Object Services) for ensuring the
consistency of a database or other stored information when a request involves multiple updates to
databases or state repositories.
usage binding
See binding.
vthread API
An object-oriented, portable API for multithreading provided by NonStop CORBA for use in C++
programs. (For Java programs, standard Java threading is recommended.) This API is implemented
as a set of jacket procedures built upon the NonStop DCE pthread API.
wrapping
A technique in which a component is given an interface that permits interoperation with
components based on a different technology. For example, a set of interacting Java object classes
can be wrapped in a single NonStop CORBA class, or the code of a legacy server can be used as
the implementation of an object supporting methods that correspond to functions of the server.
A recommended approach to wrapping is to develop a wrapper component that translates method