CORBA 2.6.1 Administration Guide
Changing the Process Priority
1. Locate the section of the script that defines the server you want to change.
2. Change the process priority number in the line that looks like this:
set server pri 150
Changing the CPU in Which a Server Runs
1. Locate the section of the script that defines the server you want to change.
2. Add a line similar to the following (which specifies that the servers should run in CPUs 1 and 2):
set server cpus (1,2)
Enabling Trace Output for a Server
1. Locate the section in the script for the server you want to change.
2. Find the lines that enable tracing. These lines are initially commented out (the left bracket comment character "[" appears in front of each
line).
3. Remove the comment character from each trace line.
4. After you restart the server, trace output appears in the log file.
For log file information, see
Appendix D.
Adding a Comm Server Process
Assume that the currently running NonStop CORBA system includes a Comm Server named $ZNCA and that you want to add a second one
named
$ZNCB.
Note:
The examples in this section assume that you have set
MY_PREFIX in the env.sh script equal to the value Z.
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 the nsdstart script. The following example shows the section of nsdstart that
configures the Comm Server process:
Configuring a Comm Server
#...
COM_SERVER1="$MY_PREFIX"NCA
COM_SERVER2="$MY_PREFIX"NCB
#...
set server maxservers 1
set server numstatic 1
set server process \$$COM_SERVER1
set server AUTORESTART 10
add server CS
start server CS
#...
3. Edit this section to add another server. Note that new Comm Servers names must have the last letter incremented, giving Comm
Servers $ZNCA through $ZNCZ. There is a limit of 26 Comm Servers.
Adding a Comm Server to the nsdstart Script
#...
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
#...
4. Be sure you add the new Comm Server profile for the process $ZNCB to the configuration database. See Configuration and Adding an
Entity for details.
5. Restart NonStop CORBA system processes by executing the nsdstart script from OSS:
> nsdstart
Removing a Comm Server Process
Assume that the current NonStop CORBA system is configured to include two Comm Servers, named
$ZNCA
and
$ZNCB
, and you want to