HP-UX Directory Server 8.1 deployment guide

9.1.3 Local enterprise directory tree design
Based on the data and schema design described in the preceding sections, Example Corp. creates
the following directory tree:
• The root of the directory tree is Example Corp.'s Internet domain name: dc=example,
dc=com.
• The directory tree has four branch points: ou=people, ou=groups, ou=roles, and
ou=resources.
• All Example Corp.'s people entries are created under the ou=people branch.
The people entries are all members of the person, organizationalPerson,
inetOrgPerson, and examplePerson object classes. The uid attribute uniquely identifies
each entry's DN. For example, Example Corp. contains entries for Babs Jensen
(uid=bjensen) and Emily Stanton (uid=estanton).
• They create three roles, one for each department in Example Corp.: sales, marketing, and
accounting.
Each person entry contains a role attribute which identifies the department to which the
person belongs. Example Corp. can now create ACIs based on these roles.
For more information about roles, see “About roles”.
• They create two group branches under the ou=groups branch.
The first group, cn=administrators, contains entries for the directory administrators,
who manage the directory contents.
The second group, cn=messaging admin, contains entries for the mail administrators,
who manage mail accounts. This group corresponds to the administrators group used by
the messaging server. Example Corp. ensures that the group it configures for the messaging
server is different from the group it creates for Directory Server.
• They create two branches under the ou=resources branch, one for conference rooms
(ou=conference rooms) and one for offices (ou=offices).
• They create a class of service (CoS) that provides values for the mailquota attribute
depending on whether an entry belongs to the administrative group.
This CoS gives administrators a mail quota of 100GB while ordinary Example Corp.
employees have a mail quota of 5GB.
See “About class of service” for more information about class of service.
The following diagram illustrates the directory tree resulting from the design steps listed above:
126 Directory design examples