CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

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
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:
entities
Each entity has a name of the form profile@attribute, where profile and attribute are any strings.
When you have the list of available entities, you can use other commands to manipulate them.