HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

• By its DN
To have the template entry identified by only its DN (a pointer CoS), enter the DN of the
template in the Template DN field. Click Browse to locate the DN on the local server. This
will be an exact DN, such as cn=CoS template,ou=People,dc=example,dc=com.
• Using the value of one of the target entry's attribute
To have the template entry identified by the value of one of the target entry's attributes
(an indirect CoS), enter the attribute name in the Attribute Name field. Click Change to
select a different attribute from the list of available attributes.
• Using both its DN and the value of one of the target entry's attributes
To have the template entry identified by both its DN and the value of one of the target
entry's attributes (a classic CoS), enter both a template DN and an attribute name. The
template DN in a classic CoS is more general than for a pointer CoS; it references the
suffix or subsuffix where the template entries will be. There can be more than one template
for a classic CoS.
8. Click OK.
5.2.2.2 Creating the CoS template entry
For a pointer CoS or a classic CoS, there must be a template entry, according to the template DN
set when the class of service was created. Although the template entries can be placed anywhere
in the directory as long as the cosTemplateDn attribute reflects that DN, it is best to place the
template entries under the CoS itself.
For a pointer CoS, make sure that this entry reflects the exact DN given when the CoS was created.
For a classic CoS, the template DN should be recursive, pointing back to the CoS entry itself as
the base suffix for the template.
196 Organizing Entries with roles, Class of service, and Views