Maintaining Consistent Schema - Netscape DIRECTORY SERVER 7.0 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

that attributes that are not
section of the Directory Server Console, and you will not be able to use the
console to edit object classes that contain an
defined'
Using an
the
99user.ldif
does not remove them because it relies on an
what elements should reside in the
For example, you create a schema entry manually in
attributetypes: ( exampleContact-oid NAME 'exampleContact' DESC
1.3.6.1.4.1.1466.115.121.1.15
After the directory loads the schema entry, it appears as follows:
attributetypes: ( exampleContact-oid NAME 'exampleContact' DESC
1.3.6.1.4.1.1466.115.121.1.15
When adding new schema elements, all attributes need to be defined before
they can be used in an object class. You can define attributes and object classes
in the same schema file.
Each custom attribute or object class you create should be defined in only one
schema file. This prevents the server from overriding any previous definitions
when it loads the most recently created schema (as the server loads the schema
in numerical order first, then alphabetical order).

Maintaining Consistent Schema

A consistent schema within Directory Server aids LDAP client applications in
locating directory entries. If you use an inconsistent schema, then it becomes very
difficult to locate information in your directory tree efficiently.
Inconsistent schema use different attributes or formats to store the same
information. You can maintain schema consistency in the following ways:
Use schema checking to ensure attributes and object classes conform to the
schema rules.
Select and apply a consistent data format.
.
of value
X-ORIGIN
file are not removed from the file by the directory. The directory
'Example Corporate contact' SYNTAX
X-ORIGIN 'Example defined')
'Example Corporate contact' SYNTAX
X-ORIGIN ('Example defined' 'user defined') )
will appear in the read-only
'user defined'
X-ORIGIN
ensures that schema definitions in
'user defined'
X-ORIGIN
99user.ldif
Chapter 3
Maintaining Consistent Schema
other than
'user
of
'user defined'
file.
as follows:
99user.ldif
How to Design the Schema
to tell it
53

Advertisement

Table of Contents
loading

This manual is also suitable for:

Netscape directory server 7.0

Table of Contents