CORBA 2.3.3 Programmer's Guide for Java

tcp_server true
tcp_process $ztc1
host_name oss2.widget.com
port_number 0
When NonStop CORBA builds an IOP::TAG_INTERNET_IOP profile, the profile's host field must be
in dot-decimal form to avoid having to export the DNS/host-file configuration to every client. Also, the
port field must have the actual port number selected by TCP if it was configured as 0. This arrangement
is accomplished by the server writing its actual TCP address to the configuration database upon
successfully performing a socket listen (the listen occurs during the CORBA::ORB::ORB_init()
method invocation). Each time a direct TCP server runs, it generates an actual_tcp_address
entity. This record shows up as <profile>@actual_tcp_address in the configuration database.
To continue with the configuration above, after running the xyz server (and it calls the
CORBA::ORB::ORB_init() method), you would be able to see this record using cfgmgt:
cfgmgt> entity xyz_service@actual_tcp_address
host_name 204.160.16.38
port_number 1342
Each time the xyz server is run, you would expect to see a new
xyz_service@actual_tcp_address entity. The host_name would not change, but since TCP is
picking xyz_service's port_number, that field should have a new value each time.
Interoperable Object References for Objects in a
Server Pool
There are two distinct types of server pool objects: stateless and stateful.
IORs for Stateless Objects in a Server Pool
A stateless request (that is, a request for an operation on a stateless object) can go to any free server
process within a server pool.
The list below explains how NonStop CORBA creates and uses object references for stateless objects. In
this scenario, the client can be local or remote with respect to the server pool. If the client is remote, a
Comm Server process obtains the link with the server pool on behalf of the client.
When the client program requests an operation on a stateless object, NonStop CORBA uses the
TS/MP protocol-specific information in the reference to establish a new TS/MP dialog between the
client and the least busy server process in the server pool.
●
NonStop CORBA sends the request from the client to the target process and gets the reply from
the target process back to the client.
●
NonStop CORBA breaks the TS/MP link between the client and the server process in the server●