If you want an instance to support custom object classes
and attributes, you must add a schema file that defines the custom
object classes and attributes.
You can use Configuration Tool or the command-line
utilities, such as idscfgsch or idsucfgsch,
to manage the schema files. The schema file must exist on the computer.
For more information about the idscfgsch command
or the idsucfgsch command, see Command Reference.
You must stop the directory server before you add or remove schema
files.
When you add or remove schema files, the configuration file of
the instance is updated. You can run the following schema management
operations:
- Add a schema file to the list of schema files that is loaded at
the server startup.
- Remove a schema file from the list of schema files that gets updated
at the server startup.
- Change the type of validation checking that is done for schema
files.
You cannot remove the following system-defined schema files:
- V3.config.at
- V3.config.oc
- V3.ibm.at
- V3.ibm.oc
- V3.system.at
- V3.system.oc
- V3.user.at
- V3.user.oc
- V3.ldapsyntaxes
- V3.matchingrules
- V3.modifiedschema
You can also use Configuration Tool to specify
the schema validation rule to check whether the entries meet the schema
rules. The default schema validation rule is Version 3 (Lenient).
The following schema validation rules are supported by a directory
server:
- Version 3 (Strict)
- The server runs LDAP version 3 strict validation check against
the entries. With this type of validation, all parent object classes
must be present when you add entries.
- Version 3 (Lenient)
- The server runs LDAP version 3 lenient validation check against
the entries. With this type of validation, all parent object classes
do not require to be present when you add entries. LDAP version 3
lenient is the default schema validation rule.
- Version 2
- The server runs LDAP version 2 check against the entries.
- None
- The server does not run validation check.