CORBA 2.6.1 Programmer's Guide for Java

Make decisions about server implementation.
Design or modify clients to take advantage of new features.
To create an application, you have to:
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. Sample programs are also provided for the JORB Lite application development
environment on the PC. The sample programs demonstrate some features of NonStop CORBA as shown in the following table.
The following sample programs are available on both the PC (using the JORB Lite environment) and the NSK platform.
Table 1.1. Java Sample Programs
Program
Name
Key Features
bank
Illustrates using TS/MP with the NonStop CORBA Naming Service, Location Service Daemon (LSD), and
Communication Server (Comm Server) to provide a scalable and reliable implementation of a SQL/MP backed
Bank. The sample also interoperates with the C++ version. The sample consists of:
An interface (bank.idl)
A client (Client)
A server (Server)
A client wrapper (ClientWrapper)
A server wrapper (ServerWrapper)
A feed (Feed)
calc
Demonstrates:
Two object interface definitions written in IDL
A server that implements the two interfaces defined by the interface definition
A client application that makes use of an instance of a calcFactory object and an instance of a NS_Calculator
object
Interoperability between JORB Lite and NonStop CORBA for Java
event_service
Demonstrates the use of the NonStop CORBA Event Service. The Event Service is a CORBA specified facility
which 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.
The sample demonstrates:
A "push" supplier that produces events and supplies them to the event channel at its own pace
A "push" consumer that receives events from the event channel. These events have previously been
produced by a supplier.
A "pull" supplier that produces events and supplies them to the event channel upon demand