directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r843750 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/ apacheds/advanced-ug/images/
Date Mon, 24 Dec 2012 23:59:01 GMT
Author: buildbot
Date: Mon Dec 24 23:59:00 2012
New Revision: 843750

Log:
Staging update by buildbot for directory

Added:
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.graphml   (with props)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.png   (with props)
Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 24 23:59:00 2012
@@ -1 +1 @@
-1425518
+1425693

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html Mon Dec 24 23:59:00 2012
@@ -131,10 +131,10 @@
 <h2 id="chapter-content">Chapter content</h2>
 <ul>
 <li><a href="1.1-architecture-overview.html">1.1 - Architectural Overview</a></li>
-<li><a href="1.2-frontend-protocols.html">1.2 - Frontend, protocol provider</a></li>
-<li><a href="1.3-interceptors.html">1.3 - Interceptors</a></li>
-<li><a href="1.4-backend.html">1.4 - Backend</a></li>
-<li><a href="1.5-schema-manager.html">1.5 - SchemaManager</a></li>
+<li><a href="1.2-network.html">1.2 - Network Layer</a></li>
+<li><a href="1.3-directory-service.html">1.3 - Directory-Service</a></li>
+<li><a href="1.4-interceptors.html">1.4 - Interceptors</a></li>
+<li><a href="1.5-backend.html">1.5 - Backend</a></li>
 </ul>
 
 

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html Mon Dec 24 23:59:00 2012
@@ -119,7 +119,7 @@
         </div>
         <div class="nav_next">
         
-            <a href="1.2-frontend-protocols.html">1.2 - Frontend, protocol provider</a>
+            <a href="1.2-network.html">1.2 - Network Layer</a>
 		
         </div>
         <div class="clearfix"></div>
@@ -127,7 +127,14 @@
 
 
 <h1 id="11-architecture-overview">1.1 - Architecture Overview</h1>
-<p>Blah...</p>
+<p>The Apache Directory Server (aka <em>ApacheDS</em>) architecture has many different layers. The following schema expose the most important ones :</p>
+<p><img alt="ApacheDS architecture" src="images/architecture.png" /></p>
+<p>As we can see, we distinguish four different layers :
+<em> The network
+</em> The Session
+<em> The PartitionNexus
+</em> The Backends</p>
+<p>We will describe in detail those layers in the following chapters.</p>
 
 
     <div class="nav">
@@ -143,7 +150,7 @@
         </div>
         <div class="nav_next">
         
