Table of Contents
Advertisement
Customizing the Schema
•
Single object classes simplify data design when you have data that you want
to put on more than one type of object class structure.
For example, suppose you want
entry. You may want to create only a single object class to allow this attribute.
•
Avoid required attributes for new object classes.
Requiring attributes can make your schema inflexible. When creating a new
object class, allow rather than require attributes.
After defining a new object class, you need to decide what attributes it allows and
requires and from what object class(es) it inherits.
Strategies for Defining New Attributes
Add new attributes and new object classes when the existing object classes do not
support all of the information you need to store in a directory entry.
Try to use standard attributes whenever possible. Search the attributes that
already exist in the default directory schema and use them in association with a
new object class. Create a new attribute if you cannot find a match in the default
directory schema.
For example, you may find that you want to store more information on a person
entry than the
support. If you want to store the birth dates in your directory, no attribute exists
within the standard Directory Server schema. You can choose to create a new
attribute called
representing people by defining a new auxiliary class,
allows this attribute.
Deleting Schema Elements
Do not delete the schema elements shipped with Directory Server. Unused
schema elements represent no operational or administrative overhead. By
deleting parts of the standard LDAP schema, you may run into compatibility
problems with future installations of Directory Server and other
directory-enabled applications.
50
Netscape Directory Server Deployment Guide • October 2004
,
person
organizationalPerson
and allow this attribute to be used on entries
dateOfBirth
on both a person and a group
preferredOS
, or
inetOrgPerson
examplePerson
object classes
, which
Advertisement
Table of Contents
