Tokens; Installing A Certificate Manager; Installing A Certificate Manager As A Root Ca - Netscape MANAGEMENT SYSTEM 6.1 - ADMINISTRATOR Administrator's Manual

specifying this when running the installation wizard to configure that subsystem.
You should carefully consider whether you want to store this information in a
separate internal database for each subsystem or use one internal database for all
subsystems installed on the host.
It's recommended that you do not use this Directory Server instance for any other
purposes; the directory schema is configured for storing CMS data.

Tokens

You choose either the
token) or an external token to store the signing certificate and key pair and the SSL
signing certificate and key pair.
If you are using an external token, you will need to install it before you run the
Installation Wizard. In the wizard, you can select from a list of already installed
and available tokens. For example,
"External Token" on page 316.

Installing a Certificate Manager

You install the subsystems by installing the CMS software on each host in which
you will install a subsystem, and then creating an instance of CMS in that
installation for each subsystem you want to configure on that host. CMS provides
an Installation Wizard that allows you to choose which subsystem you are
installing in a particular instance, and allows you to make some configuration
choices for the subsystem, and get and install the certificates used by the
subsystem. Once the Certificate Manager is installed, it is set up with a default set
of configuration settings. You can change the default settings to meet the needs of
your PKI.

Installing a Certificate Manager as a Root CA

To configure the Certificate Manager as a root CA:
Log into Netscape Console as the administrator, see "Netscape Console" on
1.
page 245.
token (if you plan to use the internal/software
internal
SmartCard
Installing a Certificate Manager
. For installation instructions, see
Chapter 3 Certificate Manager 91