Novell EDIRECTORY WHAT'S NEW GUIDE

Novell eDirectory 8.8 What's New Guide

Novell

novdocx (ENU) 01 February 2006

eDirectory

8.8

WHAT'S NEW GUIDE

June 09, 2006

TM

www.novell.com

Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no
responsibility for your failure to obtain any necessary export approvals.

Copyright © 2005-2006 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.

novdocx (ENU) 01 February 2006

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent
applications in the U.S. and in other countries.

Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com

Online Documentation: To access the online documentation for this and other Novell products, and to get

updates, see www.novell.com/documentation.

Novell Trademarks

Client32 is a trademark of Novell, Inc.

eDirectory is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc., in the United States and other countries.

NetWare Core Protocol and NCP are trademarks of Novell, Inc.

NMAS is a trademark of Novell, Inc.

Novell is a registered trademark of Novell, Inc., in the United States and other countries.

Novell Client is a trademark of Novell, Inc.

Novell Directory Services and NDS are registered trademarks of Novell, Inc., in the United States and other

countries.

Ximiam is a registerd trademark of Novell, Inc., in the United States and other countries.

ZENworks is a registered trademark of Novell, Inc., in the United States and other countries.

Third-Party Materials

All third-party trademarks are the property of their respective owners.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://

www.openssl.org).

novdocx (ENU) 01 February 2006

novdocx (ENU) 01 February 2006

About This Guide

Welcome to Novell® eDirectoryTM 8.8. This guide introduces you to the new features in this product.

eDirectory 8.8 provides a host of new features and enhancements to further strengthen eDirectory's
leadership in the directory market.

This guide introduces the following:

• Chapter 1, “Install and Upgrade Enhancements,” on page 7

• Chapter 2, “Multiple Instances,” on page 21

• Chapter 3, “Authentication to eDirectory through SASL-GSSAPI,” on page 29

• Chapter 4, “Enforcing Case-Sensitive Universal Passwords,” on page 33

• Chapter 5, “Priority Sync,” on page 41

• Chapter 6, “Data Encryption,” on page 43

• Chapter 7, “Bulkload Performance,” on page 47

novdocx (ENU) 01 February 2006

• Chapter 8, “iManager ICE Plug-ins,” on page 49

• Chapter 9, “LDAP-Based Backup,” on page 53

• Chapter 10, “Managing Error Logging in eDirectory 8.8,” on page 55

• Chapter 11, “Offline Bulkload Utility: ldif2dib,” on page 65

• Chapter 12, “Miscellaneous,” on page 67

Audience

The guide is intended for network administrators.

Feedback

We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.

Documentation Updates

For the most recent version of this guide, see Novell eDirectory 8.8 What's New Guide (http://

www.novell.com/documentation/beta/edir88/edir88new/data/front.html).

Additional Documentation

For more information about eDirectory 8.8, refer to the following:

• Novell eDirectory 8.8 Installation Guide

• Novell eDirectory 8.8 Administration Guide

• Novell eDirectory 8.8 Troubleshooting Guide

5

These guides are available at Novell eDirectory 8.8 documentation Web site (http://

www.novell.com/documentation/edir88/index.html).

For information about the eDirectory management utility, refer to Novell iManager 2.5

