CORBA 2.6.1 Programmer's Guide for C++

Make decisions about server implementation.
Design or modify clients to take advantage of new features.
To create an application, you:
Define new object classes and create new class libraries and frameworks, or modify existing ones to suit your application.
Create the client programs.
Create the server programs.
More specifically, NonStop CORBA application processes that you might design are:
Clients running on a NonStop system
These processes reside on the same NonStop system (or Expand network) as the NonStop CORBA Object Request Broker (ORB)
and act as CORBA clients.
Clients running elsewhere as network or remote clients
These processes reside on some other system (not the same NonStop system or Expand network as the NonStop CORBA ORB). The
processes act as CORBA clients. Such network clients send IIOP requests for the services of an application through the NonStop
CORBA communication services.
Network clients often use a different vendor's ORB. The IIOP protocol allows the different ORBs to communicate.
Servers running on a NonStop system
These processes run on a NonStop system and act as CORBA servers. Server processes act as host processes for CORBA application
objects. The server process can be implemented as server pools (TS/MP server classes) to provide scalability, fault tolerance, or both.
Sample Programs
NonStop CORBA includes sample programs for the NSK server. The sample programs demonstrate some features of NonStop CORBA as
shown in the following table.
Table 1.1. NSK C++ Sample Programs
Program
Name
Key Features
bank
Illustrates the concept of legacy wrapping. You should be familiar with the basic concepts presented in this
advanced topic, for example, see the
stock sample program.
eventservice
Demonstrates the use of the NonStop CORBA Event Service. The Event Service decouples communication between
objects. A supplier object produces events. A consumer object processes that event data. The Event Channel is an
intermediary which permits suppliers and consumers to be decoupled.
INS
Illustrates some of the basic concepts of Interoperable Naming Service (INS) programming with the NonStop
CORBA C++ ORB.
ots_bank
Contains a simple client, a transaction-aware client, and a transaction-aware server pool. The simple client is a copy
of the
.../samples/bank client. The transaction-aware client and server were taken from .../samples/bank and
converted to use OTS.
portable-
interceptor
Demonstrates basic aspects of request-type portable interceptors.
stack
Illustrates some of the basic concepts of CORBA programming using NonStop CORBA. The stack sample shows
you:
An object interface definition written in IDL
A server that implements the interface defined by the interface definition
A client application which makes use of an instance of a stack object
The stack sample may be used to verify installation of NonStop CORBA.
stack_obv
Illustrates some of the basic concepts of Object-By-Value and describes a simple abstract interface. The stack_obv
sample creates:
An abstract interface
A valuetype that supports the interface
An interface derived from the abstract interface
stock
Illustrates some of the basic concepts of CORBA programming using NonStop CORBA. The stock sample shows
you: