Creating Custom Schema Files - Netscape DIRECTORY SERVER 6.02 - DEPLOYMENT Deployment Manual

However, if you extend the schema and find you do not use the new elements, feel
free to delete the elements you don't use. Before removing the object class
definitions from the schema, you need to modify each entry using the object class.
Otherwise, if you remove the definition first, you might not be able to modify the
entries that use the object class afterwards. Schema checks on modified entries will
also fail unless you remove the unknown object class values from the entry.

Creating Custom Schema Files

You can create custom schema files other than the
Directory Server. However, your custom schema files should not be numerically or
alphabetically higher than
The file contains attributes with the an
99user.ldif
. If you create a schema file called
defined'
the schema using LDAP or the Directory Server Console, all of the attributes with
an value of
X-ORIGIN
directory writes them to
sequenced file (numerically, then alphabetically) for its internal schema
management. The result is two LDIF files that contain duplicate information and
some information in the
When naming custom schema files, name them as follows:
[00-99] yourname .ldif
The directory loads these schema files in numerical order, followed by alphabetical
order. For this reason, you should use a number scheme that is higher than any
directory standard schema defined. For example,
creates a new schema file named
file something lower than the standard schema files, the server may encounter
errors when loading the schema. In addition, all standard attributes and object
classes will be loaded only after your custom schema elements have been loaded.
You should not use
'user defined'
files as
'user defined'
over LDAP. Use something more descriptive, such as
.
defined'
After you have created custom schema files, you can either:
• Manually copy these custom schema files to all of your servers, which requires
a restart of each server.
or the server could experience problems.
99user.ldif
will be written to
'user defined'
because the directory uses the highest
99zzz.ldif
file might be erased.
99zzz.ldif
60examplecorp.ldif
in the
is used internally by the directory when schema is added
file provided with
99user.ldif
of
X-ORIGIN
, the next time you update
99zzz.ldif
99zzz.ldif
Corporation
example.com
. If you name your schema
field of your custom schema
X-ORIGIN
'example.com Corporation
Chapter 3 How to Design the Schema
Customizing the Schema
'user
. The
51