CORBA 2.6 Administration Guide

RC4-MD5
EXP1024-DHE-DSS-RC4-SHA
EXP1024-RC4-SHA
EXP1024-DHE-DSS-DES-CBC-SHA
EXP1024-DES-CBC-SHA
EXP1024-RC2-CBC-MD5
EXP1024-RC4-MD5
ADH-RC4-MD5
EDH-RSA-DES-CBC-SHA
EDH-DSS-DES-CBC-SHA
DES-CBC-SHA
ADH-DES-CBC-SHA
EXP-EDH-RSA-DES-CBC-SHA
EXP-EDH-DSS-DES-CBC-SHA
EXP-DES-CBC-SHA
EXP-RC2-CBC-MD5
EXP-RC4-MD5
EXP-ADH-DES-CBC-SHA
EXP-ADH-RC4-MD5
NULL-SHA
NULL-MD5
NULL-NULL
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).●
The server is running in a TS/MP server pool and your object is associated with a POA that has a stateful policy.●
When your server produces object references that specify the file-system protocol, the process name is included as part of the object
references. Later, clients using the object reference make requests and those requests are directed to the identically named process. For this
reason, the server process must run as a named process.
The POA lifespan policy also affects file-system object references:
Lifespan Policy Effect
Transient
Only the process instance that produced the object reference can subsequently service it. Thus if your server restarts, the
transient object reference is no longer valid even though the restarted process has the same name as the original process.
Persistent A restarted process that has the same name as the original process can service the request.