CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

of the POA policies depend on the particular transport protocol. Details about these relationships are
explained in:
Pathsend Protocol●
File System Protocol●
IIOP Protocol●
The following table shows the server protocol keys and values that can appear in a NonStop CORBA
program profile.
Server Protocol Keys and Values
Key Possible Values Default Value Operational Characteristics
tsmp_server
true or false
false
Pathsend protocol; Uses the TS/MP context-sensitive
protocol.
Fs_server
true or false
false
File system protocol: Uses the NonStop File System
operations (for example, FILE_OPEN_,
WRITEREADX, FILE_CLOSE_).
tcp_server
true or false
false
IIOP protocol: Uses socket operations on the target
object's host name and port number.
The following subsections explain the use of the protocols in the preceding table.
Pathsend Protocol
Enable the Pathsend protocol when the object is hosted by a server running in a server pool and you want
to use the TS/MP transport mechanism. The Pathsend protocol is appropriate when your object is
associated with a POA that has a stateless policy. By using the stateless policy and the Pathsend protocol,
any process in the server pool can handle a request. To use the protocol you must specify the server's
PATHMON process name and server class name in the program profile. The following table shows the
keys and values that are associated with the Pathsend protocol (tsmp_server):
Pathsend Protocol Keys and Values
Key Possible Values Default Value
pathmon
Valid process name None
server_class
Valid server class name None
File-System Protocol
Enable the file-system protocol when you want the NonStop Kernel file system to be used as the
transport mechanism for requests and responses. The file-system protocol is appropriate when:
The client and server reside in the same Expand network.●
The server is running as a stand-alone OSS process (that is, not as part of a TS/MP server pool).●