For information about customizing the default directory schema, refer to
"Customizing the Schema," on page 46.
Directory Tree Design
creates a directory tree as follows:
example.com
•
The directory tree is rooted in the suffix
creates two branch. One branch,
example.com
contains data internal to
dc=exampleNet,dc=com
•
The directory tree for the intranet (under
three main branches, each corresponding to one of the regions where
has offices. These branches are identified using the
example.com
attribute.
l(locality)
•
Each main branch under
directory tree design of
creates an
example.com
branch. See "Directory Tree for example.com Corporation," on
ou=resources
page 168 for more information about this directory tree design.
•
Under the
dc=exampleNet,dc=com
branches. One branch for suppliers (
(
), and one branch for groups (
o=partners
•
The
branch of the extranet contains entries for the administrators of
ou=groups
the extranet as well as mailing lists that partners subscribe to for up-to-date
information on auto part manufacturing.
The basic directory tree that results appears as follows:
Basic Directory Tree for example.com International
Figure 8-6
The directory tree for the
dc=com
International. The other branch,
example.com
, contains data for the extranet.
dc=exampleCorp,dc=com)
dc=exampleCorp,dc=com
Corporation. Under each locality,
example.com
, an
ou=people
ou=groups
branch,
o=suppliers
intranet appears as follows:
example.com
A Multinational Enterprise and its Extranet
. Under this suffix,
dc=exampleCorp,dc=com
mimics the original
, an
ou=roles
creates three
example.com
), one branch for partners
).
ou=groups
Chapter 8
Directory Design Examples
,
has
, and an
177
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - DEPLOYMENT and is the answer not in the manual?
Questions and answers