DCE Installation, Configuration, and Management Guide

HP NonStop DCE Installation, Configuration, and Management Guide—429552-005
C-1
C
Noninteractive Use of dce_config
You can use dce_config to configure a DCE cell without having to respond to
queries. To do so, specify an environment file using the -e flag and a command file
using the -c flag. If NonStop DCE will be installed or configured several times, it is
helpful to create both these files.
The environment file sets values for NonStop DCE variables that specify responses to
user prompts. The command file is a shell script that can be used to control installation
and configuration processing.
You can create an environment file and a command file for each configuration of a
NonStop DCE virtual host. For example, one pair of files could be used to configure a
NonStop node containing a single virtual host as a DCE client with the NonStop DCE
product. Another pair of files could be used to configure a NonStop node containing a
single virtual host as a server running the security, CDS, and DTS servers.
NonStop DCE provides sample files within each set of virtual host files that can be
used as templates to create your own environment and command files. You must
modify the values set for the variables to suit the environment in which you intend to
install and configure NonStop DCE.
These sample files can be used to install NonStop DCE after the files in the dceconf
archive have been extracted using the pax command. The files installed from the
dceconf archive include the dce_config script utility and a pair of sample files in
/opt/dcelocal.hostname/usr/examples/dce_config.
The sample environment file, dce_config_all.env, in Example C-1 on page C-2,
specifies the name of the cell to be configured, the name of the node on which the
security and CDS servers are to be configured, and the directory name of the CDS
database. This sample file is for a TNS virtual host installation. The corresponding
TNS/R and TNS/E files do not contain the UPDATE_DEFAULT_LIBDCESO entry.
The command file can be used to specify the components that you want to install or
configure. The sample command file, dce_config_all.cmd, in Example C-2 on
page C-5, specifies that the files for all the NonStop DCE components, except those for
the replica security server, must be configured to run the security, CDS, and DTS
servers and the DTS null provider.
After your virtual-host-specific environment and command files have been created, you
can configure NonStop DCE using the command:
dce_config -c dce_config_all.cmd -e dce_config_all.env
To stop running or to unconfigure NonStop DCE on a node, you must use the
dce_config program interactively, selecting appropriate options.