CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

tcp_process
The TCP process associated with host_name, can be omitted if using the default TCP process $ZTC0.
Client and Server Protocol Specifications
To make and receive object requests, NonStop CORBA programs need transport-protocol information.
This information is used by the ORB component of a client or server program.
An entity of the form name@ORB defines a NonStop CORBA program profile with the given name.
This profile is used with the CORBA program command-line argument -ORBprofile name. The
ORB uses the information in the profile to govern the communication characteristics of the NonStop
CORBA program. This information is used in the following situations:
When the program is acting as a client in making CORBA requests, the protocol information
specifies the allowable transport protocols.
●
When the program is acting as a server, the protocol information determines the transport
protocols that appear in generated object references. The protocol information also specifies the
protocols to which the server will respond. For example, if the tcp_server protocol is
specified, the program will listen on a TCP socket and accept CORBA requests on it.
●
NonStop CORBA provides three 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 sever reside in the same Expand
network
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: