svn commit: r1010213 - in /websites/staging/directory/trunk/content: ./ apacheds/basic-ug/1.4.3-adding-partition.html

[bu...@apache.org]

Author: buildbot
Date: Tue Apr 11 08:10:18 2017
New Revision: 1010213

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 11 08:10:18 2017
@@ -1 +1 @@
-1790927
+1790938

Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html Tue Apr 11 08:10:18 2017
@@ -317,8 +317,8 @@ h2:hover > .headerlink, h3:hover > .head
 <p>When the server starts for the first time after installation, <em>config.ldif</em> is renamed to <em>config.ldif_migrated</em>. After that time, this priming ldif file is never referred to again, so any changes you make will be ignored. <a href="https://issues.apache.org/jira/browse/DIRSERVER-2050">The reason for this change is discussed in a JIRA</a>.</p>
 <h3 id="before-starting-the-server">Before starting the server<a class="headerlink" href="#before-starting-the-server" title="Permanent link">&para;</a></h3>
 <p>Therefore, if you would like to have your (empty) partition created immediately following installation, you should prevent your server from starting during or after installation, i.e. when config.ldif has not yet been migrated.</p>
-<p>Next, edit <em>config.ldif</em> to change all occurrences of "<strong>example</strong>" to suit the name of your own partition. Once the server has started and you run your first ldapsearch as the admin user, you will see that the server has created your own empty partition (instead of the example one).</p>
-<p>Note that the entry for the "<strong>example</strong>" partition does NOT have an <em>ads-contextEntry</em> attribute. This "signature" attribute is created during the "migration" process (see below for details).</p>
+<p>Next, edit <em>config.ldif</em> to change all occurrences of "<em>example</em>" to suit the name of your own partition. Once the server has started and you run your first ldapsearch as the admin user, you will see that the server has created your own empty partition (instead of the example one).</p>
+<p>Note that the entry for the "<em>example</em>" partition does NOT have an <em>ads-contextEntry</em> attribute. This "signature" attribute is created during the "migration" process (see below for details).</p>
 <p>Subsequent ldif changes to your new partition should work provided they use the default schema.</p>
 <h3 id="with-ldapmodify-to-a-running-server">With ldapmodify to a running server<a class="headerlink" href="#with-ldapmodify-to-a-running-server" title="Permanent link">&para;</a></h3>
 <p>This is task more tricky because the root of your new partition MUST have a valid <em>ads-contextEntry</em> attribute and you must determine its value. The other attributes (see the definitions above) are quite straightforward, but this control value must be synthesised based on the specific attribute values of your own partition.</p>
@@ -347,9 +347,9 @@ h2:hover > .headerlink, h3:hover > .head
 
 
 <p>Base64 these four lines as a single string (with \n newlines, but without the prefix spaces). The result should match the <em>ads-contextentry</em> value shown above.</p>
-<p>However, you need to be careful because simply adding an extra space or newline will change the base64 value and make it unacceptable to the server. Also, any valid UTF-8 attribute values which are not in the base64 character set (such as accented characters) <strong><em>MUST</em></strong> be base64-encoded strings, which effectively makes them double-encoded.
-e.g. <strong><em>"dn: cn=lécharny,dc=com"</em></strong> needs to be specified as <strong><em>"dn:: Y249bMOpY2hhcm55LGRjPWNvbQ=="</em></strong>.</p>
-<p>You will probably want to create some associated index entries. You can use those of the "<strong>example</strong>" partition in <em>config.ldif-migrated</em> for your templates (which do not require any special encoded attributes).</p>
+<p>However, you need to be careful because simply adding an extra space or newline will change the base64 value and make it unacceptable to the server. Also, any valid UTF-8 attribute values which are not in the base64 character set (such as accented characters) <em>MUST</em> be base64-encoded strings, which effectively makes them double-encoded.
+e.g. <em>"dn: cn=lécharny,dc=com"</em> needs to be specified as <em>"dn:: Y249bMOpY2hhcm55LGRjPWNvbQ=="</em>.</p>
+<p>You will probably want to create some associated index entries. You can use those of the "<em>example</em>" partition in <em>config.ldif-migrated</em> for your templates (which do not require any special encoded attributes).</p>
 
 
     <div class="nav">