Managing CoS from the Command-Line

to be returned. When operational is used as a qualifier, it works as if override and operational were specified.

NOTE

An attribute can only be made operational if it is also defined as operational in the schema. For example, if the CoS generates a value for the description attribute, it is not possible to use the operational qualifier because this attribute is not marked operational in the schema.

Operational-default.This qualifier indicates that the server only returns a generated value if there is no corresponding attribute value stored with the entry and if it is explicitly requested in the search.

If no qualifier is set, default is assumed.

For example, a pointer CoS definition entry that contains an override qualifier is created as follows:

dn: cn=pointerCoS,dc=example,dc=com

objectclass: top

objectclass: cosSuperDefinition

objectclass: cosPointerDefinition

cosTemplateDn: cn=exampleUS,ou=data,dc=example,dc=com

cosAttribute: postalCode override

This pointer CoS definition entry indicates that it is associated with a template entry, cn=exampleUS,ou=data,dc=example,dc=com, that generates the value of the postalCode attribute. The override qualifier indicates that this value will take precedence over the value stored by the entries for the postalCode attribute.

NOTE

If an entry contains an attribute value generated by a CoS, the value of the attribute cannot be manually updated if it is defined with the operational or override qualifiers.

For more information about the attributes, refer to the Directory Server Configuration, Command, and File Reference.

Table 5.4, “CoS Definitions” describes the CoS definition for each type of CoS.

155

Page 175
Image 175
HP UX Red Hat Direry Server Software manual Managing CoS from the Command-Line