CORBA 2.3.7 Programmer's Guide for C++

General environment configuration such as names and directories●
Bootstrap Service Daemon (BSD)●
Comm Servers●
Event Service●
Interoperable Location Service Daemon (ILSD)●
Interface Repository (IRD)●
Location Service Daemon (LSD)●
Naming Service●
Object Transaction Service (OTS)●
OTS Transaction ID Broker (XID)●
When you use the Console to make configuration changes, it stores the changes in the configuration database. The
Console software also checks entries to make sure they fall between allowed ranges. If you change one field in the
Console screens that has dependencies on other fields, the Console will either automatically make changes to the
other fields or leave them blank, prompting you to fill in a value.
You can also change the configuration database directly from the OSS environment command line, by using the
Configuration Management Tool (cfgmgt). For information on how to use cfgmgt see the NonStop CORBA 2.3.7
Administration Guide. When you alter the configuration database without using the Console, you need to understand
the dependencies between the database entities and make your changes carefully to keep your configuration working
correctly.
Note
You can set many configuration database entities by using the NonStop Distributed Component Console. These
database settings apply to all applications, unless overridden by an application-specific configuration entity (that is,
profile@ORB). Application-specific entities are managed by using the cfgmgt tool. See Application Profiles:
Configuring and Managing an Application for more information.
Note
The Console is also useful when you troubleshoot your application. In addition to checking configuration
information, you can use the Console to aid in tracing of NonStop CORBA processes (but not application
processes). You can also use it to view and modify the Naming Service. See How to Enable and Disable Tracing and
Viewing the Naming Service for more information.
Caution
Be very careful to keep changes made through the Console and changes made to the
$NSD_ROOT/bin/nsdstart script or $NSD_ROOT/etc/env.sh consistent with your intentions. If you have
used the Console to change trace settings, those changes will not be reflected in scripts.