CORBA 2.3.7 Programmer's Guide for Java

Obtaining Object References
NonStop CORBA obtains server IORs at three points:
Explicitly, when the application calls CORBA::Object::object_to_string(). This
action is usually done when an IOR must be "hand delivered" to a client, for example, during
initial testing of a system when the Naming Service is being avoided.
●
Implicitly, when an object is returned as an out parameter or result for an operation. An example is
found in the Naming Service resolve() operation.
●
Implicitly, when an object is passed as an in parameter to an operation. An example is found in the
Bank sample program Server.java when it calls the Naming Service rebind() operation.
●
Content of Object References
The content of a NonStop CORBA IOR is determined by the servant's POA policies, the server protocols
enabled in the configuration database, and the actual deployment of the server processes.
NonStop CORBA IORs adhere to the CORBA IOR rules except that NonStop CORBA does not
recognize the IOP::TAG_MULTIPLE_COMPONENTS.
NonStop CORBA recognizes three profile tags:
NSDOM_GCF_IOP::Profile_Tag (0)●
NSDOM_GFS_IOP::Profile_Tag (0)●
IOP::TAG_INTERNET_IOP (0)●
If more than one protocol is enabled for a server, multiple profiles will exist in the IOR. Multiple profiles
are ordered based on desirability from the server's perspective, in the order shown above.
Addresses
Servers may be configured as direct or indirect TCP servers:
Direct TCP servers are configured with tcp_server true, and the host_name and
port_number are specified. These servers communicate directly with TCP sockets.
●
Indirect TCP servers are configured with tcp_server true and use_comm_server
true. They are accessed by the NSK message system. Access via TCP will be bridged through a
Comm Server. This configuration is useful with stateless servants, and for TCP connection
concentration.
●