CORBA 2.3.3 Programmer's Guide for C++ (NonStop CORBA 2.3.3+)

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 Himalaya 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 Himalaya system
These processes run on a NonStop Himalaya 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.
Introduction to NonStop CORBA Components
You will work with several NonStop CORBA components as you design and write your applications,
including:
Bootstrap Service Daemon (BSD)
For applications that need interoperability with the bootstrap protocol in some earlier versions of
J2EE, the Bootstrap Service Daemon provides a standard interoperable protocol for resolving an
initial reference ID and for listing the supported initial reference IDs. The BSD configuration is
held in the configuration database.
Configuration database
This database is built during the installation and configuration of NonStop CORBA. It contains an
entry for the Naming Service that includes an IOR used by
ORB::resolve_initial_references. The database is used to maintain the TCP/IP
addresses for the Comm Servers and the LSD. It is also used to maintain a map table for
associations between the Comm Servers and remote client hosts. It also contains a Comm Server
load table. Finally, it is used to maintain application configurations. You modify the configuration
database directly by using the NonStop Distributed Component Console or by using the
cfgmgt tool.
Comm Servers
Comm Servers can be thought of as gateways allowing network clients to communicate with
application servers on the NonStop Himalaya system. They also act as TCP/IP network resource
concentrators, mapping all connections from a client address to the same Comm Server. Comm
Servers take advantage of TS/MP capabilities and are configured as TS/MP (Pathway) server
classes. You configure Comm Servers to use various transport protocols depending upon your
application design.
Location Service Daemon (LSD)