CORBA 2.6.1 Getting Started Guide for C++

Language bindings
Portable Object Adapter (POA)
Object Method Invocation
Naming Service and Interoperable Naming Service
Bootstrap Daemon (BSD)
OTS/JTS
NSots XID Broker
Object by Value
Event Service
Error Logging and Tracing
Portable Interceptors
Legacy Wrapper Interface
IIOP and GIOP Protocol Support
Internet Inter-ORB Protocol (IIOP) is the standard protocol that different ORBs must use to communicate across the Internet. This protocol is
standardized by the OMG. Because the objects that you write in NonStop CORBA comply with IIOP they can be used by other ORBs and
clients, and NonStop CORBA clients can use the objects located on other ORBs that support IIOP.
NonStop CORBA 2.6.1 supports GIOP versions 1.0, 1.1, and 1.2. If a client from another ORB uses an earlier version of GIOP, NonStop
CORBA automatically adopts that version.
IIOP/SSL Protocol Support
IIOP/SSL extends the support of the IIOP protocol to provide security features at the transport layer. IIOP/SSL adds confidentiality,
authentication, and message integrity to IIOP communications. Installation of IIOP/SSL is optional.
IDL Compiler
The NonStop CORBA IDL compiler (NSDIDL) is based on the CORBA 2.6.1 specifications defined by the OMG, and on the resolution of Issue
4160 (ptc/2003–03–09). Any differences between the specification and the NonStop CORBA implementation are noted in the NonStop CORBA
2.6.1 Programmer's Reference. The compiler generates stubs and skeletons for use by client objects and server objects, respectively.
Language Bindings
NSDIDL supports OMG standard C++ and Java language bindings, as defined in the OMG binding specifications. Any differences between the
specification and the NonStop CORBA implementation are noted in the NonStop CORBA 2.6.1 Programmer's Reference.
Portable Object Adapter
The NonStop CORBA Portable Object Adapter (POA) supports the function defined in the CORBA specification. An Object Adapter is the
primary way that an object implementation accesses the services an ORB provides.
The NonStop CORBA POA:
Allows for development of portable object solutions
Provides for objects that persist over long periods of time
Allows a servant to manage multiple objects as one logical object (A servant is a user-defined object that provides an implementation of
the methods of an interface.)
Allows multiple distinct instances of a POA to exist in a server
Supports transient objects
Supports application use of static and/or dynamic skeletons
Provides an extensible method for associating policies with objects
Supports threaded objects
Application programmers upgrading from the Basic Object Adapter (BOA) to the POA can rethink design issues because they will probably need
to alter their application interfaces to make use of the POA. However, basic BOA usage can easily be mapped to basic POA usage.
Object Method Invocation
NonStop CORBA supports the Static Invocation Interface (SII).
Naming Service
The Naming Service provides for the binding of human-readable object names to CORBA objects, and the resolving of these named objects in
client requests. The NonStop CORBA Naming Service is based on the CORBA Naming Service 1.2 specification. The Naming Service database
in NonStop CORBA is implemented as a structured Enscribe file.