CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.7+)
requests for imported transactions within the pool of NSotsTMs by routing secondary import requests
back to the NSotsTM that originally imported the transaction. In previous versions of NSOTS and
NSJTS, the broker function was provided through a shared file. The current version of NSOTS and
NSJTS replaces the file implementation with a singleton process called NSotsXID.
Object by Value
NonStop CORBA supports Object by Value, allowing applications to pass objects and parameters by
value rather than by reference. The receiving side of an object passed by value receives a description of
the "state" of the object and then instantiates a new object with that state but having a separate identity
from that of the sending side. Once the parameter-passing operation is complete, no relationship exists
between the two instances.
Event Service
The Event Service allows for decoupled communication between suppliers and consumers of events
through an event channel. Suppliers and consumers register with the event channel. At registration, the
supplier/consumer indicates either the push or pull model. For the push model, the supplier initiates the
transfer of the event. For the pull model, the consumer requests the event transfer. NonStop CORBA
supports both the generic and the typed communication models. The Event Service also installs
automatically when you install NonStop CORBA.
Error Logging and Tracing
All server pools and system infrastructure in NonStop CORBA provide user-configurable error logging,
tracing, and event-channel messaging. Application programmers may instrument objects that take
advantage of these debugging features.
NonStop CORBA also supplies an IDL interface to the Error Logging facility, allowing the developer to
log application-specific information.
Legacy Wrapper Interface
Legacy wrapping is never an easy task because the legacy application code itself may require
modification. However, HP's supplied set of generic legacy wrappers act as an integration framework for
your legacy application. You do not need to modify your legacy application, and your legacy application
can interoperate transparently with existing CORBA objects and components.
Prev Up Next
Chapter 1. Overview of Distributed
Object Computing and CORBA
Home
Chapter 3. Installing NonStop CORBA