CORBA 2.6.1 Administration Guide

remove the $ZNCB process.
1. If NonStop CORBA system processes are running, stop them by executing the
nsdstop script from OSS:
> nsdstop
2. Locate the Comm Server specification section in nsdstart. The following example shows the section of nsdstart that configures the
Comm Server, including two processes:
Configuring Two Comm Servers
#...
COM_SERVER1="$MY_PREFIX"NCA
COM_SERVER2="$MY_PREFIX"NCB
#...
set server maxservers 2
set server numstatic 2
set server process \$$COM_SERVER1
set server process \$$COM_SERVER2
set server AUTORESTART 10
add server CS
start server CS
#...
3. Edit the section to remove the $ZNCB server process, as follows:
Removing a Comm Server From nsdstart
#...
COM_SERVER1="$MY_PREFIX"NCA
#...
set server maxservers 1
set server numstatic 1
set server process \$$COM_SERVER1
set server AUTORESTART 10
add server CS
start server CS
#...
4. Restart the NonStop CORBA system processes by executing the nsdstart script from OSS:
> nsdstart
Managing NSots Transaction Managers in a Process Pool
To support two or more NSots transaction managers in a process pool, it is necessary to run a NSots XID Broker process. The XID Broker
brokers requests for imported transactions within the pool of NSotsTMs by routing secondary import requests back to the NSotsTM that
originally imported the transaction. If only more than one NSotsTM process is configured in a process pool, it is necessary to also configure one
and only one NSotsXID process. It is also necessary to define the environment variable NSOTS_XID_BROKER_REQUIRED for the NSotsTM
process. These steps are shown in commentary form in the
nsdstart script. They are also supported by the Console. If
NSOTS_XID_BROKER_REQUIRED is defined and NSotsXID is not available, the application should receive the exception
CORBA::TRANSIENT.
Configuring NonStop CORBA to Use Parallel Library TCP/IP
When NonStop CORBA is initially installed the default configuration is for the original TCP/IP. To configure Parallel Library TCP/IP, perform the
following steps:
1. During installation, provide a Parallel Library TCP process name to the prompt beginning:
"ENTER the TCP process name here ..."
The default TCP process name for original TCP/IP is $ZTC0. The default TCP process name for Parallel Library TCP/IP is set when
Parallel Library TCP/IP is installed. You can locate the Parallel Library TCP/IP process for your system by using the SCF command
LISTDEV TCPIPand looking for a process with program path ending in TCPSAM.
2. Before starting the subsystem, configure the BSD, LSD, ILSD, and Comm Server(s) to take advantage of Parallel Library TCP/IP.
Note:
If you want to change from original TCP/IP to Parallel Library TCP/IP after the initial installation of NonStop
CORBA, it is easier to use the Console to make the changes, due to the number of configuration database
changes that must be made.
Configuring the BSD, LSD and ILSD for Parallel Library TCP/IP
The same procedure is required to configure the BSD, LSD and ILSD. Apply this procedure to the BSD server class, LSD server class and/or
the ILSD server class.
1. Use the cfgmgt tool to add the key/value pair parallel_ip/true to the application's profile. For example:
[dbname:$system.zorbsdk.NSDCFGDB] 1>entity lsd1@ORB {parallel_ip true}