Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual page 73

Table of Contents

Advertisement

generate the attribute dynamically. The
stored in one place, and each entry points to that place to give a value to their fax
number attribute. For the application, these attributes appear just like all other
attributes, despite that they are not actually stored on the entries themselves.
Each CoS is comprised of the following entries in your directory:
CoS Definition Entry—The CoS definition entry identifies the type of CoS you
are using. It is stored as an LDAP subentry below the branch it affects.
Template Entry—The template entry contains a list of the shared attribute
values. Changes to the template entry attribute values are automatically
applied to all the entries sharing the attribute.
The CoS definition entry and the template entry interact to provide attribute values
to their target entries, the entries within their scope. The value they provide
depends upon the following:
The entry's DN (different portions of the directory tree might contain different
CoS).
A service class attribute value stored with the entry.
The absence of a service class attribute can imply a specific default CoS.
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.
You can use different types of CoS depending upon how you want the value of
your dynamic attributes to be generated. There are three types of CoS:
Pointer CoS—A 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—An 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.
facsimileTelephoneNumber
Chapter 4
Designing the Directory Tree
Grouping Directory Entries
attribute is
73

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 6.01

Table of Contents