Netscape NETSCAPE DIRECTORY SERVER 6.1 - ADMINISTRATOR, Administrator'S Manual

Page: 191 / 578

Assigning Class of Service
Chapter 5 Advanced Entry Management 191
Next, you create the template entries for the sales and marketing departments as
follows:
dn: cn=sales,cn=exampleUS,cn=data,dc=example,dc=com
objectclass: top
objectclass: LDAPsubentry
objectclass: extensibleobject
objectclass: cosTemplate
postalCode: 44438
dn: cn=marketing,cn=exampleUS,cn=data,dc=example,dc=com
objectclass: top
objectclass: LDAPsubentry
objectclass: extensibleobject
objectclass: cosTemplate
postalCode: 99111
The classic CoS definition entry applies to all entries under the
dc=example,dc=com
suffix. Depending upon the combination of
employeeType
attribute found in the entry and the cosTemplate DN, it can arrive at one of two
templates. One, the sales template, provides a postal code specific to employees in
the sales department. The marketing template provides a postal code specific to
employees in the marketing department.
Creating Role-Based Attributes
You can create classic CoS schemes that generate attribute values for an entry
based on the role possessed by the entry. For example, you could use role-based
attributes to set the server look through limit on an entry-by-entry basis.
To create a role-based attribute, use the
nsRole
attribute as the
cosSpecifier
in
the CoS definition entry of a classic CoS. Because the
nsRole
attribute can be
multivalued, you can define CoS schemes that have more than one possible
template entry. To resolve the ambiguity of which template entry to use, you can
include the
cosPriority
attribute in your CoS template entry.
For example, you can create a CoS that allows members of the manager role to
exceed the standard mailbox quota. The manager role exists as follows:
dn: cn=ManagerRole,ou=people,dc=example,dc=com
objectclass: top
objectclass: LDAPsubentry
objectclass: nsRoleDefinition
objectclass: nsComplexRoleDefinition