CORBA 2.6 Getting Started Guide for Java

};
};
For more information on the Bootstrap Daemon, see the NonStop CORBA 2.6 Administration Guide.
Java Transaction Service (JTS)
The NonStop Java Transaction Service (JTS) is automatically installed with NonStop CORBA. JTS
implements the Java Transaction API defined by Sun Microsystems, Inc. This service supports
transaction processing between distributed objects.
NSots XID Broker
When transaction context is inherited from one process to another, an imported transaction branch is
created. A transaction branch is represented by a new TMF transaction identifier called the XID. The root
XID and any branch XIDs are not recognized by TMF or SQL as representing the same transaction. This
means that if a process such as an application starts a transaction and makes multiple invocations on
server processes, multiple XIDs can be created resulting in SQL errors or blocking. It is up to the
application designer to avoid this problem. If more than one NSotsTM is configured in a server pool,
multiple requests on the same transaction branch might be routed through more than one NSotsTM. This
situation is beyond the control of the application designer.
To solve this problem, NSOTS and NSJTS include an XID Broker function. The XID Broker brokers
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.