CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

NSD_BOOTCP
$JAVA_HOME/lib/tandemvm.
zip:$JAVA_HOME/lib/tsmp.
jar:$JAVA_HOME/lib/ classes.zip
Specifies the boot
classpath needed by
Pathway scripts (for NSJ
v16)
NSD_BOOTCP
$JREHOME/lib/tandemvm.
jar:$JREHOME/lib/rt. jar
Specifies the boot
classpath needed by
Pathway scripts (for NSJ
v20)
CLASSPATH
$CLASSPATH:$NSD_ROOT/idl/
nsdidl.jar:$NSD_ROOT/idl/
jorb/jar:$NSD_ROOT/idl/
jts.jar:$NSD_ROOT/idl/ ejb.jar
Sets up the CLASSPATH
for the OMG Interface
Definition Language
(IDL)" compiler for
NonStop CORBA for
Java.
PATH
$PATH:$NSD_ROOT /bin:$NSD_ROOT/
bin/unsupported: $COMP_ROOT/usr/lib:
$JAVA_HOME/bin
Adds the NonStop
CORBA for Java bin
and lib directories to the
current path.
* The default setting might be different, because it depends on the options you selected when you ran the
NonStop CORBA installer program.
Configuration Database
The configuration information for the NonStop CORBA system is stored in the configuration database file. The
installer program creates this file during product installation. The file location is defined by environment variable
NSDOM_CFG_DBM. The file is an Enscribe file that is stored in the Guardian file space.
The configuration database is used by various NonStop CORBA programs, by the NonStop Distributed
Component Console, and by the configuration management tool (cfgmgt). Each of these programs can read
information from the database as well as alter its contents.
The data are structured as a collection of entities or records. Each of these has a unique name that always
conforms to the following syntax:
profile@attribute
An example of such a name is NS@ORB. Each entity consists of a series of keys and associated values. Both keys
and values consist of strings of characters. You must enclose white space in double quotation marks. Within a
particular entity each key must be unique.
While there are some standard entities in the configuration database, the specific entities in a particular database is
installation-dependent. Appendix A lists some standard entities and their contents. There are no constraints on
what entities can appear in the configuration database nor on what keys and values comprise an entity; however,
many of the NonStop CORBA system components and the NonStop Distributed Component Console expect
certain entities to be present. Be careful not to make changes that could adversely affect system operation.
Whenever possible, use the Console to manipulate the contents of the configuration database, because the console
helps to ensure data consistency. Configuration Management Tool (cfgmgt) describes the use of the
configuration management tool that can be used to view and alter the configuration database when necessary.
Most work is accomplished using only a few of the available commands, which are described in the following