This installation guide describes the Red Hat Directory Server 9.1 installation process and the migration process. This manual provides detailed step-by-step procedures for all supported operating systems, along with explanations of the different setup options (express, typical, custom, and silent), additional options for Directory Server instance creation, migrating previous versions of Directory Server, and troubleshooting and basic usage.
Directory Server 9.1 provides a migration tool for upgrading or migrating from earlier Directory Server versions. If you already have a Directory Server deployment that is supported for migration, you must use the documented migration procedure to migrate your data and configuration to version 9.1. Chapter 5, Migrating from Previous Versions
has for more information.
To become more familiar with directory service concepts, consult the Red Hat Directory Server Deployment Guide; that manual is designed to help you plan the most effective directory service for your organization's requirements. For instructions on using Directory Server itself, see the Red Hat Directory Server Administration Guide.
The Directory Server setup process requires information specific to the Directory Server instance being configured, information about the host names, port numbers, passwords, and IP addresses that will be used. The setup program attempts to determine reasonable default values for these settings based on your system environment. Read through this manual before beginning to configure the Directory Server to plan ahead what values to use.
If you are installing Directory Server for evaluation, use the express or typical setup mode. These processes are very fast, and can help get your directory service up and running quickly.
Red Hat Directory Server 9.1 introduces filesystem paths for configuration files, scripts, commands, and database files used with Directory Server which comply with Filesystem Hierarchy Standard (FHS). This file layout is very different than previous releases of Directory Server, which installed all of the files and directories in
. If you encounter errors during the installation process, look at Section 6.6, “Troubleshooting”
. For more information on how the file layout has changed, see Section 6.1, “Directory Server File Locations”
The latest Directory Server release is available for your platform and operating system through the Red Hat Customer Portal
1. Examples and Formatting
Each of the examples used in this guide, such as file locations and commands, have certain defined conventions.
1.1. Command and File Examples
All of the examples for Red Hat Directory Server commands, file locations, and other usage are given for Red Hat Enterprise Linux 6.2 (64-bit) systems. Be certain to use the appropriate commands and files for your platform.
Example 1. Example Command
To start the Red Hat Directory Server:
# service dirsrv start
Square brackets (
) are used to indicate an alternative element in a name. For example, if a tool is available in
/usr/lib on 32-bit systems and in
/usr/lib64 on 64-bit systems, then the tool location may be represented as
1.4. Text Formatting and Styles
Certain words are represented in different fonts, styles, and weights. Different character formatting is used to indicate the function or purpose of the phrase being highlighted.
| Formatting Style || Purpose |
| Monospace is used for commands, package names, files and directory paths, and any text displayed in a prompt. |
| This type of formatting is used for anything entered or returned in a command prompt. |
| Italicized text || Any text which is italicized is a variable, such as instance_name or hostname. Occasionally, this is also used to emphasize a new term or other phrase. |
| Bolded text || Most phrases which are in bold are application names, such as Cygwin, or are fields or options in a user interface, such as a User Name Here: field or button. |
Other formatting styles draw attention to important text.
A note provides additional information that can help illustrate the behavior of the system or provide more detail for a specific issue.
Important information is necessary, but possibly unexpected, such as a configuration change that will not persist after a reboot.
A warning indicates potential data loss, as may happen when tuning hardware for maximum performance.