CORBA 2.3.3 Programmer's Guide for C++

NSDOM_GCF_IOP::Profile_Tag Addresses
If a server is configured to enable GIOP over TS/MP (tsmp_server true), the profile address will
contain pathmon-process-name and server-class.
NSDOM_GFS_IOP::Profile_Tag Addresses
If a server is configured to enable GIOP over the Guardian file system (fs_server true), the
address field will contain a Guardian file system address. If the servant's POA has the PERSISTENT
lifespan policy, the profile address will be set to pname.subdevice. If the servant's POA has the
TRANSIENT lifespan policy, the profile address will be set to
pname:sequence_number.#subdevice. The sequence number allows NS CORBA to detect if a
server process has been restarted. Transient servants are not valid across process restarts.
IOP::TAG_INTERNET_IOP Addresses
If a server is configured to enable IIOP (tcp_server true), this profile will be added to IORs
generated for objects within that server. NonStop CORBA supports the IIOP profile defined by the OMG
with the exception that NonStop CORBA does not support IIOP::ProfileBody_1_1. Servers can
be configured either as direct or as indirect TCP servers. The content of the host and port fields are of
interest here.
The address field contains an TCP/IP address in dot-decimal form and a port_number. Which TCP/IP
address and port is dependent on server configuration and servant POA lifespan policy:
If the server is configured as an indirect TCP server, or the servant's POA has a PERSISTENT
lifespan policy, these fields will contain the actual host name and port number of the LSD (see
Configured Versus Actual TCP Addresses). The result is that attempts to connect to such servers
will first reach the LSD. The LSD will forward indirect-TCP-server requests to a Comm Server,
and direct-TCP-server requests to the actual TCP address of the server.
●
If the server is configured as a direct TCP server and the servants POA has a TRANSIENT
lifespan policy, the host and port fields will contain the server's actual TCP host name and port
number (see Configured Versus Actual TCP Addresses). Clients' attempts to contact such a server
will connect directly to the server, as opposed to contacting the LSD first.
●
Configured Versus Actual TCP/IP Addresses
When configuring direct TCP servers (that is, tcp_server true, but not use_comm_server), the
host_name field can be entered in name-form rather than the dot-decimal form. Further, since a host
name can map to more than one TCP process, the host name might be ambiguous. This ambiguity is
resolved by using the tcp_process entity key in the profile.
Also, the port_number entity key in the profile can be set to 0, allowing TCP/IP to pick a port as
shown in this configuration database record:
cfgmgt> entity xyz_service@ORB