96 lines
5.4 KiB
HTML
96 lines
5.4 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow"/>
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<title>Directory Server (LDAP) - Object classes</title>
|
||
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
</head>
|
||
|
<body>
|
||
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
||
|
|
||
|
<a name="rzahyobjectclass"></a>
|
||
|
<h3 id="rzahyobjectclass">Object classes</h3>
|
||
|
<p>An object class specifies a set of attributes used to describe an object.
|
||
|
For example, if you created the object class <span class="bold">tempEmployee</span>, it could contain attributes associated with a temporary employee such
|
||
|
as, <span class="bold">idNumber</span>, <span class="bold">dateOfHire</span>, or <span class="bold">assignmentLength</span>. You
|
||
|
can add custom object classes to suit the needs of your organization. The
|
||
|
IBM Directory Server schema provides some basic types of object classes, including: </p>
|
||
|
<ul>
|
||
|
<li>Groups</li>
|
||
|
<li>Locations</li>
|
||
|
<li>Organizations</li>
|
||
|
<li>People</li></ul>
|
||
|
<a name="wq10"></a>
|
||
|
<div class="notetitle" id="wq10">Note:</div>
|
||
|
<div class="notebody">Object classes that are specific
|
||
|
to the Directory Server have the prefix 'ibm-'.</div>
|
||
|
<p>Object classes are defined by the characteristics of type, inheritance,
|
||
|
and attributes.</p>
|
||
|
<p><span class="bold">Object class type</span></p>
|
||
|
<p>An object class can be one of three types:</p>
|
||
|
<dl>
|
||
|
<dt class="bold">Structural:</dt>
|
||
|
<dd>Every entry must belong to one and only one structural object class,
|
||
|
which defines the base contents of the entry. This object class represents
|
||
|
a real world object. Because all entries must belong to a structural object
|
||
|
class, this is the most common type of object class.
|
||
|
</dd>
|
||
|
<dt class="bold">Abstract: </dt>
|
||
|
<dd>This type is used as a superclass or template for other (structural)
|
||
|
object classes. It defines a set of attributes that are common to a set of
|
||
|
structural object classes. These object classes, if defined as subclasses
|
||
|
of the abstract class, inherit the defined attributes. The attributes do not
|
||
|
need to be defined for each of the subordinate object classes.
|
||
|
</dd>
|
||
|
<dt class="bold">Auxiliary: </dt>
|
||
|
<dd>This type indicates additional attributes that can be associated with
|
||
|
an entry belonging to a particular structural object class. Although an entry
|
||
|
can belong to only a single structural object class, it might belong to multiple
|
||
|
auxiliary object classes.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p><span class="bold">Object Class Inheritance </span></p>
|
||
|
<p>This version of the Directory Server supports object inheritance for object
|
||
|
class and attribute definitions. A new object class can be defined with parent
|
||
|
classes (multiple inheritance) and the additional or changed attributes.</p>
|
||
|
<p>Each entry is assigned to a single structural object class. All object
|
||
|
classes inherit from the abstract object class <span class="bold">top</span>. They can also inherit from other object classes. The object class
|
||
|
structure determines the list of required and allowed attributes for a particular
|
||
|
entry. Object class inheritance depends on the sequence of object class definitions.
|
||
|
An object class can only inherit from object classes that precede it. For
|
||
|
example, the object class structure for a person entry might be defined in
|
||
|
the LDIF file as: </p>
|
||
|
<pre class="xmp">objectClass: top
|
||
|
objectClass: person
|
||
|
objectClass: organizationalPerson
|
||
|
</pre><p class="indatacontent"> In this structure, the organizationalPerson inherits from the person
|
||
|
and the top object classes, while person object class only inherits from the
|
||
|
top object class. Therefore, when you assign the organizationalPerson object
|
||
|
class to an entry, it automatically inherits the required and allowed attributes
|
||
|
from the superior object class (in this case, the person object class).</p>
|
||
|
<p>Schema update operations are checked against the schema class hierarchy
|
||
|
for consistency before being processed and committed.</p>
|
||
|
<p><span class="bold">Attributes</span></p>
|
||
|
<p>Every object class includes a number of required attributes and optional
|
||
|
attributes. Required attributes are the attributes that must be present in
|
||
|
entries using the object class. Optional attributes are the attributes that
|
||
|
can be present in entries using the object class.</p>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|