Table of Contents
Advertisement
Directory Design Overview
For more information about roles, see "About Roles," on page 71. For more
information about class of service, see "About Class of Service," on page 72.
Distributing Directory Data
When you store various parts of your tree in separate databases, your directory can
process client requests in parallel, improving performance. You can also store your
databases on different machines, to further improve performance.
To connect your distributed data, you can create a special entry in a subtree of your
directory. All LDAP operations attempted below this entry are sent to a remote
machine where the entry is actually stored. This method is called chaining.
Chaining is implemented in the server as a plug-in. The plug-in is enabled by
default. Using this plug-in, you create database links, special entries that point to
data stored remotely. When a client application requests data from a database link,
the database link retrieves the data from the remote database and returns it to the
client.
Directory Design Overview
The previous sections described directory services in general and the Directory
Server in particular. Now it is time to consider the design of your own directory
service.
Planning your directory service before actual deployment is the most important
task to ensure the success of your directory. During your directory design you will
gather data about your directory requirements, such as environment and data
sources, your users, and the applications that will use your directory. With this
data, you can design a directory service that meets your needs.
However, keep in mind that the flexibility of Directory Server allows you to rework
your design to meet unexpected or changing requirements, even after you deploy
Directory Server.
Chapter 1
Introduction to Directory Server
21
Advertisement
Table of Contents
