View Source

h3.Definition: Subschema Subentry

A subschema subentry is a special entry within the Directory Server that provides information about the [schema|Definition -- Schema] elements defined in the server. Attributes in this entry include:

* {{ldapSyntaxes}} -- The set of [attribute syntaxes|Definition -- Attribute Syntax] defined in the server schema.
* {{matchingRules}} -- The set of [matching rules|Definition -- Matching Rule] defined in the server schema.
* {{matchingRuleUse}} -- The set of [matching rule uses|Definition -- Matching Rule Use] defined in the server schema.
* {{attributeTypes}} -- The set of [attribute types|Definition -- Attribute Type] defined in the server schema.
* {{objectClasses}} -- The set of [object classes|Definition -- Object Class] defined in the server schema.
* {{nameForms}} -- The set of [name forms|Definition -- Name Form] defined in the server schema.
* {{dITContentRules}} -- The set of [DIT content rules|Definition -- DIT Content Rule] defined in the server schema.
* {{dITStructureRules}} -- The set of [DIT structure rules|Definition -- DIT Structure Rule] defined in the server schema.

Note that all of these are [operational attributes|Definition -- Operational Attribute] and therefore will not be returned unless explicitly requested.

Also note that it is technically possible for directory servers to have multiple subschema subentries with different sets of schema definitions that govern different portions of the [DIT|Definition -- Directory Information Tree]. The schema that applies to any given entry may be determined by retrieving the {{subschemaSubentry}} [virtual attribute|Definition -- Virtual Attribute] from that entry. Sun OpenDS SE currently supports only a single schema, and by default publishes that schema at "cn=schema".

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact