Overview Of Directory Server Architecture - Netscape DIRECTORY SERVER 6.1 - DEPLOYMENT Deployment Manual

Introduction to Directory Server
You can use Directory Server to manage extranet user-authentication, create access
control, set up user preferences, and centralize user management. In hosted
environments, partners, customers, and suppliers can manage their own portions
of the directory, reducing administrative costs.
When you install Directory Server, the following components are installed on your
machine:
• An LDAP server (Directory Server) with a plug-in interface
The name of this process is
• Netscape Administration Server
For more information about the Administration Server, see Managing Servers
with Netscape Console.
• Netscape Console to manage the servers
For more information about the Netscape Console, see Managing Servers with
Netscape Console.
• Command-line tools for starting and stopping the server, importing and
exporting data in the database, database reindexing, account inactivation and
deactivation, LDIF merges, and kernel tuning
For more information about the command-line tools, refer to Netscape Directory
Server Configuration, Command, and File Reference.
• An SNMP monitor
For more information about SNMP monitoring, refer to the Netscape Directory
Server Administrator's Guide.
This guide talks about the core Directory Server and the plug-ins it uses for doing
its work. The next sections describe Directory Server in more detail. The topics
discussed are:
• "Overview of Directory Server Architecture," on page 16
• "Directory Server Data Storage," on page 19

Overview of Directory Server Architecture

At installation, Directory Server contains the following:
• A server front-end responsible for network communications
• Plug-ins for server functions, such as access control and replication
16 Netscape Directory Server Deployment Guide • August 2002
.
ns-slapd