Directory Tree Design Examples; Directory Tree For An International Enterprise - Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual

Directory Tree Design Examples

• Classic CoS—A classic CoS identifies the template entry by both its DN and the
value of one of the target entry's attributes. Classic Cos can have multiple
template entries, including a default CoS template to be applied to those
entries that do not belong to any other CoS template.
Roles and the Classic CoS can be used together to provide role-based attributes.
These attributes appear on an entry because it possesses a particular role with an
associated class of service template. For example, you could use a role-based
attribute to set the server look through limit on an role-by-role basis.
Directory Tree Design Examples
The following sections provide examples of directory trees designed to support a
flat hierarchy as well as several examples of more complicated hierarchies.

Directory Tree for an International Enterprise

To support an international enterprise, root your directory tree in your Internet
domain name and then branch your tree for each country where your enterprise
has operations immediately below that root point. In "Suffix Naming
Conventions," on page 59, you are advised to avoid rooting your directory tree in a
country designator. This is especially true if your enterprise is international in
scope.
Because LDAP places no restrictions on the order of the attributes in your DNs,
you can use the
follows:
However, some administrators feel that this is stylistically awkward, so instead
you could use the
74 Netscape Directory Server Deployment Guide • January 2002
( ) attribute to represent each country branch as
c countryName
( ) attribute to represent different countries:
l locality