Package com.novell.service.bindery

Provides contexts that implement the behavior of the NetWare 3.x bindery, such as creating, deleting and renaming Bindery objects and references to servers and trees, and discovering and accessing the objects present in the bindery.

See:
Description

Class Summary

BinderyDirContext	Implements the JNDI DirContext interface (via the AtomicDirContext).
BinderyEnvironment	Defines the set of constant Strings that uniquely controls the behavior of the Bindery name provider.
BinderyObjectDirContext	Represents an individual object found in the NetWare bindery.
BinderyPropertyAttrVal	Holds all the information found in a Bindery Property.
BinderyPropertyDataSegment	Holds a 128-byte data segment containing the data of a Bindery Property.
BinderyUtil	Defines a number of constants for use with the Bindery.
QueueBinderyObjectDirContext	Represents a bindery object that is a queue.
ServerBinderyObjectDirContext	Represents a bindery object that is a server.
TreeBinderyObjectDirContext	Represents a bindery object that is an NDS tree.

Package com.novell.service.bindery Description

Provides contexts that implement the behavior of the NetWare 3.x bindery, such as creating, deleting and renaming Bindery objects and references to servers and trees, and discovering and accessing the objects present in the bindery.

NetWare 3.x servers use the bindery database to identify and store information about network objects. The Bindery provider allows applications to read and modify standard information stored in the bindery and to create and manage their own object data.

The NetWare 4.0 OS replaced the bindery with NDS (an object database), which offers many advantages over the bindery, including a hierarchical structure and global naming. However, to maintain compatibility with bindery-based servers and to work effectively with such NetWare features as file trustee rights, NDS provides built-in bindery context. This is provided by a bindery-like database maintained by NDS for objects contained in the local directory partitions of a server.

NDS generates object IDs and makes them available to bindery clients using the local file system, queue management system, and other bindery-oriented services. These values are dynamic, not remaining consistent over time; however, NDS object IDs and the object IDs returned by Bindery are the same.

Some of the objects within a server's bindery represent links to objects that are contained in other name spaces (such as servers, trees, and queues). Instances of these objects will support federation to their appropriate name spaces.

The bindery serves many purposes, some of which are the following:

• Identifying users of the file system, which is done through login control and file trustee rights. Users, user groups, print servers, and other objects that require access to the NetWare file system must be represented in the bindery.
• Advertising services and circulating their network addresses to NetWare servers and other network services.
• Storing application-specific data. For example, applications often use the bindery to maintain lists of users that can access the application services.

Package Specification

(none)

Related Documentation

The following classes are used by the Bindery classes.

• com.novell.service.session.Session Interface
• javax.naming.directory.DirContext Interface

For overviews, concepts, sample code and demos, and tasks documentation, please see:

• NJCL Developer's Guide Documentation