Versions of NetWare prior to the release of 4.0 used a flat database structure called the bindery to manage users, server volumes , and resources on the network. Each NetWare server had its own bindery (not unlike a Windows NT domain), making it more difficult for users to access resources on different network servers. As already mentioned, with the release of version 4.0, a hierarchical database called the Novell Directory Services (NDS) provided a tree structure that allowed for the integration of all network resources and objects into one branching structure.
Versions 4 and 5 of NetWare embraced NDS. With the release of NetWare 6, Novell has upgraded the directory service to the eDirectory; eDirectory is similar to NDS in that a branching hierarchy is used to hold objects that make up the network entities. Network trees, servers, users, groups, and other objects reside in this branching structure.
The eDirectory consists of a database, which identifies objects in the database through the use of a schema (which is really just a scheme for differentiating between objects such as servers and users; Figure 8.1 shows a lists of object definitions in the Schema Manager). The eDirectory is synchronized among the different branches in the eDirectory tree, making it easy to find resources anywhere on the network.
Figure 8.1. The schema is the defining element for the objects that can exist in the network hierarchy.
The eDirectory tree has a root, which is created when you configure the first NetWare server for the network. Additional servers, providing additional resources, can be added to the eDirectory tree as branches. Figure 8.2 shows the eDirectory tree for a NetWare network as seen in the ConsoleOne management tool.
Figure 8.2. The eDirectory tree holds the objects that make up the network.
When you create the root of the eDirectory tree, you must supply a name for the tree (in this example, the tree is called popeye). You must also create a context for the network tree when you create the root. The context describes the position of an object within the eDirectory tree. The context for the tree in Figure 8.1 is "habraken." The context of the tree might typically be specified by the name of your company. We will discuss the creation of the root in the next section of this chapter.