HP-UX Directory Server 8.1 deployment guide

Table 3-2 Data mapped to default directory schema (continued)
AttributeObject ClassOwnerData
homePhoneinetOrgPersonHRHome phone number
localityNameinetOrgPersonISEmployee location
telephoneNumberpersonFacilitiesOffice phone number
In Table 3-2 “Data mapped to default directory schema”, the employee name describes a person.
In the default directory schema, there is a person object class, which inherits from the top object
class. This object class allows several attributes, one of which is the cn or commonName attribute
to describe the full name of the person. This attribute makes the best match for containing the
employee name data.
The user password also describes an aspect of the person object class, and the userPassword
attribute is listed in the allowed attributes for the person object class.
The home phone number describes an aspect of a person; however, there is not a related attribute
in the list associated with the person object class. The home phone number describes an aspect
of a person in an organization's enterprise network. This object corresponds to the
inetOrgPerson object class in the directory schema. The inetOrgPerson object class inherits
from the organizationPerson object class, which in turn inherits from the person object
class. Among the inetOrgPerson object's allowed attributes is the homePhone attribute, which
is appropriate for containing the employee's home telephone number.
NOTE:
The Directory Server Schema Reference is invaluable for determining what attributes are available
for your data. Each attribute is listed with object classes which accept it, and each object class is
cross-listed with required and allowed attributes.
3.4 Customizing the schema
The standard schema can be extended if it is too limited for the directory needs. The Directory
Server Console can be used to extend the schema by easily adding attributes and object classes.
It is also possible to create an LDIF file and add schema elements manually. For more information,
see the HP-UX Directory Server administrator guide.
Keep the following rules in mind when customizing the Directory Server schema:
• Keep the schema as simple as possible.
• Reuse existing schema elements whenever possible.
• Minimize the number of mandatory attributes defined for each object class.
• Do not define more than one object class or attribute for the same purpose (data).
• Do not modify any existing definitions of attributes or object classes.
NOTE:
When customizing the schema, never delete or replace the standard schema. Doing so can lead
to compatibility problems with other directories or other LDAP client applications.
Custom object classes and attributes are defined in the 99user.ldif file. Each individual
instance maintains its own 99user.ldif file in the
/etc/opt/dirsrv/slapd-instance_name/schema directory. It is also possible to create
custom schema files and dynamically reload the schema into the server.
3.4 Customizing the schema 31