CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

Client/Server Process
A NonStop Himalaya CORBA server is any process that resides on the same NonStop Himalaya system or Expand network.
An object contained by a NonStop Himalaya CORBA server can act as a client, a server, or both. CORBA objects execute
from within a server process. Two types of CORBA servers are available on the NonStop Himalaya system, stand-alone
CORBA servers or CORBA servers within the TS/MP environment. A stand-alone CORBA server process does not have any
load balancing or automatic scale applied to it during execution. In contrast, a CORBA server running within the TS/MP
environment allows the CORBA server to be contained within a server pool. In a server pool objects may be stateless and/or
stateful. These CORBA servers are automatically fault-tolerant (as defined by the TS/MP application script). The objects
within these CORBA servers may also balance loads. Note that stateless objects are automatically load balanced upon each
method request. Stateful objects are load balanced upon each instantiation and then each method request is directed to the
same server-pool process for execution.
NonStop CORBA Remote Services
The NonStop CORBA remote services are services that enable high-volume, high-performance access from other systems.
Figure 16 shows the architecture of the remote services.
Figure 1.6. NonStop CORBA Remote Services