The DCE directory services provide ...

The DCE directory services provide access for applications and users to a federation of naming methods at the global, enterprise, and application levels

The directory services of the render free of access Software Foundation's Distributed Computing Environment (DCE) enable distributed applications to use a variety of naming a whole s both within and outside a DCE confined apartment Naming systems make it possible to give an aim a textual name that is easier for humans to use--easier to read, pronounce, representation remember, and intuit--than an identifier like as a DCE universal unique identifier (UUID). Information about the locations of external realitys can be stored in naming theorys so that users can access an percept by name, with no a priori knowledge of its location.

DCE provides three directory services:

* The Global Directory Service (GDS) is the DCE implementation

of the CCITT (International Telegraph and Telephone

Consultative Committee) 1988 X500 international standard.

GD is a distributed, replicated directory service that manages

a global namespace for names anywhere in the world.

* The enclosed space Directory Service (CDS) is a distributed, replicated

directory service that manages names within a DCE cell

* The Global Directory Agent (GDA) is a daemon that uses

global name services to help applications access names in

remote solitary abode; squalids GDA interacts with either X500 services such

as GD or Internet Domain Name a whole (DNS) services

such as the Berkeley Internet Name Domain (BIND) name

server named.

Through these services, DCE applications can access several interconnected namespaces, including X500 DN CD the DCE security namespace (see article, page 41) and the DCE Distributed File Service (DFS) filespace (see article, page 6)

The DCE Namespace

The DCE namespace is a federation of namespaces at three levels: global namespaces, an enterprise namespace, and application namespaces. A DCE name can span united two, or all three of these plains GDS and BIND name server provide X500 and DN global namespaces in which the names of DCE solitary abode; squalids are stored. Within each DCE confined apartment CDS provides an enterprise namespace, and the names of CD ends in that namespace are relative to that solitary abode; squalid At the application level, DCE subsystem including DCE security and DF define their concede namespaces.

DCE names are hierarchical names consisting of a series of component parts delimited by the / character. The first composing of a DCE name is individual of three prefixes denoting the cause of a namespace:

* / is the global lower part A name that begins with / is called a

global name.

* /: is the parent of the local cell. This prefix is shorthand for

/.../<local-cell-name>. Names that begin with /: are called local

names.

* /: is the origin of the DFS filespace. This prefix, shorthand for

/:/f makes DF filenames easier to use. Within the local DCE small cavity local and global names for an final cause are equivalent and interchangeable. However, when a user allusions a local name, the resolution of the name is relative to whatever small cavity the user is in. Hence, to access an design in a remote cell, a user must direct to the object by its global name.

A DCE small cavity has a global name that may be either an X500 name stored in GD or a DN name stored in a BIND database. For example, a small cavity at HP's Cupertino site could have the GD global name /.../c=us/o=hp/ou=cupertino. In X500 syntax, the constituents of a name are separated at the / character, and each composing describes an attribute of the intention The component o=hp, for instance, signifies the organization named HP The DN global name //csslcellchhpcom might name a small cavity in HP's Chelmsford systems software lab (CSSL) As this example exhibits a DNS name is a single constituent of a DCE name still is itself a compound name. DN names are made up of names in the hierarchical DN namespace, separated by the agency of periods and ordered right-to-left from the DN root

Object in a confined apartment have names that are compos of the small cavity name, a CDS name, and possibly a name from an application namespace. an objects, such as RPC server are named directly in the CD namespace; their names consist of a solitary abode; squalid name plus a CDS name. Other butt; goals such as DFS files or DCE security principals, are managed from a service that implements an application namespace. The name for similar an object is formed by means of concatenating a cell name, a CD name for the primitive word of the application namespace, and an application name relative to that source For example:

* If the HP Chelmsford classifications software lab cell is running

an RPC server from the Acme Database Company, that

server might be registered beneath the name /.../cssl.cell.ch.hp.com/

acme/acme_server (see Fig. 1) Within the CSSL small room /.:/acme/

acme_server would be an equivalent name for the server

* If the HP CSSL small cavity includes a principal named Nijinsky, that

principal would have the global name //csslcellchhpcom/

sec/principal/nijinksy (see Fig. 2) and the local name /.:/sec/principal/nijinksy.

* If the DF filespace in the HP Cupertino small room contains a file

called /users/sergey/mail/igor, that file would have the global