CORBA 2.6 Programmer's Guide for Java

nm
The nm command writes the name list of each specified object file to the standard output file. The
nm command displays symbolic information appearing in an object file, executable file, or
object-file library. nm can be used to find symbols that show up in unresolved external error
messages.
vi
This utility is the OSS editor used to create and update OSS files.
jdb
You must use the jdb tool to debug your NonStop CORBA application programs. The
implementation of jdb and extensions to the Sun Microsystems tool are described in the NonStop
Server for Java (NSJ) Tools Reference Pages.
Working in the NonStop CORBA Administrative
Environment
Applications that you write use services provided by the NonStop CORBA administrative environment.
This section gives a brief overview of the administrative environment. For more information on the
NonStop CORBA administrative environment, see the NonStop CORBA 2.6 Administration Guide.
Components of the NonStop CORBA Environment
The NonStop CORBA administrative environment has the following components:
The NonStop Distributed Component Console is a GUI-based interface used to manage the
administrative environment.
Security domains are the processes that are managed under a single user ID.
Business domains are collections of related business application processes, configuration data,
and NonStop services for CORBA. You identify business domains by using the Console.
The NSDAdminServer process provides services that are independent of any security domain,
such as system configuration information.
The NSDEnvironServer process provides services for a specific security domain.
The $NSD_ROOT/etc/env.sh file contains environment settings.
The Configuration database (nsdcfgdb) contains entities for ORB components and application
profiles.
The adminDB stores the operational data used by the NSDAdminServer and NSDEnvironServer
processes. The location of the database is given by the environment variable
NSDOM_ADMIN_DB.