Netscape Standard Schema
•
Extending the standard Directory Server schema to define new elements to
meet your remaining needs.
•
Planning for schema maintenance.
It is best to use existing schema elements defined in the standard schema provided
with Directory Server. Choosing standard schema elements helps ensure
compatibility with directory-enabled applications. In addition, as the schema is
based on the LDAP standard, you are assured it has been reviewed and agreed to
by a wide number of directory users.
Netscape Standard Schema
Your directory schema maintain the integrity of the data stored in your directory
by imposing constraints on the size, range, and format of data values. You decide
what types of entries your directory contains (people, devices, organizations, and
so forth) and the attributes available to each entry.
The predefined schema included with Directory Server contains both the
standard LDAP schema as well as additional application-specific schema to
support the features of the server. While this schema meets most directory
needs, you may need to extend it with new object classes and attributes to
accommodate the unique needs of your directory. Refer to "Customizing the
Schema" for information on extending the schema.
The following sections describe the format, standard attributes, and object classes
included in the Netscape standard schema.
Schema Format
Directory Server bases its schema format on version 3 of the LDAP protocol
(LDAPv3). This protocol requires directory servers to publish their schemas
through LDAP itself, allowing directory client applications to programmatically
retrieve the schema and adapt their behavior based on it. The global set of schema
for Directory Server can be found in the entry named
40
Netscape Directory Server Deployment Guide • December 2003
.
cn=schema
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 - DEPLOYMENT and is the answer not in the manual?
Questions and answers