CORBA 2.6.1 Administration Guide

Chapter 2. System Management
Chapter 2. System Management
NSDAdminServer and NSDEnvironServer
Purpose of NSDAdminServer and NSDEnvironServer
Starting and Stopping NSDAdminServer
Starting NSDEnvironServer
Configuration Data Used by NSDAdminServer and NSDEnvironServer
What You Need to Know
NSDAdminServer and NSDEnvironServer
Purpose of NSDAdminServer and NSDEnvironServer
Starting and Stopping NSDAdminServer
Starting NSDEnvironServer
Configuration Data Used by NSDAdminServer and NSDEnvironServer
Purpose of NSDAdminServer and NSDEnvironServer
The NonStop Distributed Component Console (called the Console) requires support services from the systems it manages. The processes that
provide these support services are the NSDAdminServer and the NSDEnvironServer.
For any given NonStop Kernel system, there is a single NSDAdminServer process with which the Console communicates. There are one or
more NSDEnvironServer processes, depending on the number of security domains that have been configured.
The NSDAdminServer process is the initial point of contact for a Console that needs to manage components on the system. This process
provides information and services that are independent of any particular security domain, for example:
Information about the available security domains
Logon authentication for a security domain
System configuration information such as the available CPUs, disks, and TCP processes
Management of security domains
The NSDEnvironServer process provides services for a particular security domain. Generally, the NSDEnvironServer processes are created by
the NSDAdminServer on demand. The NSDEnvironServer process provides information and services specific to a security domain, for example:
Starting and stopping processes
Providing status-update information about processes
Retrieving and storing configuration information
Management of business domains
Starting and Stopping NSDAdminServer
The NonStop CORBA installer starts the NSDAdminServer process so that the Console can use it. The installer runs runadmin, which starts an
admin server that is not a TS/MP server class. If the NSDAdminServer process is stopped, you must restart it. You can start the
NSDAdminServer either as a stand-alone OSS process or as an OSS process running under PATHMON control.
Starting NSDAdminServer as a Stand-Alone Process
Stopping the Stand-Alone Process
Starting NSDAdminServer as a PATHMON Process
Stopping the PATHMON Process
Starting NSDAdminServer as a Stand-Alone Process
To run the NSDAdminServer as a stand-alone OSS process:
1. Set the required environment variables (see The env.sh Source File).
2. At the OSS command prompt, give the command
runadmin, with or without one or more of these options: