HP NonStop SSL, Reference Manual

Page: 31 / 127

HP NonStop SSL Reference Manual Configuration
•
31
Configuration
Configuration Overview
HP NonStop SSL processes can be flexibly configured by a set of configuration parameters which can be specified by
the following means:
•
A configuration file
•
PARAM commands
•
startup command line parameters
•
SSLCOM commands
The different options to specify a configuration for HP NonStop SSL allow system administrators to easily manage
installations with multiple HP NonStop SSL processes running on multiple TCP/IP processes and ports as well as in
different modes. For example, multiple HP NonStop SSL secure proxy processes with a an identical SSL configuration
can share the same configuration file, while process-unique parameters such as proxy port, target host and port can be
specified on the command line.
On startup, HP NonStop SSL parses the given configuration parameters sources. A single parameter may be specified in
multiple sources, e.g. in the configuration file and on the startup command line. In this case, HP NonStop SSL will
process parameters with the following precedence (highest to lowest):
1. PARAM parameter
2. Configuration file parameter
3. Startup line parameter
This means that a parameter given in the configuration file will override the value given for the same parameter on the
startup line. Likewise, a parameter value given as PARAM command will override any value specified in the
configuration file.
All parameters can be specified in any of the configuration parameter sources, with the following exceptions:
•
The run mode of a HP NonStop SSL process is specified explicitly on the command line as first startup line
parameter. This parameter defines if HP NonStop SSL acts as a secure Telnet server proxy, a secure FTP server
proxy, or in any other supported mode of operation (see "
Starting an HP NonStop SSL Process " for a complete
list of run modes).
•
The configuration file to be used as a parameter source can only be specified as a PARAM or startup line
parameter, as it is meaningless in a configuration file itself.
Regardless which way they are specified, parameter names are case insensitive.
Additionally, a subset of configuration parameters can be changed at run time using SSLCOM commands (see chapter
"
SSLCOM Command Interface " for details).