Step 2: Specify Ip Addresses - Netscape MANAGEMENT SYSTEM 4.5 Installation And Setup Manual

Backlog. Type the number of connections that can be waiting to be serviced at
the end-entity HTTPS port. The default number is 15. The number you enter in
this field is passed to the operating system's
To save your changes, click Save.
5.
The CMS configuration is modified. If the changes you made require you to
restart the server, you will be prompted accordingly. In that case, restart the
server.

Step 2: Specify IP Addresses

This step is optional.
You can configure CMS instances to listen to specific IP addresses. For example,
you can install the Certificate Manager and Data Recovery Manager on a single
host, in separate instances, and then configure the instances so that the Certificate
Manager is served on one IP address and the Data Recovery Manager is served on
another address.
To clarify this further, consider the machine that hosts the Certificate Manager and
Data Recovery Manager has two Ethernet cards that respond to the IP addresses
and
197.1.137.97 197.1.137.98
to port 443 for the IP address
listen to port 443 for the IP address
To configure a CMS instance to listen to specific IP addresses:
Stop the CMS instance; see "Stopping Certificate Management System" on
1.
page 320.
Open the configuration file in a text editor; to locate the file, see "Locating the
2.
Configuration File" on page 348.
Add one or more of the following as appropriate:
3.
For remote administration port, add this line:
For agent port, add this line:
For end-entity HTTPS port, add this line:
For end-entity HTTP port, add this line:
listen()
. You can set up the Certificate Manager to listen
and the Data Recovery Manager to
197.1.137.97
.
197.1.137.98
agentGateway.https.host=
eeGateway.https.host=
eeGateway.http.host=
Configuring Port Numbers
call.
radm.https.host=
Chapter 11 Setting Up Ports 377