Custom Schema Best Practices - Netscape DIRECTORY SERVER 7.0 - DEPLOYMENT Deployment Manual

Customizing the Schema
• Allow the replication process to replicate this information to each of the
consumers for you.
If you do not copy these custom schema files to all of your servers, the schema
information will only be replicated to the consumer when changes are made to the
schema on the supplier using LDAP or the Directory Server Console.
When the schema definitions are then replicated to a consumer server where they
do not already exist, they will be stored in the
does not track where schema definitions are stored. Storing schema elements in
the
99user.ldif
maintain your schema on the supplier server only.
If you copy your custom schema files to each server, changes to the schema files
must be copied again to each server. If you do not copy them again, it is possible
the changes will be replicated and stored in the
consumer. Having the changes in the
management difficult, as some attributes will appear in two separate schema files
on a consumer, once in the original custom schema file you copied from the
supplier and again in the
For more information about replicating schema, see "Schema Replication," on
page 131.

Custom Schema Best Practices

Consider the following points when creating custom schema elements:
• If you manage your schema using LDAP or the Directory Server Console, add
all of your schema definitions to the
duplication of schema elements in multiple files. Schema elements added and
updated via LDAP are automatically written to the
If you define custom schema files, for example,
then update these schema elements using LDAP, the new definitions will be
written to the
overriding your original custom schema definition. For example, changes to
60examplecorp.ldif
99user.ldif
• If adding schema elements to the
X-ORIGIN
defined'
will add the
in addition to what you have already specified for the
52 Netscape Directory Server Deployment Guide • October 2004
file of consumers does not create a problem as long as you
99user.ldif
file and not to your custom schema file, thus
99user.ldif
will be overwritten by the definitions stored in
.
of value
'user defined'
, when the server loads the schema from the
value to the
'user defined'
99user.ldif
99user.ldif
file may make schema
99user.ldif
file after replication.
file to avoid possible
99user.ldif
99user.ldif
60examplecorp.ldif
manually, always use an
99user.ldif
. If you use something other than
portion of the definition
X-ORIGIN
X-ORIGIN
file. The directory
file on the
file.
, and
'user
file, it
99user.ldif
. The result is