CORBA 2.6 Administration Guide

modify the entity. Each line contains a single key and its associated value. A closing brace terminates data entry.
When an input line contains a key that is the same as an existing key, the new value replaces the current value.
When an input line contains a new key, the new key and value are made part of the entity. For example, to change
the value of fs_server for the entity displayed in the previous example, use this entity command:
entity NS@ORB {
fs_server false }
To remove a key and value from an entity, use the entitydeletekey command. For example, to delete the
key use_comm_server and its value from the NS@ORB entity, use this command:
entitydeletekey NS@ORB use_comm_server
Adding an Entity
To add an entity to the configuration database, use the first technique described in Changing an Entity. When you
use a new entity name, the subsequent keys and values define that entity. For example, the following entity
command would create a new entity named tcp_client@ORB:
entity tcp_client@ORB {
tsmp_client false
fs_client false }
Deleting an Entity
To delete an entity (along with its keys and values) from the configuration database, use the entitydelete
command. For example, to delete an entity named app_profile@ORB, use this command:
entitydelete app_profile@ORB
Exiting cfgmgt
When you are finished using cfgmgt, return to the OSS command prompt by entering one of the following
commands:
bye●
exit●
quit●
Managing Configuration Change When IIOP/SSL is Configured
If you change the LSD or the Naming Service configuration to use IIOP/SSL, you will need to reconfigure the
database to keep IORs consistent. Also, if you change the LSD port number, you need to reconfigure the database.
To reconfigure the database, follow this procedure:
Stop the NonStop CORBA system using nsdstop:
nsdstop
1.
Back up the naming database ($MY_SUBVOL.namingdb) and the configuration database
($MY_SUBVOL.nsdcfgdb) before you reconfigure. You can then restore these files should you wish to
return to the previous configuration.
2.
Dump the configuration database using the dumpdb command:3.