Netscape Directory Server (Directory Server) comes with a standard schema that includes hundreds of object classes and attributes. While the standard object classes and attributes should meet most of your requirements, you may need to extend your schema by creating new object classes and attributes.
This chapter describes how to extend your schema in the following sections:
When you add new attributes to your schema, you must create a new object class to contain them. Although it may seem convenient to just add the attributes you need to an existing object class that already contains most of the attributes you require, doing so compromises interoperability with LDAP clients.
Interoperability of Directory Server with existing LDAP clients relies on the standard LDAP schema. If you change the standard schema, you will also have difficulties when upgrading your server. For the same reasons, you cannot delete standard schema elements.
For more information on object classes, attributes, and the directory schema, as well as guidelines for extending your schema, refer to Netscape Directory Server Deployment Guide. For information on standard attributes and object classes, see the Netscape Directory Server Schema Reference.
To extend the directory schema, you should proceed in the following order:
Through Directory Server Console, you can view all attributes in your schema, and you can create, edit, and delete your attribute extensions to the schema. The following sections describe how to manage attributes:
For information on managing object classes, see Managing Object Classes.
To view information about all attributes that currently exist in your directory schema:
For information on the fields and lists in
the Attributes tab, refer to Table
9-1.
Table 9-1
Attributes Tab Reference
|
The object identifier of the attribute. An OID is a string, usually of dotted decimal numbers, that uniquely identifies an object, such as an object class or an attribute. If you do not specify an OID, the Directory Server automatically uses attribute_name-oid. For example, if you create the attribute birthdate without supplying an OID, the Directory Server automatically uses birthdate-oid as the OID. For more information about OIDs or to request a prefix for your enterprise, send mail to the IANA (Internet Assigned Number Authority) at iana@iana.org, or visit the IANA website at: http://www.iana.org/. |
|
Operational attributes are not returned as a result of an ldapsearch operation unless they are explicitly specified in the search. Generally, operational attributes are reserved for use by the Directory Server. |
|
|
If the attribute is multi-valued, an X appears in this column; otherwise, this field is blank. The Directory Server allows more than one instance of a multi-valued attribute per entry. |
You can use Directory Server Console to create new attributes. After adding new attributes to your schema, you must create a new object class to contain them. See Creating Object Classes for information.
You can only edit attributes you have created. You cannot edit standard attributes.
You can only delete attributes that you have created. You cannot delete standard attributes.
You can use Directory Server Console to manage your schema's object classes. Through the Console, you can view all of your schema's object classes and create, edit, and delete your object class extensions to the schema. The following sections describe how to manage object classes:
For information on managing attributes, see Managing Attributes.
To view information about all object classes that currently exist in your directory schema:
For information on the fields and lists in
the Object Classes tab, refer to Table 9-2.
|
The parent identifies the object class from which this object class inherits its attributes and structure. For example, the parent object for the inetOrgPerson object class is the organizationalPerson object. That means that an entry with the object class inetOrgPerson must also include the object class organizationalPerson. Typically, if you want to add new attributes for user entries, the parent would be the inetOrgPerson object class. If you want to add new attributes for corporate entries, the parent is usually organization or organizationalUnit. If you want to add new attributes for group entries, the parent is usually groupOfNames or groupOfUniqueNames. |
|
|
The object identifier of the object class. An OID is a string, usually of dotted decimal numbers, that uniquely identifies an object, such as an object class or an attribute. If you do not specify an OID, the Directory Server automatically uses ObjectClass_name-oid. For example, if you create the object class division without supplying an OID, the Directory Server automatically uses division-oid as the OID. For more information about OIDs or to request a prefix for your enterprise, send mail to the IANA (Internet Assigned Number Authority) at iana@iana.org, or visit the IANA website at: http://www.iana.org/ . |
|
|
This list contains all of the standard and user-defined object classes in the Directory Server schema. |
|
|
Contains a list of attributes that must be present in entries that use this object class. Includes inherited attributes. |
|
|
Contains a list of attributes that may be present in entries that use this object class. Includes inherited attributes. |
You create an object class by giving it a unique name, selecting a parent object for the new object class, and adding required and optional attributes.
You can use Directory Server Console to edit object classes that you previously created. You cannot edit a standard object class.
You can delete only object classes that you have created. You cannot delete standard object classes.
When schema checking is on, the Directory Server ensures that:
Schema checking is turned on by default in the Directory Server, and you should always run the Directory Server with schema checking turned on. The only case where you might want to turn schema checking off is to accelerate LDAP import operations. However, there is a risk of importing entries that do not conform to the schema. Consequently, it is impossible to search for these entries.
To turn schema checking on and off:
You can also turn
schema checking on and off by using the
nsslapd-schemacheck
attribute. For
information, see the Netscape
Directory
Server Configuration, Command, and File Reference.
| Previous |
Contents |
Index |
DocHome | Next |