Overview - Red Hat DIRECTORY SERVER 7.1 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

Overview

When considering directory namespace, you have the choice of creating either of
the following:
A hierarchical directory information tree.
A flat directory information tree.
The hierarchical DIT is useful for navigating the directory but is cumbersome and
time-consuming to change. The flat DIT, while requiring little to no change, does
not provide a convenient way to navigate or manage the entries in the directory. A
flat DIT also presents many management challenges as administration becomes
more complex without any natural hierarchical groupings. On the other hand, a
major organizational change to a hierarchical DIT can be an expensive and
time-consuming operation as it usually involves considerable service disruption,
which can only be minimized by operating during late hours and periods of low
traffic. Also, moving millions of entries from one place in a hierarchy to another is a
lot of work.
Figure 4-1 shows examples of a flat and an organizationally-based DIT.
Figure 4-1
Examples of a Flat and an Organizationally-Based DIT
Having decided upon a hierarchical DIT, a deployment must then decide upon the
subject domain of the hierarchy. Only one choice can be made, and that tends to
mean that only one natural choice is available: the organizational hierarchy.
Virtual Directory Information Tree Views
Chapter 4
Designing the Directory Tree
81

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 7.1

Table of Contents