HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

l
ldapschema(1) ldapschema(1)
ldapschema -q /etc/opt/ldapux/schema/rfc3712.xml -T rhds -V 7.1
Note that LDAP directory server version number bears no effect unless also specified in the XML files being
processed. Version specification must follow the same format as version specification used in the
/etc/opt/ldapux/schema/rfc3712.xml
and /etc/opt/ldapux/schema/map-
rules.xml
files.
To extend Windows 2000 Active Directory Server with custom
SampleA schema, follow the following pro-
cedure:
1. Create schema definition file containing attribute type and object class definitions for
SampleA
schema
(that is,
/etc/opt/ldapux/schema/sampleA.xml
).
2. Recommended : Query the current status of
SampleA schema on the server:
ldapschema -q /etc/opt/ldapux/schema/sampleA.xml -T ads -V 2000
-D "<binddn>" -j /tmp/secret.txt
3. Based on the results produced by Step 2, correct any invalid definitions.
4. Extend the Active Directory Server schema with new
SampleA schema elements by executing the fol-
lowing command:
ldapschema -e /etc/opt/ldapux/schema/sampleA.xml -T ads -V 2000
-D "<binddn>" -j /tmp/secret.txt
Note that LDAP directory server version number bears no effect unless also specified in the XML files being
processed. Version specification must follow the same format as version specification used in the
/etc/opt/ldapux/schema/sampleA.xml
, /etc/opt/ldapux/schema/schema-ads.xml
,
and
/etc/opt/ldapux/schema/map-rules.xml
files.
RETURN VALUES
The
ldapschema utility returns the following values:
0 Successful completion.
1 Failure.
In addition, ldapschema prints to STDOUT the overall status of the schema being queried or extended.
Based on the schema status, any combination of the following messages is displayed. Detailed explanations
of each message are specified in the square brackets following the message body text.
Schema Status Messages
SCHEMA_NEW: file "<schema>" contains attribute types and object classes that are not defined in the
LDAP server schema.
[The SCHEMA_NEW message indicates all attribute types and object classes defined in the <schema> file
are new to the LDAP directory server. The
SCHEMA_NEW message indicates none of the specified
definitions are currently installed in the LDAP server schema.]
----------------------------------------------------------------------
SCHEMA_EXISTS:
All attribute types and object classes defined in file "<schema>" are already part of the
LDAP server schema.
[The SCHEMA_EXISTS message indicates the schema specified in the <schema> file is already installed on
the LDAP directory server. All attribute types and object classes defined in the <schema> file are already
part of the schema on the LDAP directory server. Only attribute types and object classes with new and
unique numeric oids and names can be added to the LDAP server schema. Check the messages containing
ATTRIB_FOUND and OBJECT_FOUND described below for details. Since the definitions specified in the
<schema> file are already installed in the LDAP server schema, the ldapschema utility will make no
changes to the LDAP directory server schema.]
----------------------------------------------------------------------
SCHEMA_FOUND: subset of attribute types and/or object classes defined in file "<schema>" are already
part of the LDAP server schema.
[The
SCHEMA_FOUND message indicates one or more attribute type or object class definitions specified in
the <schema> file are already installed in the LDAP server schema. Such elements will be excluded from
being extended on the LDAP server. Only attribute types and object classes with new and unique numeric
556 Hewlett-Packard Company − 12 − HP-UX 11i Version 2: December 2007 Update