From commits-return-20345-apmail-directory-commits-archive=directory.apache.org@directory.apache.org Wed Nov 19 22:08:32 2008 Return-Path: Delivered-To: apmail-directory-commits-archive@www.apache.org Received: (qmail 67285 invoked from network); 19 Nov 2008 22:08:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Nov 2008 22:08:31 -0000 Received: (qmail 30853 invoked by uid 500); 19 Nov 2008 22:08:40 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 30813 invoked by uid 500); 19 Nov 2008 22:08:40 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 30804 invoked by uid 99); 19 Nov 2008 22:08:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Nov 2008 14:08:40 -0800 X-ASF-Spam-Status: No, hits=-1994.3 required=10.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_HTML_ONLY X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Nov 2008 22:07:16 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 45567234C297 for ; Wed, 19 Nov 2008 14:08:01 -0800 (PST) Message-ID: <1029493204.1227132481282.JavaMail.www-data@brutus> Date: Wed, 19 Nov 2008 14:08:01 -0800 (PST) From: confluence@apache.org To: commits@directory.apache.org Subject: [CONF] Apache Directory Server v1.5: Architectural Overview (page edited) MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org

Architectural Overview has been edited by Emmanuel L=C3=83=C2=A9charny (Nov 19, 2008).

=20

= (View changes)

Content:
<= colgroup>=
3D""= Work in progress

This site is in the process of being reviewed and updated.

Architectur= al Overview

Partitions

A partition is a physically distinct store for a subset of the entries c= ontained within a DSA (Directory Server/Service Agent A.K.A the LDAP server= ). The entries of a partition all share the same suffix which is the distin= guished name of the namingContext from which the stored entries in the part= ition are hung from the DIT. A partition can be implemented using any stora= ge mechanism or can even be backed in memory. The default storage mechanism= for a partition is JDBM. The addition of such a partition is described in = the Basic User's Guide. A= partition with a different storage mechanism simply has to implement the P= artition interface and by doing so can be mounted in the server at it's suf= fix/namingContext (described here).

The server can have any number of partitions (with any implementation) a= ttached to various namingContexts which are published by the RootDSE (empty= string dn "") using the namingContexts operational attribute. So if you w= ant to see the partitions served by the server you can query the RootDSE fo= r this information.