Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
Configuring
Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
Configuring directory services
This section describes how to plan, set up, and use IBM® Domino® directory services.
LDAP schema
A directory entry contains information about a particular entity, or object -- for example, a person or a group -- and is associated with a distinguished name. An LDAP schema is a set of rules that define what can be stored as entries in an LDAP directory. Each LDAP directory has a default schema, which organizations can customize, or "extend," by adding elements to it. The elements of a schema are attributes, syntaxes, and object classes. LDAP directory servers provide the ability to enforce the schema to ensure that directory changes made using LDAP operations conform to it.
The Domino® LDAP schema
The default Domino® LDAP schema includes both Domino-specific and LDAP-standard elements.
displayName operational attribute
The attribute displayName, from the inetOrgPerson schema, has been implemented in the Domino® LDAP server to improve performance of name resolution queries from external LDAP servers.

displayName operational attribute

The attribute displayName, from the inetOrgPerson schema, has been implemented in the Domino® LDAP server to improve performance of name resolution queries from external LDAP servers.

The name for displayName is the user's abbreviated name. Thus, the displayName value for cn=John Doe,ou=Anytown,o=Renovations is John Doe/Anytown/Renovations.

Domino serves up displayName from the existing Person.DisplayName field. The latter is already included in the pubnames.ntf design, but its field properties reveal that it is computed for display.

Because the design of displayName is computed for display, it cannot be modified, so RELOADSCHEMA makes the inetOrgPerson displayName a no-user-modification (read-only) attribute.