CORBA 2.6 Programmer's Guide for Java

Naming Service (implemented as a server pool or NonStop TS/MP server class). NonStop
CORBA implements the Interoperable Naming Service specified in the OMG CORBA 2.6.1
specifications, with the exception that the Resolve Initial References (RIR) URL is not supported.
●
Event Service. A standard application service (one of the OMG Common Object Services) for
asynchronous communication among objects
●
Transaction Service. NonStop CORBA implements the Transaction Service by means of
components that collaborate with the Transaction Management Facility (TMF) on the NonStop
system. These components include special language-specific client stubs, a Transaction Service
process that can run as a TS/MP server pool, and a singleton transaction ID broker process. The
Java client stub (JTS) supports the Java Transaction Service (JTS) API.
●
You can configure and monitor NonStop CORBA components by using the NonStop Distributed
Component Console, a GUI-based configuration tool. For some application-specific configuration
settings you also use a command-line interface as described later in this manual.
For more information about the NonStop CORBA architecture, see Architectural Walkthrough in this
guide and the architecture section of the NonStop CORBA 2.6 Administration Guide.
NonStop CORBA Programming Environments
You can develop applications on the NonStop system directly. Alternatively, you can use JORB Lite to
develop and test on a workstation, then move the tested application to the NonStop system (JORB Lite is
not supported for production use). For more information on JORB Lite, see Developing Prototype
Applications on a PC in this guide.
About This Guide Chapter 2. NonStop CORBA
Administrative Environment