CORBA 2.6.1 Administration Guide
MY_COLLECTOR
'$0' Specifies the EMS collector process used by the NonStop CORBA
processes. The name is defined in NonStop Kernel format. Modify this line if
you want to use a different collector other than the system default of $0.
COMP_ROOT
Specifies the root location where your tools, such as c89, are located. Modify
this line if the tools you want to use are in a location other than the system
default.
JAVA_HOME /usr/tandem/java
Sets path for NSJ. Modify this line if your installation of NSJ is in a different
location than this default.
JREHOME $JAVA_HOME/jre
Specifies Java Runtime Environment home (for NSJ v3.1)
NSD_BOOTCP $JREHOME/lib/tandemvm.jar:
$JREHOME/lib/rt.jar
Specifies the boot classpath needed by TS/MP scripts (for NSJ v3.1)
CLASSPATH CLASSPATH=.:$NSD_ROOT/lib/jorb.jar:
$NSD_ROOT/lib/jts.jar
Sets up the CLASSPATH for the Java ORB.
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 depend upon the installation.
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 subsections. For a complete list of the available commands, see Appendix B.
Configuration Management Tool (cfgmgt)
Starting cfgmgt
Displaying All Entities
Displaying a Particular Entity
Changing an Entity
Adding an Entity
Deleting an Entity
Exiting cfgmgt
Starting cfgmgt
Start cfgmgt from the OSS command prompt by using this command:
cfgmgt [-r]
cfgmgt is command-based. The command prompt identifies the current configuration database. The -r option opens the database for read only.
If you have difficulty starting
cfgmgt, verify that your environment variable settings are correct. In particular:
The environment variable PATH must be set to refer to the bin directory of your product installation.
The environment variable NSDOM_CFG_DBM must be set to refer to the configuration database you wish to manipulate.
Displaying All Entities
To display all the entities in the configuration database, use this command: