HP-UX Directory Server 8.1 deployment guide

• The attribute value stored in the CoS template entry.
Each CoS template entry supplies the attribute value for a particular CoS.
• The object class of the entry.
CoS attribute values are generated only when an entry contains an object class allowing the
attribute when schema checking is turned on; otherwise, all attribute values are generated.
• The attribute stored in some particular entry in the directory tree.
Types of CoS There are three different types of CoS depending on how the value of the dynamic
attributes is to be generated:
• Pointer CoS identifies the template entry using the template DN only. There may be only
one template DN for each pointer CoS. A pointer CoS applies to all entries within the scope
of the template entry.
• Indirect CoS identifies the template entry using the value of one of the target entry's attributes.
The target entry's attribute must contain the DN of an existing entry.
• 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 CoS template. For
example, use a role-based attribute to set the server look-through limit on a role-by-role basis.
4.4 Virtual directory information tree views
Directory Server supports a concept for hierarchical navigation and organization of directory
information called virtual directory information tree views or virtual DIT views.
NOTE:
Virtual views are not entirely compatible with multiple backends in that the entries to be returned
by the views must reside in the same backend; the search is limited to one backend.
4.4.1 About virtual DIT views
There are two ways to configure the directory namespace:
• A hierarchical directory information tree.
• A flat directory information tree.
The hierarchical DIT is useful for navigating the directory but is cumbersome and time-consuming
to change. A major organizational change to a hierarchical DIT can be an expensive and
time-consuming operation, because it usually involves considerable service disruption. This can
usually only be minimized by performing changes after hours and during periods of low traffic.
The flat DIT, while requiring little to no change, does not provide a convenient way to navigate
or manage the entries in the directory service. A flat DIT also presents many management
challenges as administration becomes more complex without any natural hierarchical groupings.
50 Designing the directory tree