Administration Guide (http://www.novell.com/documentation/imanager25/index.html).

Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
within a cross-reference path.

®

A trademark symbol (

, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party

trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* and UNIX*, should use forward slashes as required by your software.

novdocx (ENU) 01 February 2006

6 Novell eDirectory 8.8 What's New Guide

1

Install and Upgrade

novdocx (ENU) 01 February 2006

Enhancements

This chapter discusses the new features and enhancements with the Novell® eDirectoryTM 8.8
installation and upgrade.

The following table lists the new features and specifies the platforms they are supported on.

Feature NetWare Linux UNIX Windows

Multiple package formats for installing eDirectory 8.8

Automatic deployment through Ximian
Management 2.2

Install and configure eDirectory through YaST

Custom location install for application files

Custom location install for data files

Custom location install for configuration files

Nonroot install

FHS compliance

®

ZENworks® Linux

1

LSB compliance

Server health checks

SecretStore integration

The following features are discussed in this chapter:

• Multiple Package Formats for Installing eDirectory 8.8 (page 8)

• Automatic Deployments (page 8)

• Installing and Configuring eDirectory Through YaST (page 10)

• Installing eDirectory 8.8 in a Custom Location (page 10)

• Nonroot Install (page 12)

• Standards Compliance (page 13)

• Server Health Checks (page 14)

• SecretStore Integration with eDirectory (page 19)

• Unattended Upgrade to eDirectory 8.8 SP1 on Netware (page 19)

Install and Upgrade Enhancements

7

1.1 Multiple Package Formats for Installing eDirectory 8.8

On Linux* and UNIX, you have an option to choose from various file formats while installing
eDirectory 8.8 on your host. The file formats are listed in the table below.

novdocx (ENU) 01 February 2006

Type of User and
Installation Location

Root user:

Default location RPM Package File-set Depot

Custom location Tarball Package and

Nonroot user:

Custom location Tarball Tarball Tarball Tarball

For more information on installing using tarballs, refer to the Novell eDirectory 8.8 Installation

Guide (http://www.novell.com/documentation/edir88/edirin88/data/a79kg0w.html#bs6a3gs).

Linux Solaris AIX HP-UX

Tarball Depot and tarball

tarball

1.2 Automatic Deployments

eDirectory 8.8 on Linux leverages ZENworks® Linux Management to provide easy upgrade
distribution and deployment. For more information, refer to ZENworks Linux Management (http://

www.novell.com/products/zenworks/linuxmanagement/index.html).

8 Novell eDirectory 8.8 What's New Guide

1.2.1 Upgrade Distributions

With eDirectory 8.8, you can subscribe to a specific feature that eDirectory offers and whenever
there is an update (upgrade or patch) to this feature on the Novell site, you will automatically get this
update.

Figure 1-1 Upgrade Distributions

novdocx (ENU) 01 February 2006

To facilitate this, you need to install the ZENworks Linux Management client on the host where
eDirectory 8.8 is present and subscribe to the ZENworks Linux Management server that would
inform you when there is an update.

Install and Upgrade Enhancements 9

1.2.2 Easy Deployments

With eDirectory 8.8, you can install eDirectory on a host that has the ZENworks Linux Management
server installed and then roll it out to the other servers that have installed ZENworks Linux
Management clients.

Figure 1-2 eDirectory Distribution through RedCarpet

novdocx (ENU) 01 February 2006

1.3 Installing and Configuring eDirectory Through YaST

On SLES 9.1 or otherwise known as Open Enterprise Server (OES), you can install and configure
eDirectory 8.8 through YaST.

For more information on installing and configuring eDirectory through YaST, refer to the Novell

eDirectory 8.8 Installation Guide (http://www.novell.com/documentation/edir88/edirin88/data/
a79kg0w.html#bv1lxl8).

1.4 Installing eDirectory 8.8 in a Custom Location

eDirectory 8.8 gives you the flexibility to install the application, data, and configuration files in a
location of your choice.

One of the scenarios for installing eDirectory 8.8 in a custom location is when you already have an
earlier version of eDirectory installed on your host and you want to test eDirectory 8.8 before
upgrading to it. This way, you can have your existing eDirectory setup undisturbed and also test this
new version. You can then decide whether you want to retain your existing version or want to
upgrade to eDirectory 8.8.

10 Novell eDirectory 8.8 What's New Guide

NOTE: SLP and the SNMP subagent are installed in the default locations.

This section explains how to install the various files in a custom location:

• Section 1.4.1, “Specifying a Custom Location for Application Files,” on page 11

• Section 1.4.2, “Specifying a Custom Location for Data Files,” on page 11

• Section 1.4.3, “Specifying a Custom Location for Configuration Files,” on page 12

1.4.1 Specifying a Custom Location for Application Files

While installing eDirectory, you can install your application files in a location of your choice.

Linux and UNIX

To install eDirectory 8.8 in a custom location, you can use the Tarball installation file and untar
eDirectory 8.8 in a location of your choice.

NetWare

novdocx (ENU) 01 February 2006

You cannot specify a custom location for the application files on NetWare.

Windows

You were able to specify a custom location for the application files during the installation Wizard
even prior to eDirectory 8.8.

1.4.2 Specifying a Custom Location for Data Files

While configuring eDirectory, you can save the data files in a location of your choice. The data files
include the data, dib, and log directories.

Linux and UNIX

To configure the data files in a custom location, you can use either the -d or -D option of the
ndsconfig utility.

Option Description

-d custom_location Creates the DIB (the eDirectory database) directory in the path mentioned.

NOTE: This option was present prior to eDirectory 8.8 also.

-D custom_location Creates the data (contains data such as the pids and socket IDs), dib, and
log directories in the path mentioned.

NetWare

You cannot select a custom DIB path while upgrading eDirectory. On NetWare, eDirectory
installation is always an upgrade. Therefore, you cannot choose a custom DIB path on NetWare.

Install and Upgrade Enhancements 11

Windows

On Windows you would be prompted to enter the DIB path during the installation. Enter a path of
your choice.

1.4.3 Specifying a Custom Location for Configuration Files

While configuring eDirectory, you can select the path where you want to save your configuration
files.

Linux and UNIX

To configure the nds.conf configuration file to a different location, use the --config-file option of the
ndsconfig utility.

To install the other configuration files (such as modules.conf, ndsimon.conf, and
ice.conf) to a different location, do the following:

1 Copy all the configuration files to the new location.

2 Set the new location by entering the following:

novdocx (ENU) 01 February 2006

ndsconfig set n4u.nds.configdir custom_location

NetWare and Windows

You cannot specify a custom location for the configuration files on NetWare and Windows.

1.5 Nonroot Install

This feature enables a user who does not have the root privileges to install eDirectory 8.8 on Linux
and UNIX. If a root user installs eDirectory, a non-root user can use it.

This feature is not supported on NetWare and Windows.

IMPORTANT: A nonroot user cannot install SLP or the SNMP subagent.

Generally, there are two kinds of non-root users:

• A user who is not the root on the UNIX machine. For more information, see Section 1.5.1,

“Nonroot User,” on page 12.

• A user who is not the administrator for eDirectory. For more information, see Section 1.5.2,

“Nonadminstrator User,” on page 13.

1.5.1 Nonroot User

• “Nonroot User Who Installs eDirectory” on page 12

• “Nonroot User Who Configures eDirectory” on page 13

Nonroot User Who Installs eDirectory

This user is not a root on the host machine. The right for a nonroot user to install eDirectory is bound
by the right the user has on the host machine.

12 Novell eDirectory 8.8 What's New Guide

Nonroot User Who Configures eDirectory

This user is not a root on the host machine. The right for a nonroot user to configure eDirectory is
bound by the right the user has on the host machine.

1.5.2 Nonadminstrator User

This user is not the administrator of eDirectory. The right for a nonadministrator user to configure
eDirectory depends on the rights assigned to the user's object in eDirectory.

1.6 Standards Compliance

eDirectory 8.8 is compliant with the following standards:

• Section 1.6.1, “FHS Compliance,” on page 13

• Section 1.6.2, “LSB Compliance,” on page 14

1.6.1 FHS Compliance

novdocx (ENU) 01 February 2006

To avoid file conflicts with other product application files, eDirectory 8.8 follows the Filesystem
Hierarchy Standard (FHS). This feature is available only on Linux and UNIX.

eDirectory follows this directory structure only if you have chosen to install it in the default
location. If you have chosen a custom location, the directory structure would be custom_location/
default_path.

For example, if you choose to install in the eDir88 directory, the same directory structure would be
followed in the eDir88 directory, like the man pages would be installed in the /eDir88/opt/
novell/man directory.

The following table lists the change in the directory structure:

Types of Files Stored in the Directory Directory Name and Path

Executable binaries and static shell scripts /opt/novell/eDirectory/bin

Executable binaries for root use /opt/novell/eDirectory/sbin

Static or dynamic library binaries /opt/novell/eDirectory/lib

Configuration files /etc/opt/novell/eDirectory/conf

Read/Write, run-time dynamic data like the DIB /var/opt/novell/eDirectory/data

Log files /var/opt/novell/eDirectory/log

Linux and UNIX man pages /opt/novell/man

Export Environmental Variables

With the FHS implementation in eDirectory 8.8, you need to update the path environmental
variables and export them. This creates the following problems:

• You need to remember all the paths exported, so that whenever you open a shell, you need to
export these paths and start using the utilities.

Install and Upgrade Enhancements 13

• When you want to use more than one set of binary, you have to open more than one shell or
have to unset and set the paths to the different set of binaries frequently.

To resolve the above issue, you can use the /opt/novell/eDirectory/bin/ndspath
script as follows:

• Prefix the ndspath script to the utility and run the utility you want as follows:

custom_location/opt/novell/eDirectory/bin/ndspath
utility_name_with_parameters

• Export the paths in the current shell as follows:

. custom_location/opt/novell/eDirectory/bin/ndspath

• After entering the above command, run the utilities as you would normally do. Call the script in
your profile, bashrc, or similar scripts. Therefore, whenever you log in or open a new shell, you
can start using the utilities directly.

1.6.2 LSB Compliance

eDirectory 8.8 is now Linux Standard Base (LSB) compliant. LSB also recommends FHS
compliance. All the eDirectory packages in Linux are prefixed with novell. For example, NDSserv
is now novell-NDSserv.

novdocx (ENU) 01 February 2006

1.7 Server Health Checks

eDirectory 8.8 introduces server health checks that help you determine whether your server health is
safe before upgrading.

The server health checks run by default with every upgrade and occur before the actual package
upgrade. However, you can also run the diagnostic tool ndscheck (or dscheck on NetWare) to do the
health checks.

1.7.1 Need for Health Checks

In earlier releases of eDirectory, the upgrade did not check the health of the server before proceeding
with the upgrade. If the heath was unstable, the upgrade operation would fail and eDirectory would
be in an inconsistent state. In some cases, you probably could not roll back to the pre-upgrade
settings.

This new health check tool resolves this, letting you to ensure that your server is ready to upgrade.

1.7.2 What Makes a Server Healthy?

The server health check utility performs certain health checks to ensure that the tree is healthy. The
tree is declared healthy when all these health checks are completed successfully.

1.7.3 Performing Health Checks

You can perform server health checks in two ways:

• “With the Upgrade” on page 15

• “As a Standalone Utility” on page 15

14 Novell eDirectory 8.8 What's New Guide

NOTE: You need administrative rights to run the health check utility.

With the Upgrade

The health checks are run by default every time you upgrade eDirectory.

Linux and UNIX

Every time you upgrade, the health checks are run by default before the actual upgrade operation
starts.

To skip the default health checks, you can use the -j option with the nds-install utility.

NetWare and Windows

The server health checks happen as part of the installation wizard. You can enable or disable the
health checks when prompted to do so.

As a Standalone Utility

novdocx (ENU) 01 February 2006

You can run the server health checks as a standalone utility any time you want. The following table
explains the health check utilities.

Table 1-1 Health Check Utilities

Platform Utility Name

Linux and UNIX ndscheck

Syntax:

ndscheck -h hostname:port -a admin_FDN -F
logfile_path --config-file
configuration_file_name_and_path

NOTE: You can specify either -h or --config-file and not both of them.

NetWare dscheck

Windows ndscheck

1.7.4 Types of Health Checks

When you upgrade or run the ndscheck utility, the following types of health checks are done:

• Basic Server Health

• Partitions and Replica Health

If you run the ndscheck utility, the results from the health checks are displayed on the screen and
logged in to ndscheck.log (or dscheck.log on NetWare). For more information on log files,
refer to Section 1.7.6, “Log Files,” on page 18.

Install and Upgrade Enhancements 15

If the health checks are done as part of the upgrade, then after the health checks, based on the
criticality of the error, either you are prompted to continue the upgrade process or the process is
aborted. The details of the errors are described in Section 1.7.5, “Categorization of Health,” on

page 16.

Basic Server Health

This is the first stage of the health check.The health check utility checks for the following:

1. The eDirectory service is up. The DIB is open and able to read some basic tree information
such as the tree name.

2. The server is listening on the respective port numbers.

For LDAP, it gets the TCP and the SSL port numbers and checks if the server is listening on
these ports.

Similarly, it gets the HTTP and HTTP secure port numbers and checks if the server is listening
on these ports.

Partitions and Replica Health

novdocx (ENU) 01 February 2006

After checking the basic server health, the next step is to check the partitions and replica health as
follows:

1. Checks the health of the replicas of the locally held partitions.

2. Reads the replica ring of each and every partition held by the server and checks whether all
servers in the replica ring are up and all the replicas are in the ON state.

3. Checks the time synchronization of all the servers in the replica ring. This shows the time
difference between the servers.

1.7.5 Categorization of Health

Based on the errors found while checking the health of a server, there can be the three categories of
health. The status of the health checks is logged in to a logfile. For more information, refer to

Section 1.7.6, “Log Files,” on page 18.

The three categories of health Normal, War ni ng , and Critical.

Normal

The server health is normal when all the health checks were successful.

The upgrade proceeds without interruption.

Warning

The server health is in the warning category when minor errors are found while checking the health.

If the health check is run as part of the upgrade, you are prompted to either abort or continue.

Warnings normally occur in the following scenarios:

1. Server not listening on LDAP and HTTP ports, either normal or secure or both.

2. Unable to contact any of the nonmaster servers in the replica ring.

16 Novell eDirectory 8.8 What's New Guide

3. Servers in the replica ring are not in sync.

For more information, see the following figure.

Figure 1-3 Health Check with a Warning

novdocx (ENU) 01 February 2006

Critical

The server health is critical when critical errors were found while checking the health.

If the health check is run as part of the upgrade, the upgrade operation is aborted.

The critical state normally occurs in the following cases:

1. Unable to read or open the DIB. The DIB might be locked or corrupt.

2. Unable to contact all the servers in the replica ring.

3. Locally held partitions are busy.

4. Replica is not in the ON state.

Install and Upgrade Enhancements 17

For more information, see the following figure.

Figure 1-4 Health Check with a Critical Error

novdocx (ENU) 01 February 2006

1.7.6 Log Files

Every server health check operation, whether it is run with the upgrade or as a standalone utility,
maintains the status of the health in a log file.

The content of the log file is similar to the messages displayed on the screen when the checks are
happening. For example, see Figure 1-3 and Figure 1-4 above.

The health check log file contains the following:

• Status of the health checks (normal, warning, or critical).

• URLs to the Novell support site.

The following table gives you the locations for the log file on the various platforms:

18 Novell eDirectory 8.8 What's New Guide

Table 1-2 Health Check Logfile Locations

Platform Logfile Name Logfile Location

Linux and UNIX ndscheck.log Depends on the location you specified with the

ndscheck -F utility.

If you did not use the -F option, the location of
the ndscheck.log file is determined by the
other options you used at the ndscheck
command line as follows:

1. If you used the -h option, the ndscheck.log
file is saved in the user’s home directory.

2. If you used the --config-file option, the
ndscheck.log file is saved in the server
instance’s log directory. You can also
select an instance from the multiple
instances list.

NetWare dscheck.log sys:\system

novdocx (ENU) 01 February 2006

Windows ndscheck.log install_directory

1.8 SecretStore Integration with eDirectory

eDirectory 8.8 gives you an option to configure Novell SecretStore® 3.4 during eDirectory
configuration. Prior to eDirectory 8.8, you had to manually install SecretStore.

SecretStore is a simple and secure password management solution. It enables you to use a single
authentication to eDirectory to access most UNIX, Windows, Web, and mainframe applications.

After you've authenticated to eDirectory, SecretStore-enabled applications store and retrieve the
appropriate login credentials. When you use SecretStore, you eliminate the need to remember or
synchronize all the multiple passwords required for accessing password-protected applications, Web
sites, and mainframes.

To configure SecretStore 3.4 along with eDirectory, you can do the following:

• Linux and UNIX:

Use the ndsconfig add -m ss parameter. Here, ss denotes SecretStore and is an
optional parameter. If you do not mention the module name, all the modules are installed.

• NetWare and Windows:

Installed by default with eDirectory installation.

For more information on the SecretStore usage, refer to the Novell SecretStore Administration Guide

(http://www.novell.com/documentation/secretstore33/index.html).

1.9 Unattended Upgrade to eDirectory 8.8 SP1 on Netware

Novell® ZENworks® Server Management provides the Server Software Packages component for
managing files and applications on your network. Using software packages, you can automate the

Install and Upgrade Enhancements 19

installation and upgrading of software on your servers. Software management is done by creating
Server Software Packages and distributing them using Tiered Electronic Distribution. You can
configure Server Software Packages so that a server must meet certain minimum requirements
before a package is installed on it.

The automated upgrade for eDirectory on Netware for ZFS environment is delivered as SPK along
with the source. SPK has to be inserted into the ConsoleOne “Server Software Packages” snap-in for
customizing into local environments. Once the Server Software Package ConsoleOne snap-in is
installed, you can insert this SPK in the ConsoleOne.

The compiled CPK is not provided since the user is expected to provide values for the variables
containing administrator credentials. This SPK needs to be compiled to a CPK in the customer site
after providing values to these variables.

For more information on this utility, refer to “Unattended Upgrade to eDirectory 8.8 SP1 on
Netware” of eDirectory 8.8 Installation Guide.

1.10 For More Information

Refer to the following for more information on any of the features discussed in this chapter:

novdocx (ENU) 01 February 2006

• Novell eDirectory 8.8 Installation Guide (http://www.novell.com/documentation/edir88/

edirin88/data/a2iii88.html)

• Novell eDirectory 8.8 Administration Guide (http://www.novell.com/documentation/edir88/

edir88/data/fbadjaeh.html#fbadjaeh)

• On Linux and UNIX: nds-install, ndsconfig, and ndscheck man pages

20 Novell eDirectory 8.8 What's New Guide

2

Multiple Instances

Traditionally, you could configure only one instance of Novell® eDirectoryTM on a single host. With
the multiple instances feature support in eDirectory 8.8, you can configure the following:

• Multiple instances of eDirectory on a single host

• Multiple trees on a single host

• Multiple replicas of the same tree or partition on a single host

eDirectory 8.8 also provides you with a utility (ndsmanage) to easily track the instances.

The following table lists the platforms that support the multiple instances:

Feature NetWare Linux UNIX Windows

Multiple instances support

novdocx (ENU) 01 February 2006

2

This chapter includes the following information:

• Section 2.2, “Sample Scenarios for Deploying Multiple Instances,” on page 21

• Section 2.3, “Using Multiple Instances,” on page 22

• Section 2.4, “Managing Multiple Instances,” on page 23

• Section 2.5, “Sample Scenario for Multiple Instances,” on page 27

2.1 Need for Multiple Instances

Multiple instances arose from the need to:

• Leverage high-end hardware by configuring more than one instance of eDirectory.

• Pilot your setup on a single host before investing on the required hardware.

2.2 Sample Scenarios for Deploying Multiple Instances

Multiple instances that belong to the same or multiple trees can be used in the following scenarios
effectively.

eDirectory in a Large Enterprise

• In large enterprises, you can provide load balancing and high availability of eDirectory
services.

For example, if you have three replica servers running LDAP services on ports 1524, 2524, and
3524, respectively, you can configure a new instance of eDirectory and provide a high­availability LDAP service on a new port 636.

• You can leverage high-end hardware across departments in an organization by configuring
multiple instances on a single host.

Multiple Instances

21