CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

If you want a NonStop CORBA client to communicate with a NonStop CORBA for C++ or 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 application server specifies the following:
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
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 by 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
Java
To use the file-system protocol, a server program must be run named, which can be done in the script file
that initializes the PATHCOM process under which the application server runs.
To prepare a program to run named, you need to run Java from the osh shell. In the following command,
the environment variable JAVA_HOME is already set:
run -name=/G/name [ run-args ]
$JAVA_HOME/bin/oss/posix_threads/java java-server
[ java-server-args ]
This command uses the following variable arguments:
name
This is the NonStop Kernel name of the Java process.
run-args
These are additional osh run arguments.
java-server
This is the class name of the Java application server.
java-server-args
These are Java server run arguments.
If you want a NonStop CORBA for Java client to communicate with a NonStop CORBA for C++ or