Netscape NETSCAPE MANAGEMENT SYSTEM 4.5, Installation And Setup Manual

Page: 369 / 866

Road Map to Configuring Subsystems
Chapter 10 CMS Configuration 369
For instructions to do all of the above tasks, see “Configuring Policy Rules for a
Subsystem” on page 589.
Step 10. Set up Publishing
This step is optional, and is applicable to the Certificate Manager only—you need
to do this only if you want the Certificate Manager to publish certificates and CRLs
to any of the supported repositories.
• To configure a Certificate Manager to publish certificates and CRLs to an
LDAP-compliant directory, such as Netscape Directory Server, see
“Configuring a Certificate Manager to Publish Certificates and CRLs” on
page 615.
• To configure a Certificate Manager to publish certificates and CRLs to a flat
file, see “Configuring Certificate Manager to Publish to Files” on page 667.
• To configure a Certificate Manager to publish CRLs to the Online Certificate
Status Manager (an online validation authority), see “Setting Up a Remote
OCSP Responder” on page 708.
Step 11. Set up Key Archival and Recovery
If you have installed the Data Recovery Manager, follow the instructions in
“Configuring Key Archival and Recovery Process” on page 751 and set up archival
and recovery for end users’ encryption private keys.
Step 12. Set up Logging
Each instance of Certificate Management System maintains extensive audit, error,
and system logs. By looking at these logs, you can monitor a server’s activities.
Also, by configuring these logs, you can control the information that gets written to
the log files. Because Certificate Management System maintains the log files in the
file system of the host machine, it is important that you configure the logs
appropriately (so that the host machine doesn’t get overloaded). Be sure to read
“Introduction to Logs” on page 765; this chapter will help you decide log
configuration.
Once you decide the configuration for server logs, follow the information in
“Configuring CMS Logs” on page 773 and configure all the three logs. Then, start
monitoring the server’s activities as explained in “Monitoring CMS Logs” on
page 779.