Data Design; Schema Design - Red Hat DIRECTORY SERVER 7.1 - DEPLOYMENT Deployment Manual

An Enterprise

Data Design

example.com
example.com
how the directory will be used. The deployment team determines the following:
•
example.com
server, a human resources application, and a white pages application.
• The messaging server does exact searches on attributes such as the
mailServerName
performance,
support searches by the messaging server.
For more information on using indexes, see "Using Indexes to Improve
Database Performance," on page 108.
• The white pages application will frequently search for user names and phone
numbers. The directory will therefore need to be able to handle lots of
substring, wildcard, and sounds-like searches which return large sets of
results.
for the
•
example.com
LDAP server-based intranet deployed throughout the organization. Most of
example.com
group of directory administrators. However,
information to be managed by a separate group of mail administrators.
•
example.com
the future, such as S/MIME email, so it needs to be prepared to store the
public key certificates of users in the directory.

Schema Design

example.com
represent the entries in the directory. This object class is appealing because it
allows the
needed by the applications supported by
example.com
creates the
Corporation. It derives this object class from the
188 Red Hat Directory Server Deployment Guide • May 2005
first decides the type of data it will store in the directory. To do this,
creates a deployment team that performs a site survey to determine
's directory will be used by a messaging, web server, a calendar
, and
mailAddress
example.com
decides to maintain approximate and substring indexes
example.com
, , and
dn sn givenName
's directory maintains user and group information to support an
's user and group information will be centrally managed by a
plans to support public key infrastructure (PKI) applications in
's deployment team decides to use the
and
userCertificate
also wants to customize the default directory schema.
object class to represent employees of
examplePerson
attributes. To improve database
will maintain indexes for these attributes to
attributes.
example.com
inetOrgPerson
attributes, both of which are
uid(userID)
example.com
inetOrgPerson
,
uid
also wants email
object class to
's directory.
example.com
example.com
object class.