CORBA 2.6.1 Programmer's Guide for Java

CORBA application by using the flag. The flag
improves handling of marshalled typecode indirections (which NonStop CORBA encodes by default).
If no -ORBprofile argument is passed in the run command to a NonStop CORBA application, the default@ORB entity is used. This entity acts as
a subsystem configuration domain for any settings not found in an application's
profile@ORB entity.
If you don't set them in the application's profile, the
default@ORB entity sets the log filename, trace filename, url_path name, and interface
repository filename. See the NonStop CORBA 2.6.1 Administration Guide for a complete listing of the
default@ORB entity settings.
profile@ORB Server Transport Protocols
Several of the server transport protocol settings are interrelated, and you must use caution when setting them. For a discussion of how the
choice of server transport protocols affects application design, see the
Writing Scalable Applications . The rules are:
tcp_server {true | false}
Default is false. If set to true, you must either set use_comm_server true (called indirect TCP server) or set both host_name and
port_number.
use_comm_server {true | false}
Default is false. If set to true, then tcp_server must also be set to true. When tcp_server and use_comm_server are set to true, you can
set either
tsmp_server to true, or fs_server to true, or both.
host_name {DNS-name | IP-address}
You must specify a name, TCP/IP, TCP/IPv6 address if tcp_server is true and use_comm_server is false. DNS-name represents the name
form of the address, and
IP-address represents the dot-separated IPv4 address like 172.31.41.151 or colon-separated IPv6 address
like
fe80::a00:8eff:fe06:d093.
port_number number
You must specify a port number when tcp_server is true and use_comm_server is set to false.
tcp_process tcp-process-name
If use_comm_server is set to false, you must supply a host_name. If the host_name is not associated with the default TCP process ($ZTC0),
you must specify the associated
tcp_process name.
tsmp_server {true | false}
Default is false. If set to true, you must also set pathmon and server_class. This configuration is referred to as GIOP over TS/MP.
pathmon pathmon-process-name
If tsmp_server is true, you must specify a name for pathmon.
server_class serverclass-name
If tsmp_server is true, you must specify a name for server_class.
fs_server {true | false}
Default is false. This configuration is referred to as GIOP over the Guardian file system.
profile
@ORB Client Transport Protocols
One or more of the client transport protocols must be enabled to act as a CORBA client.
tsmp_client {true | false}
Default is true.
fs_client {true | false}
Default is true.
tcp_client {true | false}
Default is true.
profile
@ORB Miscellaneous Settings
These settings are all optional. They apply only to the application using the profile. You can set the defaults for these values by using the
Console, or by editing the
default@ORB entity using the cfgmgt tool.
log_file {EMS-process-name | STDCOLL | STDOUT | STDERR | oss-file-name}
Default is STDCOLL.
trace_file {file-name | STDOUT | STDERR}
Default is STDOUT.
max_threads number
The maximum number of servant threads available in a process. Default is 4097. The effective maximum number of threads in a server
depends on the size of each thread's stack and the number of NSK threads available in a Processor.
nsdom_ir file-name
Default is $NSD_ROOT/etc/nsdom.ir.
giop_version version
Allows you to select the ORB giop version for both the client and server directions. The key values are 1.0, 1.1, and 1.2. The default is
version 1.2. The key sets the ORB’s GIOP version. IORs generated by this ORB will have this version and GIOP requests will have a
version that is the minimum of this version and the remote IOR's version.
allow_wchar_wstring_in_1_0 {true | false}
Controls whether wchar and wstring are enabled over GIOP 1.0. The key is
allow_wchar_wstring_in_1_0
, and the key value is true or