CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

rather than one line per bank teller). This factor makes it attractive to design classes to be stateless to
maximize throughput.
However, in some cases, it would be inconvenient or costly for an object to be stateless. For example, if
an object returns the results of a large SQL query to a client using a cursor, the client must make multiple
method invocations on the server. If the object is stateless, subsequent method invocations could reach
different server processes, each of which would have to repeat the original query.
Stateless and stateful server pools are managed by TS/MP, which provides for scalability and load
balancing by allowing multiple processes to work in parallel to perform the same task. TS/MP also
provides for availability: its monitor process, called PATHMON, automatically restarts a process that
fails. Because TS/MP provides all process management for the NonStop CORBA system, you use
TS/MP interfaces for either the line-oriented PATHCOM utility or the corresponding programmatic
interface (based on the SPI) to configure and manage the NonStop CORBA system processes. The same
holds true for any NonStop CORBA application process that you configure as TS/MP processes.
Application Server Protocols
NonStop CORBA supports scalability in its application servers by supporting these protocols:
File-system protocol●
TS/MP protocol●
File-System Protocol
A NonStop CORBA application server may enable communications with a NonStop CORBA client over
the NonStop Kernel file-system protocol by adding the following setting to the application server's
configuration profile:
fs_server true
Optionally, of the NonStop CORBA application server profile may also contain the following settings:
tcp_server true
use_comm_server true
When you add these two settings to the application server profile, any client that complies with NonStop
CORBA 2.3 can communicate with the NonStop CORBA application server. In this case, the Comm
Server contained in the NonStop CORBA system uses TCP/IP to communicate with the remote client,
and the file-system protocol is used for the communications between the Comm Server and the
application server.
To use the file-system protocol, a server program must be run named, which can be done in the script file
that initializes the PATHCOM process under which the application server runs. The following
subsections explain how to do this in C++ and in Java.
C++