LDAP-UX Client Services B.04.15 Administrator's Guide

6.5.4 Schema Definition File
The ldapschema utility queries and extends LDAP directory server based on the XML schema
definition file. When using the ldapschema tool, the schema argument used with the -q or -e
option must correspond to the XML file containing the appropriate schema definition.
Several predefined files (such as rfc3712.xml, rfc2256.xml, etc...) are stored in the /etc/
opt/ldapux/schema directory. But the schema definition file can be stored in any directory
with any file name.
Each schema definition file must adhere to Document Type Definition (DTD) template specified
in /etc/opt/ldapux/schema/schema.dtd file. Every XML file used by the ldapschema
utility must include /etc/opt/ldapux/schema/schema.dtd as its DTD. See Line 2 in the
“A Sample RFC3712.xml File ” (page 210) section below.
WARNING! Every XML file used with ldapschema utility must include /etc/opt/ldapux/
schema/schema.dtd file as its DTD template. Do not modify this file, or create your own DTD
template file. The /etc/opt/ldapux/schema/schema.dtd file is created to validate attribute
type and object class definitions before they can be added to the LDAP directory server schema.
Altering the format of any schema elements in this file will cause ldapschema to fail.
The schema definition file, enclosed by <schemaDefinition> tags, specifies schema name,
schema description and schema source, followed by any number of attribute type and object
class definitions. The schema name, schema description and schema source XML tags
are optional.
The following describes the schemaName, schemaDescription, and schemaSource tags:
<schemaName>
Optional, specifies the name of schema definition file.
<schemaDescription>
Optional, contains a brief one line schema description.
<schemaSource> An optional field used to specify the X-ORIGIN field of extended
attribute types and object classes, if used.
In the schema definition file, after general schema information is specified, attribute type
definitions, if any, must be specified followed by any object class definitions.
6.5 Schema Extension Utility 209