CORBA 2.6 Administration Guide

-c file-name
specifies a file containing configurations to manage.
-d domain-name
specifies the name of the domain managed by the server. A corresponding profile ES_domain must
exist in the administration configuration database. By default the logon name is used as the domain
name.
-n
directs the server not to scan for configurations to manage.
-t
causes the NSDAdminServer to generate additional output. This output is typically used for
troubleshooting.
An NSDEnvironServer process starts running with a system-assigned process name.
Configuration Data Used by NSDAdminServer and
NSDEnvironServer
NSDAdminServer and NSDEnvironServer use an administration configuration database to store
operational data. The location of this database is given by the environment variable NSDOM_ADMIN_DB.
This variable is defined by the installer and appears in the env.sh script (see The env.sh Source File).
Generally you do not need to change the contents of the administration configuration database, because
the servers manage the data automatically. If necessary, you can use the cfgmgt tool to view the
contents of the administration configuration database (see Appendix B, cfgmgt Command Reference).
What You Need to Know
To manage the NonStop CORBA runtime environment, you should be familiar with the following topics:
Procedures and considerations for managing TS/MP subsystems●
Procedures and considerations for managing NonStop TCP/IP, Parallel TCP/IP, LAN, QIO, and
X25AM
●
Syntax and use of the following tools and utilities:
NonStop Distributed Component Console❍
PATHCOM interface❍
Subsystem Control Facility (SCF)❍
Configuration Management Tool (cfgmgt)❍
NonStop CORBA error log facility❍
●