LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

Operations Performed by the Schema Extension Utility
The schema extension utility, ldapschema, supports the following two modes of operation:
1. Query Schema Status
Based on the set of attribute types and object classes defined in the input schema definition
file, this tool queries their status on the directory server schema without applying any changes
to the LDAP directory server. ldapschema checks if new attribute types and object classes
specified in the input schema file are already defined on the directory server. This tool also
determines if definitions installed on the LDAP directory server match definitions specified
in the schema file being queried.
2. Extend a Directory Server with Schema Definitions
This utility supports the extend mode of operation. It can add attribute types and object
classes defined in the input schema file that are not yet installed on the LDAP server to that
server's schema. Only new valid attribute types and object classes can be added to the LDAP
server schema. To execute the ldapschema utility in the extend mode, most LDAP directory
servers require specifying the distinguished name and password of an administrator who
has permissions to modify the schema on that server.
DTD and XML Files Used by ldapschema
The ldspschema tool uses the following XML files to perform its operations:
• LDAP Schema Definition Files
This tool queries and extends the LDAP directory server schema with the input schema
definitions stored in an XML schema definition file. Several predefined files (such as
rfc3712.xml and 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. The file
name is passed to the tool as one of the required arguments. See the “Schema Definition
File” (page 164) section for details.
• Documentation Type Definition (DTD) Template
LDAP-UX provides the predefined Document Type Definition template,
/etc/opt/ldapux/schema/schema.dtd. Each schema definition file must adhere to
DTD template specified in /etc/opt/ldapux/schema/schema.dtd file. Every XML file
used by the ldapscheam utility must include /etc/opt/ldapux/schema/schema.dtd
as its DTD. This DTD file is used by ldapschema to validate new attribute types and object
classes before they can be added to the LDAP directory server. See the “Schema Definition
File” (page 164) section for details.
WARNING! Do not modify the schema.dtd file, or create your own DTD template file.
Modifying this file will cause ldapschema to fail.
• Supported Matching Rules and Syntaxes File
The ldapschema utility performs LDAP directory server schema search to obtain the
complete list of schema syntaxes and matching rules that the Directory Server supports.
Netscape/Red Hat Directory Server provides a list of supported matching rules and syntaxes
as part of the schema search.
However, some directory servers (such as Windows Active Directory Server) do not provide
a list of supported syntaxes and/or matching rules as part of the directory server schema
search. To support Windows ADS, LDAP-UX provides the predefined LDAP directory
server definition file, /etc/opt/ldapux/schema/schema-ads.xml, which contains a
list of schema syntaxes that Windows Active Directory Server supports.
If you choose to use the ldapschema tool with the directory server other than Netscape/Red
Hat Directory Server or Windows Active Directory Server, and the LDAP directory server
doesn't provide a list of supported matching rules and syntaxes as part of the directory
server schema search. Then, you need to define your own supported matching rules and
syntaxes file. See the “LDAP Directory Server Definition File” section for detailed information
158 Command, Tool, Schema Extension Utility, and Migration Script Reference