|
||
|
|
This chapter provides a brief overview of the configuration and administration utilities provided to manage the Netscape Directory Server (Directory Server).
This chapter is divided into the following sections:
- Overview of Directory Server Management
![]()
- Directory Server Configuration
![]()
- Directory Server Instance File Reference
![]()
- Migrating Directory Server
![]()
- Using Directory Server Command-Line Utilities
![]()
- Using Directory Server Command-Line Scripts
![]()
Overview of Directory Server Management
Directory Server is based on an open-systems server protocol called the Lightweight Directory Access Protocol (LDAP). The Directory Server is a robust, scalable server designed to manage large scale directories to support enterprise-wide directory of users and resources, extranets and e-commerce applications over the Internet. The Directory Server runs as the
ns-slapdprocess or service (slapdon Windows) on your machine. The server manages the directory databases and responds to client requests.You can perform most Directory Server administrative tasks through Netscape Console, the graphical user interface provided with the Directory Server. For information on the general use of the Netscape Console see Managing Servers with Netscape Console, and for details on how to use the console to manage the Directory Server in particular, see Netscape Directory Server Administrator's Guide.
This reference manual deals with the other methods of managing the Directory Server, namely altering the server configuration attributes via the command line and using the command-line utilities.
Directory Server Configuration
The format and method for storing configuration information for Directory Server mark a significant change from previous versions of the Directory Server. A full explanation of these changes and a listing for all server attributes can be found in Chapter 2 "Core Server Configuration Reference" and Chapter 3 "Plug-in Implemented Server Functionality Reference."
Directory Server Instance File Reference
Having an overview of the files and configuration information stored in each instance of Directory Server is useful, as this helps administrators understand the changes or absence of changes in the course of directory activity. From a security standpoint, such an overview can help customers detect errors and intrusion as they know what kind of changes to expect and what will be considered abnormal behavior. See Chapter 4 "Server Instance File Reference" for further information.
In earlier versions of the Directory Server (for example, versions 4.1x), all configuration parameters were stored in text files. In Directory Server 5.x onwards, configuration attributes are stored as LDAP configuration entries in the
dse.ldiffile. The mapping of configuration parameters between earlier versions of Directory Server and Directory Server 6.x is described in Chapter 6 "Migration from Earlier Versions."Using Directory Server Command-Line Utilities
Directory Server comes with a set of configurable command-line utilities that you can use to search and modify entries in the directory and administer the server. Chapter 7 "Command-Line Utilities"describes these command-line utilities and contains information on where the utilities are stored and how to access them. In addition to these command-line utiltiies, Directory Server also provides
ns-slapdandslapd.execommand-line utilities for performing directory operations as described in Appendix A "Using the ns-slapd and slapd.exe Command-Line Utilities."Using Directory Server Command-Line Scripts
In addition to command-line utilities, several non-configurable scripts are provided with the Directory Server that make it quick and easy to perform routine server administration tasks from the command line. Chapter 8 "Command-Line Scripts" lists the most frequently used scripts and contains information on where the scripts are stored and how to access them.
© 2001 Sun Microsystems, Inc. Portions copyright 1999, 2002-2003 Netscape Communications Corporation. All rights reserved.
Read the Full Copyright and Thrid-Party Acknowledgments.
Last Updated October 30, 2003