svn commit: r930594 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/2-server-config.html

[bu...@apache.org]

Author: buildbot
Date: Wed Nov 26 15:39:48 2014
New Revision: 930594

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Nov 26 15:39:48 2014
@@ -1 +1 @@
-1641831
+1641836

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html Wed Nov 26 15:39:48 2014
@@ -167,6 +167,10 @@
 <h1 id="2-server-configuraion">2 - Server Configuraion</h1>
 <p>We will now describe the server configuration. Usually, all the configuration is done using Apache Directory Studio, which offers a pretty GUI. One can also configure the server using LDAP request, as the configuration is stored in the <strong>DIT</strong>. Otherwise, all the configuration modifications won't be applied on a started server : usually, you will have to restart the server in order to get those modifications applied.</p>
 <p>It's a good policy not to modify the LDIF files by hand, but instead to use the Studio Configuration plugin to modify your configuration. </p>
+<h1 id="bean-graph">Bean graph</h1>
+<p>The following picture represent the structure of the container used to store the configuration inside the server. The yellow beans are abstract beans, extended by specific beans.</p>
+<p>The bold links mean we can have more than one instance of a bean.</p>
+<p><img alt="ApacheDS configuration beans" src="images/configBeans.png" /></p>
 <h1 id="overall-structure">Overall structure</h1>
 <p>The configuration is stored in a hierarchical order, where sub-elements are related to their parent. For instance, the <em>Transports</em> are associated to the <em>Server</em> they are child of. If we have many kind of servers, we will have as many transports as we have servers.</p>
 <p>The following hierarchy describe the different kind of elements that one can configure, and their relationship :</p>