CORBA 2.6 Administration Guide

fs_client
true or false
true
File system protocol: Uses the NonStop File System operations
(for example, FILE_OPEN_, WRITEREADX, FILE_CLOSE_).
tcp_client
true or false
true
IIOP protocol: Uses socket operations on the target object's host
name and port number.
tcp_process
Valid TCP process name
$ZTC0 No default for
Parallel Library TCP/IP.
Used with the tcp_client protocol. If specified, the given
TCP process is used when making requests.
ssl_client
true or false
false
IIOP/SSL protocol, client side.
ssl_only
true or false
false
When false, an IIOP port is published in the IOR. A value of
true will force tcp_client to be false.
Server Protocols
Server protocols are those used when a NonStop CORBA program is acting as a server. Upon program initialization, the protocols specified
in the program profile inform the ORB component which transport protocols can be used by hosted objects. This information is used to set up
communications mechanisms. For example, if the IIOP protocol is specified, the server process listens on a TCP/IP socket. When objects
hosted in the server process create object references, the protocols specified in the program profile determine the protocols inserted into the
object reference.
Each server program should use a distinct program profile. The ORB component can place values in the program profile or create associated
database records. If you use the same program profile for different server programs, incorrect server behavior is likely.
When an object in a server program creates an object reference, the ORB component uses information from a number of sources. The
transport protocols specified in the program profile determine the protocols that appear in the generated object references. The portable object
adapter (POA) policies in effect when an object reference is created also influence the contents of the object reference. The effects of the
POA policies depend on the particular transport protocol. Details about these relationships are explained in:
Pathsend Protocol●
File System Protocol●
IIOP/SSL 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.
ssl_only
true or false
false
IIOP without SSL disabled.
ssl_port
Integer None
Identifies the servers listening port and enables the IIOP/SSL protocol for the
server side.
ssl_verify_peer
true or false
false
Requests and authenticates the clients certificate. Establishes trust in client.
ssl_verify_context
subject
cert
certchain
None
Subject is the Subject's DN in the certificate.
Peer certificate is inserted into the SSLIOP service context.
Peer certificate chain is inserted into the SSLIOP service context.
Protocols Common to both Clients and Servers
The following keys and values can be used for either clients or servers.
Key Value Default Operational Characteristics