CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

NonStop CORBA for Java application server through the file-system protocol, you must specify the
following setting in the client profile:
fs_client true
You can add this setting to the client profile using the Configuration Management Tool
Further, suppose the profile of a NonStop CORBA for Java application server specifies the following
settings:
fs_server true
tcp_server true
use_comm_server true
In this case, a remote client can use TCP/IP over IIOP to communicate with the NonStop CORBA for
Java application server. Here, the client will communicate with the Comm Server over TCP/IP, and the
Comm Server will relay the request to the application server using the file-system protocol.
In addition, if a NonStop CORBA for C++ or NonStop CORBA for Java client makes a request of the
same server, the client can use TCP/IP over IIOP if the profile of the client specifies following setting:
tcp_client true
TS/MP Protocol
A NonStop CORBA application server may enable communications with a NonStop CORBA for C++ or
NonStop CORBA for Java client over the TS/MP protocol by adding the following profile to the
application server:
temp_server true
pathmon <pathmon>
server_class <server_class>
You can add this profile by using the Configuration Management Tool, or you can configure the server
application with this protocol when you initialize the server's PATHMON process.
Optionally, the profile of the NonStop CORBA application server may also contain:
tcp_server true
use_comm_server true
When you add these two profiles, any client that complies with NonStop CORBA can communicate with
the NonStop CORBA application server. In this case, the Comm Server contained in the NonStop
CORBA system uses TCP/IP to communicate with the remote client, and the TS/MP protocol is used for
the communications between the Comm Server and the application server.
You must configure an application server as a TS/MP server before it can communicate through the
TS/MP protocol. This configuration is most easily done by using a script to initialize the application
server as a PATHCOM process. The NonStop CORBA product provides several examples that contain
such scripts.