-            <a href="1.2-frontend-protocols.html">1.2 - Frontend, protocol provider</a>
+            <a href="1.2-network.html">1.2 - Network Layer</a>
 		
         </div>
         <div class="clearfix"></div>

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html (added)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html Mon Dec 24 23:59:00 2012
@@ -0,0 +1,185 @@
+<!DOCTYPE html>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+	<head>
+		<title>1.2 - Newtork Layer &mdash; Apache Directory</title>
+		
+        <link href="./../../css/common.css" rel="stylesheet" type="text/css">
+    	<link href="./../../css/green.css" rel="stylesheet" type="text/css">
+    
+	</head>
+	<body>
+	    <div id="container">
+            <div id="header">
+                <div id="subProjectsNavBar">
+                    <a href="./../../">
+                        
+                        Apache Directory Project
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../apacheds">
+                        
+                        <STRONG>ApacheDS</STRONG>
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../studio">
+                        
+                        Apache Directory Studio
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../api">
+                        
+                        Apache LDAP API
+                        
+                    </a>
+                </div><!-- subProjectsNavBar -->
+            </div><!-- header -->
+            <div id="content">
+                <div id="leftColumn">
+                    
+<div id="navigation">
+    
+    <h5>ApacheDS 2.0</h5>
+    <ul>
+        <li><a href="./../../apacheds/">Home</a></li>
+        <li><a href="./../../apacheds/features.html">Features</a></li>
+    </ul>
+    <h5>Downloads</h5>
+    <ul>
+        <li><a href="./../../apacheds/downloads.html">ApacheDS 2.0.0-M8</a>&nbsp;&nbsp;<img src="./../../images/new_badge.gif" alt="" style="margin- bottom:- 3px;" border="0"></li>
+        <li><a href="./../../apacheds/download-old-versions.html">Older versions</a></li>
+    </ul>
+    <h5>Documentation</h5>
+    <ul>
+        <li><a href="./../../apacheds/basic-users-guide.html">Basic User's Guide </a></li>
+        <li><a href="./../../apacheds/advanced-users-guide.html">Advanced User's Guide</a></li>
+        <li><a href="./../../apacheds/developers-guide.html">Developer's Guide</a></li>
+        <li><a href="./../../apacheds/configuration/ads-2.0-configuration.html">Configuration</a></li>
+            <!--li><a href="./../../apacheds/gen-docs/latest">Generated Reports (e.g. JavaDocs)</a></li-->
+    </ul>
+    
+    
+    <h5>Support</h5>
+    <ul>
+        <li><a href="./../../mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
+        <li><a href="./../../sources.html">Sources</a></li>
+        <li><a href="./../../issue-tracking.html">Issue Tracking</a></li>
+        <li><a href="./../../commercial-support.html">Commercial Support</a></li>
+    </ul>
+    <h5>Community</h5>
+    <ul>
+        <li><a href="./../../contribute.html">How to Contribute</a></li>
+        <li><a href="./../../team.html">Team</a></li>
+        <li><a href="./../../original-project-proposal.html">Original Project Proposal</a></li>
+        <li><a href="./../../special-thanks.html" class="external-link" rel="nofollow">Special Thanks</a></li>
+    </ul>
+    <h5>About Apache</h5>
+    <ul>
+        <li><a href="http://www.apache.org/">Apache</a></li>
+        <li><a href="http://www.apache.org/licenses/">License</a></li>
+        <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+        <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+        <li><a href="http://www.apache.org/security/">Security</a></li>
+    </ul>
+    
+</div><!-- navigation -->
+
+                </div><!-- leftColumn -->
+                <div id="rightColumn">
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.1-architecture-overview.html">1.1 - Architecture Overview</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.3-directory-service.html">1.3 - DirectoryService</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+<h1 id="12-network-layer">1.2 - Network Layer</h1>
+<p>This layer is the part the user connects to when he wants to obtain some data from the server. This is not a mandatory part ot the server : we don't need to use it when the server is embedded.</p>
+<p>We offer more than just LDAP protocol, the server also include various protocols :
+<em> Kerberos
+</em> NTP
+<em> DHCP
+</em> DNS
+* ChangePassword</p>
+<p>Not all of them are implemented in the current version, but at least the Kerberos server is available. (The other protocols have been developped as a proof of concept : as they are all dpeending on a storage database, we have used the LDAP server as a storage).</p>
+<p>It's perfectly possible to imagine more protocols being implemented in the near future...</p>
+<h2 id="server-startup">Server startup</h2>
+<p>This chapter title is a bit misleading. We don't start a server, we start a <em>DirectoryService</em>, then we start various servers on top of it. The <em>DirectoryService</em> is the part responsible for the management f data (retrieval, storage, etc). All the servers can access this storage if needed.</p>
+<p>So when the <em>DirectoryService</em> has been started and is operational, we can start the various servers, which will accept incoming requests from remote peers.</p>
+<h3 id="transports">Transports</h3>
+<p>We allow connection through the definition of <em>transports</em>. A <em>Transport</em> is a <strong>TCP</strong> or an <strong>UDP</strong> socket capable of absorbing a request and to send a response. Depending on the type of server, we may declare one or more <strong>TCP</strong> <em>Transports</em>, or a <strong>TCP</strong> and a <strong>UDP</strong> <em>Transports</em>, or an <strong>UDP</strong> <em>Transport</em> only.</p>
+<h3 id="ldap-server">Ldap Server</h3>
+<p>The LDAP server needs one or two <strong>TCP</strong> <em>Transport</em>. We have the standard <em>LDAP</em> port (defaulting to <em>10389</em> for <em>ApacheDS</em>, but the well know port is usually 389), and one can also declare the <em>LDAPS</em> port (defaulting to <em>10636</em> for <em>ApacheDS</em>, but the well know port is usually 636). </p>
+<p><DIV class="warning" markdown="1">
+Note that <em>LDAPS</em> is considered as deprecated.
+</DIV></p>
+<h3 id="kerberos-server">Kerberos Server</h3>
+<p>The Kerberos Server uses one <strong>TCP</strong> <em>Transport</em> (defaulting to <em>60088</em>, but the well know port is 88 ) and one <strong>UDP</strong> _transport (same value for both ports). The idea is that the communication starts on <strong>TCP</strong> and continues on <strong>UDP</strong>.</p>
+<h3 id="changepassword-server">ChangePassword Server</h3>
+<p>The ChangePassword Server uses one <strong>TCP</strong> <em>Transport</em> and one <strong>UDP</strong> transport, too. The default value is <em>60464</em>, but the well known port is <em>464</em>.</p>
+<h3 id="http-server">Http Server</h3>
+<p>We have a HttpServer running too, it's used for management. The declared ports are both <strong>TCP</strong> port, one is for HTTP and its default value is <em>8080</em>, the other one is for HTTPS and its default value is <em>8443</em>.</p>
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.1-architecture-overview.html">1.1 - Architecture Overview</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.3-directory-service.html">1.3 - DirectoryService</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+                </div><!-- rightColumn -->
+                <div id="endContent"></div>
+            </div><!-- content -->
+            <div id="footer">&copy; 2003-2012, <a href="http://www.apache.org">The Apache Software Foundation</a> - <a href="./../../privacy-policy.html">Privacy Policy</a><br />
+                Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio, Apache LDAP API, Apache Triplesec, Triplesec, Apache, the Apache feather logo, and the Apache Directory project logos are trademarks of The Apache Software Foundation.
+            </div>
+        </div><!-- container -->
+    </body>
+</html>
\ No newline at end of file

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html (added)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html Mon Dec 24 23:59:00 2012
@@ -0,0 +1,168 @@
+<!DOCTYPE html>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+	<head>
+		<title>1.3 - DirectoryService &mdash; Apache Directory</title>
+		
+        <link href="./../../css/common.css" rel="stylesheet" type="text/css">
+    	<link href="./../../css/green.css" rel="stylesheet" type="text/css">
+    
+	</head>
+	<body>
+	    <div id="container">
+            <div id="header">
+                <div id="subProjectsNavBar">
+                    <a href="./../../">
+                        
+                        Apache Directory Project
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../apacheds">
+                        
+                        <STRONG>ApacheDS</STRONG>
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../studio">
+                        
+                        Apache Directory Studio
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../api">
+                        
+                        Apache LDAP API
+                        
+                    </a>
+                </div><!-- subProjectsNavBar -->
+            </div><!-- header -->
+            <div id="content">
+                <div id="leftColumn">
+                    
+<div id="navigation">
+    
+    <h5>ApacheDS 2.0</h5>
+    <ul>
+        <li><a href="./../../apacheds/">Home</a></li>
+        <li><a href="./../../apacheds/features.html">Features</a></li>
+    </ul>
+    <h5>Downloads</h5>
+    <ul>
+        <li><a href="./../../apacheds/downloads.html">ApacheDS 2.0.0-M8</a>&nbsp;&nbsp;<img src="./../../images/new_badge.gif" alt="" style="margin- bottom:- 3px;" border="0"></li>
+        <li><a href="./../../apacheds/download-old-versions.html">Older versions</a></li>
+    </ul>
+    <h5>Documentation</h5>
+    <ul>
+        <li><a href="./../../apacheds/basic-users-guide.html">Basic User's Guide </a></li>
+        <li><a href="./../../apacheds/advanced-users-guide.html">Advanced User's Guide</a></li>
+        <li><a href="./../../apacheds/developers-guide.html">Developer's Guide</a></li>
+        <li><a href="./../../apacheds/configuration/ads-2.0-configuration.html">Configuration</a></li>
+            <!--li><a href="./../../apacheds/gen-docs/latest">Generated Reports (e.g. JavaDocs)</a></li-->
+    </ul>
+    
+    
+    <h5>Support</h5>
+    <ul>
+        <li><a href="./../../mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
+        <li><a href="./../../sources.html">Sources</a></li>
+        <li><a href="./../../issue-tracking.html">Issue Tracking</a></li>
+        <li><a href="./../../commercial-support.html">Commercial Support</a></li>
+    </ul>
+    <h5>Community</h5>
+    <ul>
+        <li><a href="./../../contribute.html">How to Contribute</a></li>
+        <li><a href="./../../team.html">Team</a></li>
+        <li><a href="./../../original-project-proposal.html">Original Project Proposal</a></li>
+        <li><a href="./../../special-thanks.html" class="external-link" rel="nofollow">Special Thanks</a></li>
+    </ul>
+    <h5>About Apache</h5>
+    <ul>
+        <li><a href="http://www.apache.org/">Apache</a></li>
+        <li><a href="http://www.apache.org/licenses/">License</a></li>
+        <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+        <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+        <li><a href="http://www.apache.org/security/">Security</a></li>
+    </ul>
+    
+</div><!-- navigation -->
+
+                </div><!-- leftColumn -->
+                <div id="rightColumn">
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.2-network.html">1.2 - Network Layer</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.4-interceptors.html">1.4 - Interceptors</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+<h1 id="13-directoryservice">1.3 - DirectoryService</h1>
+<p>The <em>DirectoryService</em> is the core of the server. This is where we process incoming requests and ask the backend for data. </p>
+<p>It has an entry point, the <em>OperationManager</em>, which is in charge of pushing the requests into the <em>Interceptors</em> chain, and to protect the server against concurrent modifications.</p>
+<p>Then the request is going through every <em>Interceptor</em> being registred for this operation. When we have gone through all the <em>Interceptors</em>, we have reach the <em>PartitionNexus</em>, which is the connection with the backends.</p>
+<p>We now just have to determinate which type of <em>Backend</em> we should address, and this is done using the <em>Dn</em>.The request is then transmitted to the <em>Backend</em>, which returns the result.</p>
+<p>The result bubble up through the <em>Interceptors</em> as we unfold the stack stack, up the the <em>OperationManager</em> and the caller.</p>
+<h2 id="environment">Environment</h2>
+<p>The <em>DirectoryService</em> knows about its execution environment : it has a <em>schemaManager</em> instance, it knows about the <em>Interceptors</em> chain, it stores a map of all the pending requests (it's necessary as one may abandon some request), it holds the existing <em>Sessions</em>.</p>
+<p>In other word, the <em>DirectoryService</em> is not only the part of teh server executing the logic, it also holds the current state of every clients.</p>
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.2-network.html">1.2 - Network Layer</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.4-interceptors.html">1.4 - Interceptors</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+                </div><!-- rightColumn -->
+                <div id="endContent"></div>
+            </div><!-- content -->
+            <div id="footer">&copy; 2003-2012, <a href="http://www.apache.org">The Apache Software Foundation</a> - <a href="./../../privacy-policy.html">Privacy Policy</a><br />
+                Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio, Apache LDAP API, Apache Triplesec, Triplesec, Apache, the Apache feather logo, and the Apache Directory project logos are trademarks of The Apache Software Foundation.
+            </div>
+        </div><!-- container -->
+    </body>
+</html>
\ No newline at end of file

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html (added)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html Mon Dec 24 23:59:00 2012
@@ -0,0 +1,645 @@
+<!DOCTYPE html>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+	<head>
+		<title>1.4 - Interceptors &mdash; Apache Directory</title>
+		
+        <link href="./../../css/common.css" rel="stylesheet" type="text/css">
+    	<link href="./../../css/green.css" rel="stylesheet" type="text/css">
+    
+	</head>
+	<body>
+	    <div id="container">
+            <div id="header">
+                <div id="subProjectsNavBar">
+                    <a href="./../../">
+                        
+                        Apache Directory Project
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../apacheds">
+                        
+                        <STRONG>ApacheDS</STRONG>
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../studio">
+                        
+                        Apache Directory Studio
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../api">
+                        
+                        Apache LDAP API
+                        
+                    </a>
+                </div><!-- subProjectsNavBar -->
+            </div><!-- header -->
+            <div id="content">
+                <div id="leftColumn">
+                    
+<div id="navigation">
+    
+    <h5>ApacheDS 2.0</h5>
+    <ul>
+        <li><a href="./../../apacheds/">Home</a></li>
+        <li><a href="./../../apacheds/features.html">Features</a></li>
+    </ul>
+    <h5>Downloads</h5>
+    <ul>
+        <li><a href="./../../apacheds/downloads.html">ApacheDS 2.0.0-M8</a>&nbsp;&nbsp;<img src="./../../images/new_badge.gif" alt="" style="margin- bottom:- 3px;" border="0"></li>
+        <li><a href="./../../apacheds/download-old-versions.html">Older versions</a></li>
+    </ul>
+    <h5>Documentation</h5>
+    <ul>
+        <li><a href="./../../apacheds/basic-users-guide.html">Basic User's Guide </a></li>
+        <li><a href="./../../apacheds/advanced-users-guide.html">Advanced User's Guide</a></li>
+        <li><a href="./../../apacheds/developers-guide.html">Developer's Guide</a></li>
+        <li><a href="./../../apacheds/configuration/ads-2.0-configuration.html">Configuration</a></li>
+            <!--li><a href="./../../apacheds/gen-docs/latest">Generated Reports (e.g. JavaDocs)</a></li-->
+    </ul>
+    
+    
+    <h5>Support</h5>
+    <ul>
+        <li><a href="./../../mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
+        <li><a href="./../../sources.html">Sources</a></li>
+        <li><a href="./../../issue-tracking.html">Issue Tracking</a></li>
+        <li><a href="./../../commercial-support.html">Commercial Support</a></li>
+    </ul>
+    <h5>Community</h5>
+    <ul>
+        <li><a href="./../../contribute.html">How to Contribute</a></li>
+        <li><a href="./../../team.html">Team</a></li>
+        <li><a href="./../../original-project-proposal.html">Original Project Proposal</a></li>
+        <li><a href="./../../special-thanks.html" class="external-link" rel="nofollow">Special Thanks</a></li>
+    </ul>
+    <h5>About Apache</h5>
+    <ul>
+        <li><a href="http://www.apache.org/">Apache</a></li>
+        <li><a href="http://www.apache.org/licenses/">License</a></li>
+        <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+        <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+        <li><a href="http://www.apache.org/security/">Security</a></li>
+    </ul>
+    
+</div><!-- navigation -->
+
+                </div><!-- leftColumn -->
+                <div id="rightColumn">
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.3-directory-service.html">1.3 - DirectoryService</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.5-backend.html">1.5 - Backend</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+<h1 id="14-interceptors">1.4 - Interceptors</h1>
+<p><em>Interceptors</em> are functional layers inside the <em>DirectoryService</em>. Ech one of them are responsible for a specific task. They are ordered, and this order is not to be changed.</p>
+<p>Some <em>Interceptors</em> can be disabled, some other can be enabled. It's also possible to add some new one.</p>
+<p>All in all, they will handle operations from a specific functional aspect.</p>
+<h2 id="handled-operations">Handled operations</h2>
+<p>Each <em>Interceptor</em> handle a subset of the possible operations, among those listed in the following table :</p>
+<table>
+<thead>
+<tr>
+<th>Operation</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Add</td>
+<td>Add an entry in the backend</td>
+</tr>
+<tr>
+<td>Bind</td>
+<td>Bind on the DirectoryService</td>
+</tr>
+<tr>
+<td>Compare</td>
+<td>Compare the elements with the associated entry in the backend</td>
+</tr>
+<tr>
+<td>Delete</td>
+<td>Delete the entry</td>
+</tr>
+<tr>
+<td>getRooDSE</td>
+<td>Get back the RootDSE entry</td>
+</tr>
+<tr>
+<td>hasEntry</td>
+<td>Tells if an entry exists</td>
+</tr>
+<tr>
+<td>Lookup</td>
+<td>Fetch an entry</td>
+</tr>
+<tr>
+<td>Modify</td>
+<td>Modify an entry</td>
+</tr>
+<tr>
+<td>Move</td>
+<td>Move an entry</td>
+</tr>
+<tr>
+<td>MoveAndRename</td>
+<td>Move and rename an entry</td>
+</tr>
+<tr>
+<td>Rename</td>
+<td>Rename an entry</td>
+</tr>
+<tr>
+<td>Search</td>
+<td>Search for entries</td>
+</tr>
+<tr>
+<td>Unbind</td>
+<td>Unbind from the DirectoryService</td>
+</tr>
+</tbody>
+</table>
+<p>It is important to understand that each operation wil go through each <em>Interceptor</em> that are declared to handle the operation, down to the backend.</p>
+<h2 id="existing-interceptors">Existing interceptors</h2>
+<p>The following interceptors are already present in the server, even if they are not enabled. In this table, we list all the operation each interceptor is handling, and if the <em>interceptor</em> is enabled by default or not :</p>
+<table>
+<thead>
+<tr>
+<th>Interceptor</th>
+<th>Enabled</th>
+<th>add</th>
+<th>bnd</th>
+<th>cmp</th>
+<th>del</th>
+<th>DSE</th>
+<th>has</th>
+<th>lkp</th>
+<th>mod</th>
+<th>mov</th>
+<th>m&amp;r</th>
+<th>ren</th>
+<th>sea</th>
+<th>ubd</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>AciAuthorizationInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>AdministrativePointInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>?</td>
+<td>-</td>
+</tr>
+<tr>
+<td>AuthenticationInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+</tr>
+<tr>
+<td>ChangeLogInterceptor</td>
+<td>yes</td>
+<td></td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>CollectiveAttributeInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>DefaultAuthorizationInterceptor</td>
+<td>yes</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>EventInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>ExceptionInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>JournalInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>KeyDerivationInterceptor</td>
+<td>no</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>NormalizationInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>OperationalAttributeInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>PasswordHashingInterceptor</td>
+<td>no</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>ReferralInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+</tr>
+<tr>
+<td>SchemaInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>?</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>SubentryInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>?</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+</tr>
+<tr>
+<td>TimerInterceptor</td>
+<td>no</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+</tr>
+<tr>
+<td>TriggerInterceptor</td>
+<td>yes</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+<td>-</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>X</td>
+<td>-</td>
+<td>-</td>
+</tr>
+</tbody>
+</table>
+<h2 id="interceptors-order">Interceptors order</h2>
+<p>As we already said, the <em>Intecreptors</em> order is significant : why would we proceed an <em>Add</em> operation through all the <em>Interceptors</em> if the user is simply denied the right to add an entry by the <em>AciAuthorizationInterceptor</em> ?</p>
+<p>Currently, the following order is enforced :</p>
+<table>
+<thead>
+<tr>
+<th>Order</th>
+<th>Interceptor</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>1</td>
+<td>NormalizationInterceptor</td>
+</tr>
+<tr>
+<td>2</td>
+<td>AuthenticationInterceptor</td>
+</tr>
+<tr>
+<td>3</td>
+<td>ReferralInterceptor</td>
+</tr>
+<tr>
+<td>4</td>
+<td>AciAuthorizationInterceptor</td>
+</tr>
+<tr>
+<td>5</td>
+<td>DefaultAuthorizationInterceptor</td>
+</tr>
+<tr>
+<td>6</td>
+<td>AdministrativePointInterceptor</td>
+</tr>
+<tr>
+<td>7</td>
+<td>ExceptionInterceptor</td>
+</tr>
+<tr>
+<td>8</td>
+<td>SchemaInterceptor</td>
+</tr>
+<tr>
+<td>9</td>
+<td>OperationalAttributeInterceptor</td>
+</tr>
+<tr>
+<td>10</td>
+<td>SubentryInterceptor</td>
+</tr>
+<tr>
+<td>11</td>
+<td>EventInterceptor</td>
+</tr>
+<tr>
+<td>12</td>
+<td>TriggerInterceptor</td>
+</tr>
+<tr>
+<td>13</td>
+<td>ChangeLogInterceptor</td>
+</tr>
+<tr>
+<td>14</td>
+<td>JournalInterceptor</td>
+</tr>
+</tbody>
+</table>
+<h2 id="example">Example</h2>
+<p>Let's consider the <em>search</em> operation. It will be processed successuvly by the following <em>Intecreptors</em>, as it can be deduced by the two previous tables :</p>
+<ul>
+<li>NormalizationInterceptor</li>
+<li>AuthenticationInterceptor</li>
+<li>AciAuthorizationInterceptor</li>
+<li>DefaultAuthorizationInterceptor</li>
+<li>SchemaInterceptor</li>
+<li>OperationalAttributeInterceptor</li>
+<li>SubentryInterceptor</li>
+</ul>
+<p>We can do the same exercise for each operation.</p>
+<h2 id="processing">Processing</h2>
+<p>Basically, an <em>Interceptor</em> receives a request for an operation, do some pre-processing, call the next <em>Interceptor</em> in the chain, do some post-processing, and return a result. </p>
+<p>Calling the next <em>Interceptor</em> is as simple as calling the <em>next(OperationContext)</em> method, which will compute the right <em>Interceptor</em>.</p>
+<p>The pre-processing and post-processing are standard Java code, there is nothing special there. </p>
+<p>Each operation is passed into an instance of a specific <em>OperationContext</em>, which contains all what is needed about the operation and the environement.</p>
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.3-directory-service.html">1.3 - DirectoryService</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="1.5-backend.html">1.5 - Backend</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+                </div><!-- rightColumn -->
+                <div id="endContent"></div>
+            </div><!-- content -->
+            <div id="footer">&copy; 2003-2012, <a href="http://www.apache.org">The Apache Software Foundation</a> - <a href="./../../privacy-policy.html">Privacy Policy</a><br />
+                Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio, Apache LDAP API, Apache Triplesec, Triplesec, Apache, the Apache feather logo, and the Apache Directory project logos are trademarks of The Apache Software Foundation.
+            </div>
+        </div><!-- container -->
+    </body>
+</html>
\ No newline at end of file

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html (added)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html Mon Dec 24 23:59:00 2012
@@ -0,0 +1,205 @@
+<!DOCTYPE html>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+	<head>
+		<title>1.5 - Backend &mdash; Apache Directory</title>
+		
+        <link href="./../../css/common.css" rel="stylesheet" type="text/css">
+    	<link href="./../../css/green.css" rel="stylesheet" type="text/css">
+    
+	</head>
+	<body>
+	    <div id="container">
+            <div id="header">
+                <div id="subProjectsNavBar">
+                    <a href="./../../">
+                        
+                        Apache Directory Project
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../apacheds">
+                        
+                        <STRONG>ApacheDS</STRONG>
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../studio">
+                        
+                        Apache Directory Studio
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./../../api">
+                        
+                        Apache LDAP API
+                        
+                    </a>
+                </div><!-- subProjectsNavBar -->
+            </div><!-- header -->
+            <div id="content">
+                <div id="leftColumn">
+                    
+<div id="navigation">
+    
+    <h5>ApacheDS 2.0</h5>
+    <ul>
+        <li><a href="./../../apacheds/">Home</a></li>
+        <li><a href="./../../apacheds/features.html">Features</a></li>
+    </ul>
+    <h5>Downloads</h5>
+    <ul>
+        <li><a href="./../../apacheds/downloads.html">ApacheDS 2.0.0-M8</a>&nbsp;&nbsp;<img src="./../../images/new_badge.gif" alt="" style="margin- bottom:- 3px;" border="0"></li>
+        <li><a href="./../../apacheds/download-old-versions.html">Older versions</a></li>
+    </ul>
+    <h5>Documentation</h5>
+    <ul>
+        <li><a href="./../../apacheds/basic-users-guide.html">Basic User's Guide </a></li>
+        <li><a href="./../../apacheds/advanced-users-guide.html">Advanced User's Guide</a></li>
+        <li><a href="./../../apacheds/developers-guide.html">Developer's Guide</a></li>
+        <li><a href="./../../apacheds/configuration/ads-2.0-configuration.html">Configuration</a></li>
+            <!--li><a href="./../../apacheds/gen-docs/latest">Generated Reports (e.g. JavaDocs)</a></li-->
+    </ul>
+    
+    
+    <h5>Support</h5>
+    <ul>
+        <li><a href="./../../mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
+        <li><a href="./../../sources.html">Sources</a></li>
+        <li><a href="./../../issue-tracking.html">Issue Tracking</a></li>
+        <li><a href="./../../commercial-support.html">Commercial Support</a></li>
+    </ul>
+    <h5>Community</h5>
+    <ul>
+        <li><a href="./../../contribute.html">How to Contribute</a></li>
+        <li><a href="./../../team.html">Team</a></li>
+        <li><a href="./../../original-project-proposal.html">Original Project Proposal</a></li>
+        <li><a href="./../../special-thanks.html" class="external-link" rel="nofollow">Special Thanks</a></li>
+    </ul>
+    <h5>About Apache</h5>
+    <ul>
+        <li><a href="http://www.apache.org/">Apache</a></li>
+        <li><a href="http://www.apache.org/licenses/">License</a></li>
+        <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+        <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+        <li><a href="http://www.apache.org/security/">Security</a></li>
+    </ul>
+    
+</div><!-- navigation -->
+
+                </div><!-- leftColumn -->
+                <div id="rightColumn">
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.4-interceptors.html">1.4 - Interceptors</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="2-server-config.html">2 - Server Configuration</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+<h1 id="15-backend">1.5 - Backend</h1>
+<p>The <em>Backend</em> is the part of the server responsible for storing data in a way we can easily retrieve them. This storage does not necessarily have to be remanent : we can have a in-memory <em>backend</em>.</p>
+<h2 id="existing-backends">Existing Backends</h2>
+<p>We currently have 3 different backends :
+<em> JDBM
+</em> LDIF
+* In-Memory</p>
+<h3 id="jdbm-backend">JDBM Backend</h3>
+<p>The <strong>JDBM</strong> backend is storing data on disk, using <strong>BTrees</strong>. It's fast when it comes to retrieve data, slow when you have to add them.</p>
+<h3 id="in-memory-backend">In-Memory Backend</h3>
+<p>This Backend loads in memory a full set of entries. ALl of them must be hold by the existig memory, we don't write on disk anything nor we read anything from disk. If the server is stopped, everything is lost.</p>
+<h3 id="ldif-backend">LDIF Backend</h3>
+<p>It come sin two forms : one single file, or many fles (one per entry). It's always backed by a in-memory <em>Backend</em>, otherwise it would not be possible to retrieve the entries. </p>
+<p>As we depend on a in-memory backend, which handles the indexes, we have to create those index when this <em>Backend</em> is read, which can be a costly operation. </p>
+<h3 id="future-backends">Future Backends</h3>
+<p>We intend to add another in-memory backend, based on <em>Mavibot</em>, a <strong>MVCC BTREE</strong>. The biggest advantage over the other systems is that it's fast, it allows concurrent reads without locks when the other <em>Backend</em> block the reads when some write operation is being processed. Also it saves on disk it contents peridodically, and has a Journal so that we can recover fro a crash.</p>
+<p>The only drawback is that all the entries and indexes must hold in memory. On the other hand, we don't anymore need a cache.</p>
+<h2 id="how-it-works">How it works</h2>
+<p>Basically, each <em>Backend</em> instance inherit from the <em>AbstractBTreePartition</em> class. We can see that a <em>Backend</em> <strong>must</strong> be a <strong>Btree</strong>.</p>
+<p>Data are stored into various tables. In fact, we have one table containing all the entries - the <strong>MasterTable</strong> - and many indexes. </p>
+<h3 id="mastertable">MasterTable</h3>
+<p>The <em>MasterTable</em> coantins all the entries, serialized. </p>
+<p>This table is a <Key, Value> <strong>BTree</strong>, where the key is the entry's <strong>UUID</strong>, and the value the serialized entry.</p>
+<p><DIV class="note" markdown="1">
+Theorically, we could be able to read it, and restore the whole database, indexes included, assuming that we know which index we have to create. Sadly, it's not enough, as the entries are stored without any information about their position in the <strong>DIT</strong>.
+</DIV></p>
+<h3 id="indexes">Indexes</h3>
+<p>Each index is also a <key, value> <strong>BTree</strong>, with some exceptions : as we may store multi-valued elements, it's perfectly possible that the value will grow up to a point it's extremely costly to store it serialized. For instance, the <em>ObjectClass</em> index may have thousands of entries for the <em>Person</em> key.</p>
+<p>In this case, we use a sub-btree, which is a <key,key> <strong>BTree</strong> (as strange as it sounds, it's an easy way to add a new key without having to rewrite the full value).</p>
+<p>The key can be a <em>String</em>, or a <em>ParentIdAndRdn</em>.</p>
+<p>We have 7 system indexes, which are created when the server is started :</p>
+<ul>
+<li>ObjectClass : to easily find any entry associated with a give <em>ObjectClass</em></li>
+<li>EntryUUID : The entry unique ID index</li>
+<li>EntryCsn : The Change Sequence Number index</li>
+<li>ParentIdAndRdn : A special index containing a RDN and its parent</li>
+<li>Presence : An index used when searching for the presence of an attributeType in an entry</li>
+<li>Alias : An index used for aliases</li>
+<li>OneAlias : An index used for children aliases </li>
+<li>SubAlias : An index used of descendant aliases</li>
+</ul>
+<p>The user may define many different index, dependening on his needs.</p>
+<h3 id="the-parentidandrdn-index">The ParentIdAndRdn index</h3>
+<p>This index is special, as it's used to associate an entry to a position in the <strong>DIT</strong>. Assuming that each entry has a <em>Dn</em>, and that this <em>Dn</em> describes a hierarchie, the <em>ParentIdAndRdn</em> index depicts this hierarchy.</p>
+<p>The <em>ParentId</em> part refers to the <em>UUID</em> of the parent for the current entry. The <em>Rdn</em> part is the entry <em>Rdn</em>. In order to rebuild the full <em>Dn</em> for a given entry, we must get all the <em>ParentIdAndRdn</em> up to the root to grab all the needed <em>Rdn</em>.</p>
+<p>This index is also used to process one level and sub level indexes.</p>
+
+
+    <div class="nav">
+        <div class="nav_prev">
+        
+            <a href="1.4-interceptors.html">1.4 - Interceptors</a>
+		
+        </div>
+        <div class="nav_up">
+        
+            <a href="1-architecture.html">1 - Architecture</a>
+		
+        </div>
+        <div class="nav_next">
+        
+            <a href="2-server-config.html">2 - Server Configuration</a>
+		
+        </div>
+        <div class="clearfix"></div>
+    </div>
+
+
+                </div><!-- rightColumn -->
+                <div id="endContent"></div>
+            </div><!-- content -->
+            <div id="footer">&copy; 2003-2012, <a href="http://www.apache.org">The Apache Software Foundation</a> - <a href="./../../privacy-policy.html">Privacy Policy</a><br />
+                Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio, Apache LDAP API, Apache Triplesec, Triplesec, Apache, the Apache feather logo, and the Apache Directory project logos are trademarks of The Apache Software Foundation.
+            </div>
+        </div><!-- container -->
+    </body>
+</html>
\ No newline at end of file

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html Mon Dec 24 23:59:00 2012
@@ -128,12 +128,12 @@
 
 <h1 id="operations">Operations</h1>
 <p>There are six kind of operations we can have on an AdministrativePoint :
-- creating a new AP
-- removing an existing AP
-- modifying an existing AP by adding or removing a role
-- renaming an AP
-- moving an AP
-- renaming or moving an AP</p>
+<em> creating a new AP
+</em> removing an existing AP
+<em> modifying an existing AP by adding or removing a role
+</em> renaming an AP
+<em> moving an AP
+</em> renaming or moving an AP</p>
 <p>Renaming an AP has no impact on the administrative model, as we don't point
 (internally) on the entry's DN, but on its UUID, so the last three
 operations can be gathered into one single Move operation.</p>

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.graphml
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.graphml
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/architecture.png
------------------------------------------------------------------------------
    svn:mime-type = image/png



Mime
View raw message