CORBA 2.3.7 Programmer's Guide for C++

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 CPU.
nsdom_ir file-name
Default is $NSD_ROOT/etc/nsdom.ir.
stack_size number
Default is 65536. Minimum is 16384 and maximum is 32768000. This setting dictates the size of thread
stacks.
keep_alive {true | false}
Controls whether the TCP/IP keep-alive mechanism is enabled. Default is true. If enabled, TCP will
periodically ping the other end of a connection to determine if the connection is still valid, which will detect if
the other end has gone away, even if no data is being transferred. This variable is useful when one side is
waiting for data (the next request for a server, or a reply for a client) and the other side fails.