LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

9.5.4.5 Object class definition requirements
To add the new schema to the LDAP directory server, each object class definition must meet the
following requirements:
• The object class definition contains a <oid> tag with one numeric id value which adheres to
RFC 2252 format specification.
• The object class definition has at least one <name> tag with the object class name. Each name
must adhere to RFC 2252 format specification.
• No other object classes in the schema definition file or on the LDAP directory server have the
same numeric id value.
• No other object classes in the schema definition file or on the LDAP directory server have the
same name value.
• The super-class(es) used by the object class must be defined.
• The attributes used by the object classes must be defined.
• The inheritance hierarchy has no cycles (no circular dependencies exist in the super-class and
sub-class relationships).
• An ABSTRACT object class can specify only ABSTRACT object class(es) as its super-class(es).
• An AUXILIARY object class can specify ABSTRACT or AUXILIARY object class(es) as its
super-class(es).
• A STRUCTURAL object class can specify ABSTRACT or STRUCTURAL object class(es) as its
super-class(es).
9.5.4.6 Predefined schema definition files
The following LDAP schema definition files are delivered with the LDAP-UX product:
• /etc/opt/ldapux/schema/rfc2256.xml
• /etc/opt/ldapux/schema/rfc2307.xml
• /etc/opt/ldapux/schema/rfc2307–bis.xml
• /etc/opt/ldapux/schema/rfc2926.xml
• /etc/opt/ldapux/schema/rfc3712.xml
These files are provided as examples to demonstrate how to define new LDAP schema definition
files to use with the ldapschema utility. Since these files define attribute types and object classes
that come preinstalled on most LDAP directory servers they are not intended for extending the LDAP
directory server schema. Instead, these files are provided for reference when creating the new
schema definition files to query and extend the LDAP directory server schema with the new attribute
type and object class definitions.
9.5.5 Defining directory-specific information
Attribute type and object class definitions can be extended with directory-specific information using
the <dsSpecific> tag. This is useful to maintain a single schema definition file for different types
and versions of LDAP directory servers.
9.5.5.1 Example of defining directory-specific information in the attribute type definition
This section takes an example to illustrate how directory-specific information may be specified in
a single attribute type definition to support HP-UX Directory Server, Red Hat Directory Server, and
Windows Active Directory Server definitions simultaneously.
The following is an example of the attribute type definition with directory-specific information using
the <dsSpecific> tag:
9.5 Schema extension utility 369