CORBA 2.6.1 Administration Guide

is specified, the program will listen on a TCP socket and accept CORBA requests on it.
NonStop CORBA provides four transport protocols:
Transport
Protocol
Uses... Appropriate When...
Pathsend TS/MP
communication
mechanism
Servers are running in a TS/MP server pool.
File system NonStop File
System
Client and server reside in the same Expand network.
IIOP/SSL SSL over TCP/IP Data protection is required for the communication. The server needs to be authenticated
or the client needs to be authenticated.
IIOP (Internet
Inter-ORB
Protocol)
TCP/IP
mechanism
Client and server can communicate by means of an Internet or interoperability between
ORB vendors is desired (all CORBA-compliant ORBs support this protocol).
Client Protocols
Client protocols are those used when a program is making a CORBA request. The object reference to which the request is directed holds
information about the protocols acceptable to the server hosting the object. The client program's ORB component uses the list of protocols
available to it to determine how to reach the object. Each of these protocols is compared against those contained in the object reference. When
a match is found, an attempt is made to use that protocol. Typically, use of the protocol results in a successful request and response. If a
request using a particular protocol fails and there are additional protocols available to the client and additional protocols available in the object
reference, an attempt is made to use a different protocol. This process continues until the request is successful or there are no more transport
protocols to try. The order of precedence in attempting to match client protocols with protocols in an object reference is:
1.
Pathsend
2. File system
3. IIOP/SSL
4. IIOP
By default, the Pathsend, File system, and IIOP transport protocols are enabled for a NonStop CORBA program. The IIOP/SSL protocol is not
enabled by default. When you want to limit a client so that it uses only some of the protocols, or if you want to enable a protocol, you can do so
by explicitly disabling or enabling a protocol in the program profile. For example, to use only the IIOP protocol, specify a program profile in which
fs_client and tsmp_client are set to false.
The following table shows the client protocol keys and values that may appear in a NonStop CORBA program profile:
Client Protocol Keys and Values
Key Possible
Values
Default Value Operational Characteristics
tsmp_client
true or false
true
Pathsend protocol: Uses the TS/MP context-sensitive protocol to a
process in a server pool.
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