CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

The Distributed Object Environment
NonStop CORBA Configuration Management
NonStop CORBA Performance Tuning
NonStop CORBA Troubleshooting
What You Need to Know
Configuration
This section assumes that you have successfully completed installing your NonStop CORBA system as described
in Installing NonStop CORBA.
The installation process gives you a fully configured system. Later you may wish to make modifications to your
configuration. The information in this section shows you how to perform these configuration tasks. Most of the
commands described in this section are used in the Open System Services (OSS) environment. You should be
familiar with OSS before attempting any of the configuration tasks described in this section. To modify the scripts
described here you need to use a text editor such as the vi editor. For more information about using OSS
commands and the vi editor see the Open System Services User's Guide.
You should also be familiar with the Guardian environment and file system before starting to configure and
manage your system. See the Guardian User's Guide for information about working in the Guardian environment.
Setting Environment Variable (env.sh file)
Each NonStop CORBA setup uses a unique set of environment variables. The file env.sh, found in the etc
product subdirectory, sets up the NonStop CORBA environment variables that are used by the other NonStop
CORBA scripts and by some programs.
After you install the NonStop CORBA product, the settings in env.sh are correct for your installation. When
using the various NonStop CORBA programs and shell scripts, you must ensure that the correct environment
variables are in effect. To do so, issue the following OSS shell command from your NonStop CORBA base
directory:
. etc/env.sh
This command reads env.sh file and sets the environment variables in your current OSS shell session.
Alternatively, you can put the command in the OSS .profile script. This script is executed each time you
enter OSS. For example, assuming you have installed the NonStop CORBA in the directory
/usr/tandem/nsdoms, you could put the following line in your Profile file:
. /usr/tandem/nsdoms/etc/env.sh
Customizing the env.sh file
You might want to customize the env.sh file to reflect a special NonStop CORBA setup. For example, if you
wanted to move the NonStop CORBA files from one Guardian subvolume to another, you need to make a change
to the NSD_DIR and NSD_SUBVOL environment variables in env.sh. Use a text editor to modify env.sh.
After editing the file, you must execute the script (as described in Setting Environment Variables) in order for the
new settings to take effect.
The following table gives a brief description of each environment variable set in the env.sh script. The table