Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 41 / 574

Understanding Novell eDirectory 41
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
1.3.7 Trailing Periods
Trailing periods can be used only in relative naming. Therefore, you can’t use both a leading period
and a trailing period. A trailing period changes the container that eDirectory resolves the name from.
Each trailing period changes the resolution point one container toward the top of the tree. For
example, suppose you want to change your workstation’s current context from Timmins to
Allentown in the example in
Figure 1-11 on page 41 .
Figure 1-11
Sample eDirectory Container
The proper CX command uses relative naming with trailing periods:
CX Allentown.East..
eDirectory interprets the command as “Change the context to Allentown, which is in East, resolved
from two containers up the tree from the current context.”
Similarly, if Bob is in the Allentown container and your workstation’s current context is Timmins,
then Bob’s relative name would be
Bob.Allentown.East..
1.3.8 Context and Naming on Linux and UNIX
When Linux and UNIX user accounts are migrated to eDirectory, the eDirectory context is not used
to name users.
1.4 Schema
Schema defines the types of objects that can be created in your tree (such as Users, Printers, and
Groups) and what information is required or optional at the time the object is created. Every object
has a defined schema class for that type of object.
The schema that originally shipped with the product is called the base schema. After the base
schema has been modified in any way—such as adding a new class or a new attribute—then it is
considered the extended schema.
You aren't required to extend the schema, but you have the ability to do so. The Schema role in
iManager lets you extend the schema to meet organizational needs. For example, you might want to
extend your schema if your organization requires special footwear for employees and you need to
keep track of employee shoe sizes. You might want to create a new attribute called Shoe Size and
then add it to the User class.
For more information, see Chapter 4, “Managing the Schema,” on page 117 .