You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2015/07/06 00:34:38 UTC
svn commit: r957126 [13/18] - in /websites/staging/directory/trunk/content:
./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/
apacheds/configuration/ apacheds/kerberos-ug/ api/ api/download/
api/groovy-api/ api/user-guide/ escimo/ fortress/ fortres...
Modified: websites/staging/directory/trunk/content/fortress/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/fortress/developer-guide.html Sun Jul 5 22:34:35 2015
@@ -160,7 +160,18 @@
-<h1 id="building-fortress">Building FORTRESS</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="building-fortress">Building FORTRESS<a class="headerlink" href="#building-fortress" title="Permanent link">¶</a></h1>
<DIV class="note" markdown="1">
Please read <a href="http://www.apache.org/dev/" class="external-link" rel="nofollow">the Developer Infrastructure Information</a> if you haven't yet before you proceed.
</DIV>
@@ -203,9 +214,9 @@
</li>
</ul>
</div>
-<h1 id="checking-out-the-code">Checking out the code</h1>
+<h1 id="checking-out-the-code">Checking out the code<a class="headerlink" href="#checking-out-the-code" title="Permanent link">¶</a></h1>
<p>You need Git to check out the source code from our source code repository, and [Maven(http://maven.apache.org/) 3.0 to build the source code. The following example shows how to get the Fortress projects.</p>
-<h2 id="fortress-core">Fortress-core</h2>
+<h2 id="fortress-core">Fortress-core<a class="headerlink" href="#fortress-core" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">core</span><span class="p">.</span><span class="n">git</span> <span class="n">fortress</span><span class="o">-</span><span class="n">core</span>
$ <span class="n">cd</span> <span class="n">fortress</span><span class="o">-</span><span class="n">core</span>
$ <span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> # <span class="n">Build</span> <span class="n">packages</span> <span class="p">(</span><span class="n">JARs</span><span class="p">)</span> <span class="k">for</span> <span class="n">the</span> <span class="n">Fortress</span> <span class="n">core</span> <span class="n">API</span> <span class="n">and</span> <span class="n">other</span>
@@ -221,7 +232,7 @@ You can declare new variables in Eclipse
<p>If you want to check out the source code of previous releases, you have to select the branch you want to work on :</p>
<p>$ git clone http://git-wip-us.apache.org/repos/asf/directory-fortress-core.git fortress-core
$ git checkout <tag></p>
-<h2 id="fortress-realm">Fortress-realm</h2>
+<h2 id="fortress-realm">Fortress-realm<a class="headerlink" href="#fortress-realm" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">realm</span><span class="p">.</span><span class="n">git</span> <span class="n">fortress</span><span class="o">-</span><span class="n">realm</span>
$ <span class="n">cd</span> <span class="n">fortress</span><span class="o">-</span><span class="n">realm</span>
$ <span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> # <span class="n">Build</span> <span class="n">packages</span> <span class="p">(</span><span class="n">JARs</span><span class="p">)</span> <span class="k">for</span> <span class="n">the</span> <span class="n">Fortress</span> <span class="n">realm</span> <span class="n">API</span> <span class="n">and</span> <span class="n">other</span>
@@ -237,7 +248,7 @@ You can declare new variables in Eclipse
<p>If you want to check out the source code of previous releases, you have to select the branch you want to work on :</p>
<p>$ git clone http://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git fortress-realm
$ git checkout <tag></p>
-<h2 id="fortress-enmasse">Fortress-enmasse</h2>
+<h2 id="fortress-enmasse">Fortress-enmasse<a class="headerlink" href="#fortress-enmasse" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">enmasse</span><span class="p">.</span><span class="n">git</span> <span class="n">fortress</span><span class="o">-</span><span class="n">enmasse</span>
$ <span class="n">cd</span> <span class="n">fortress</span><span class="o">-</span><span class="n">enmasse</span>
$ <span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> # <span class="n">Build</span> <span class="n">packages</span> <span class="p">(</span><span class="n">JARs</span><span class="p">)</span> <span class="k">for</span> <span class="n">the</span> <span class="n">Fortress</span> <span class="n">enmasse</span> <span class="n">API</span> <span class="n">and</span> <span class="n">other</span>
@@ -253,7 +264,7 @@ You can declare new variables in Eclipse
<p>If you want to check out the source code of previous releases, you have to select the branch you want to work on :</p>
<p>$ git clone http://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git fortress-enmasse
$ git checkout <tag></p>
-<h2 id="fortress-commander">Fortress-commander</h2>
+<h2 id="fortress-commander">Fortress-commander<a class="headerlink" href="#fortress-commander" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">commander</span><span class="p">.</span><span class="n">git</span> <span class="n">fortress</span><span class="o">-</span><span class="n">commander</span>
$ <span class="n">cd</span> <span class="n">fortress</span><span class="o">-</span><span class="n">commander</span>
$ <span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> # <span class="n">Build</span> <span class="n">packages</span> <span class="p">(</span><span class="n">JARs</span><span class="p">)</span> <span class="k">for</span> <span class="n">the</span> <span class="n">Fortress</span> <span class="n">commander</span> <span class="n">API</span> <span class="n">and</span> <span class="n">other</span>
@@ -269,9 +280,9 @@ You can declare new variables in Eclipse
<p>If you want to check out the source code of previous releases, you have to select the branch you want to work on :</p>
<p>$ git clone http://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git fortress-commander
$ git checkout <tag></p>
-<h1 id="coding-convention">Coding Convention</h1>
+<h1 id="coding-convention">Coding Convention<a class="headerlink" href="#coding-convention" title="Permanent link">¶</a></h1>
<p>The applicable coding standards for Fortress are described in <a href="coding-standards.html">Coding Standards</a></p>
-<h1 id="deploying-snapshots-commiters-only">Deploying Snapshots (Commiters Only)</h1>
+<h1 id="deploying-snapshots-commiters-only">Deploying Snapshots (Commiters Only)<a class="headerlink" href="#deploying-snapshots-commiters-only" title="Permanent link">¶</a></h1>
<p>Before running Maven to deploy artifacts, <em>please make sure if your umask is configured correctly</em>. Unless configured properly, other committers will experience annoying 'permission denied' errors. If your default shell is <code>bash</code>, please update your umask setting in the <code>~/.bashrc</code> file (create one if it doesn't exist.) by adding the following line:</p>
<div class="codehilite"><pre><span class="n">umask</span> 002
</pre></div>
@@ -287,8 +298,8 @@ $ <span class="n">mvn</span> <span class
<p>(do the same thing for the <em>enmasse, realm and commander</em> projects)</p>
<p>Please double-check the mode (i.e. <code>0664</code> or <code>-rw-rw-r--</code>, a.k.a permission code) of the deployed artifacts, otherwise you can waste other people's time significantly.</p>
-<h1 id="releasing-a-point-release-committers-only">Releasing a Point Release (Committers Only)</h1>
-<h2 id="preparing-the-release-for-the-vote">Preparing the release for the vote</h2>
+<h1 id="releasing-a-point-release-committers-only">Releasing a Point Release (Committers Only)<a class="headerlink" href="#releasing-a-point-release-committers-only" title="Permanent link">¶</a></h1>
+<h2 id="preparing-the-release-for-the-vote">Preparing the release for the vote<a class="headerlink" href="#preparing-the-release-for-the-vote" title="Permanent link">¶</a></h2>
<p>Before starting be sure to have the java and mvn command in your PATH.
On linux you can check with the following commands :</p>
<div class="codehilite"><pre>$ <span class="n">type</span> <span class="n">mvn</span>
@@ -298,12 +309,12 @@ $ <span class="n">type</span> <span clas
</pre></div>
-<h3 id="step-0-building-fortress-xxx">Step 0: Building Fortress-xxx</h3>
+<h3 id="step-0-building-fortress-xxx">Step 0: Building Fortress-xxx<a class="headerlink" href="#step-0-building-fortress-xxx" title="Permanent link">¶</a></h3>
<DIV class="note" markdown="1">
Here, 'xxx' is one of the four fortress mdules : core, enmasse, realm or comander
</DIV>
-<h3 id="step-1-tagging-and-deploying">Step 1: Tagging and Deploying</h3>
+<h3 id="step-1-tagging-and-deploying">Step 1: Tagging and Deploying<a class="headerlink" href="#step-1-tagging-and-deploying" title="Permanent link">¶</a></h3>
<p>First you need to configure maven for using the good username for scp and operation.</p>
<p>In the <code>~/.m2/settings.xml</code> you need the following lines :</p>
<div class="codehilite"><pre><span class="nt"><settings</span> <span class="na">xmlns=</span><span class="s">"http://maven.apache.org/POM/4.0.0"</span>
@@ -356,7 +367,7 @@ Here, 'xxx' is one of the four fortress
</pre></div>
-<h3 id="step-2-processing-with-a-dry-run">step 2 : Processing with a dry run</h3>
+<h3 id="step-2-processing-with-a-dry-run">step 2 : Processing with a dry run<a class="headerlink" href="#step-2-processing-with-a-dry-run" title="Permanent link">¶</a></h3>
<p>After having checked out the trunk, and built it (see step 0), </p>
<div class="codehilite"><pre>$ <span class="n">git</span> <span class="n">clone</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">core</span><span class="p">.</span><span class="n">git</span> <span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">core</span>
$ <span class="n">cd</span> <span class="n">directory</span><span class="o">-</span><span class="n">fortress</span><span class="o">-</span><span class="n">core</span>
@@ -390,7 +401,7 @@ $ <span class="n">mvn</span> <span class
Make sure the change made by the release plugin is correct! (pom.xml, tags created)
</DIV>
-<h3 id="step-3-processing-with-the-real-release">Step 3 : Processing with the real release</h3>
+<h3 id="step-3-processing-with-the-real-release">Step 3 : Processing with the real release<a class="headerlink" href="#step-3-processing-with-the-real-release" title="Permanent link">¶</a></h3>
<p>When the dry run is successful, then you can do in real with the following commands:</p>
<div class="codehilite"><pre>$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">clean</span> # <span class="n">Clean</span> <span class="n">up</span> <span class="n">the</span> <span class="n">temporary</span> <span class="n">files</span> <span class="n">created</span> <span class="n">by</span> <span class="n">the</span> <span class="n">dry</span><span class="o">-</span><span class="n">run</span><span class="p">.</span>
$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> # <span class="n">Copy</span> <span class="n">to</span> <span class="n">tags</span> <span class="n">directory</span><span class="p">.</span>
@@ -429,7 +440,7 @@ $ <span class="n">mvn</span> <span class
<p>The first mail tells you that the SNAPSHOT has been moved to the release version in trunk, the second mails tells you that this version has been tagged, and the last mail tells you that trunk has moved to the next version.</p>
-<h3 id="step-4-perform-the-release">Step 4 : perform the release</h3>
+<h3 id="step-4-perform-the-release">Step 4 : perform the release<a class="headerlink" href="#step-4-perform-the-release" title="Permanent link">¶</a></h3>
<p>The last step before launching a vote is to push the potential release to Nexus so that every user can test the created packages. Perform the following actions</p>
<div class="codehilite"><pre>$ <span class="n">mvn</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span> <span class="n">release</span><span class="p">:</span><span class="n">perform</span>
<span class="p">...</span>
@@ -452,17 +463,17 @@ $ <span class="n">mvn</span> <span class
<p>Done !</p>
-<h3 id="step-5-closing-the-staging-release-on-nexus">Step 5 : closing the staging release on nexus</h3>
+<h3 id="step-5-closing-the-staging-release-on-nexus">Step 5 : closing the staging release on nexus<a class="headerlink" href="#step-5-closing-the-staging-release-on-nexus" title="Permanent link">¶</a></h3>
<p>Now, you have to close the staged project on nexus. In order to do that you <em>must</em> have exported your PGP key to a PGP public server <a href="http://www.apache.org/dev/openpgp.html">see</a></p>
<p>Connect to the <a href="https://repository.apache.org">Nexus server</a>, login, and select the MINA staging repository you just created, then click on the 'close' button. You are home...</p>
-<h3 id="step-6-build-the-site">Step 6 : Build the Site</h3>
+<h3 id="step-6-build-the-site">Step 6 : Build the Site<a class="headerlink" href="#step-6-build-the-site" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>$ <span class="n">cd</span> <span class="n">target</span><span class="o">/</span><span class="n">checkout</span>
$ <span class="n">mvn</span> <span class="n">site</span>
</pre></div>
<p>This creates the site.</p>
-<h3 id="step-7-sign-the-packages">Step 7 : Sign the packages</h3>
+<h3 id="step-7-sign-the-packages">Step 7 : Sign the packages<a class="headerlink" href="#step-7-sign-the-packages" title="Permanent link">¶</a></h3>
<p>Now, you have to sign the binary packages which are in target/checkout/target.</p>
<DIV class="note" markdown="1">
Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID)
@@ -615,7 +626,7 @@ stty <span class="nb">echo</span>
</pre></div>
</td></tr></table>
-<h3 id="step-8-publish-source-and-binary-distribution-packages">Step 8 : Publish Source and Binary Distribution Packages</h3>
+<h3 id="step-8-publish-source-and-binary-distribution-packages">Step 8 : Publish Source and Binary Distribution Packages<a class="headerlink" href="#step-8-publish-source-and-binary-distribution-packages" title="Permanent link">¶</a></h3>
<p>First of all, create a new directory on people.apache.org/public_html to store the pacckages :</p>
<div class="codehilite"><pre>$ <span class="n">ssh</span> <span class="n">people</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span>
$ <span class="n">mkdir</span> <span class="n">public_html</span><span class="o">/</span><span class="n">fortress</span><span class="o">-</span><span class="n">core</span><span class="o">-<</span><span class="n">version</span><span class="o">></span>
@@ -640,7 +651,7 @@ $ <span class="n">scp</span> <span class
</pre></div>
-<h2 id="step-9-voting-a-release">Step 9 : Voting a release</h2>
+<h2 id="step-9-voting-a-release">Step 9 : Voting a release<a class="headerlink" href="#step-9-voting-a-release" title="Permanent link">¶</a></h2>
<p>Once the tarballs have been created, and the binaries available in Nexus, a vote can be launched. Simply send a mail on the dev@directory.apache.org mailing list describing the new release.</p>
<p>Here is how you send a [VOTE] mail on the dev mailing list :</p>
<div class="codehilite"><pre><span class="n">Hi</span><span class="p">,</span>
@@ -678,7 +689,7 @@ $ <span class="n">scp</span> <span class
<p>The vote will be open for 72 hours. Once the delay is over, collect the votes, and count the binding +1/-1. If the vote is positive, then we can release.</p>
-<h3 id="step-11-close-the-vote">Step 11 : Close the vote</h3>
+<h3 id="step-11-close-the-vote">Step 11 : Close the vote<a class="headerlink" href="#step-11-close-the-vote" title="Permanent link">¶</a></h3>
<p>You can officially close the vote now. There are some more steps to fulfill :</p>
<ul>
<li>Release the project on https://repository.apache.org</li>
@@ -698,7 +709,7 @@ $
</pre></div>
-<h3 id="step-12-deploy-web-reports-javadoc-and-jxr">Step 12: Deploy Web Reports (JavaDoc and JXR)</h3>
+<h3 id="step-12-deploy-web-reports-javadoc-and-jxr">Step 12: Deploy Web Reports (JavaDoc and JXR)<a class="headerlink" href="#step-12-deploy-web-reports-javadoc-and-jxr" title="Permanent link">¶</a></h3>
<p>The javadoc and xref files have been generated in step 6, it's now time to push them into the production site. They are generated in the following directory :</p>
<div class="codehilite"><pre><span class="n">target</span><span class="o">/</span><span class="n">checkout</span><span class="o">/</span><span class="n">target</span><span class="o">/</span><span class="n">site</span>
</pre></div>
@@ -753,9 +764,9 @@ $ <span class="n">vi</span> <span class=
</pre></div>
-<h3 id="step-13-wait-24-hours">Step 13: Wait 24 hours</h3>
+<h3 id="step-13-wait-24-hours">Step 13: Wait 24 hours<a class="headerlink" href="#step-13-wait-24-hours" title="Permanent link">¶</a></h3>
<p>We have to wait at least 24 hours for all mirrors to retrieve the uploaded files before making any announcement. I'd recommend you to wait for 48 hours because some mirrors might lag due to various issues.</p>
-<h3 id="step-14-update-the-links-in-web-site">Step 14: Update the Links in Web Site</h3>
+<h3 id="step-14-update-the-links-in-web-site">Step 14: Update the Links in Web Site<a class="headerlink" href="#step-14-update-the-links-in-web-site" title="Permanent link">¶</a></h3>
<p>Update the links to new distributions in [Downloads] page.</p>
<p>There are a few places to modify :
- /lib/path.pm : update the $version_fortress variable with the new version.
@@ -763,9 +774,9 @@ $ <span class="n">vi</span> <span class=
- /content/fortress/news.mdtext : add the news on top of thise page
- /content/fortress/download-old-versions.mdtext : add a new line on top of the array, which refers to the latest version before the new one</p>
<p>Commit the changes, and publish the web site, you are done !</p>
-<h3 id="step-15-wait-another-24-hours">Step 15: Wait another 24 hours</h3>
+<h3 id="step-15-wait-another-24-hours">Step 15: Wait another 24 hours<a class="headerlink" href="#step-15-wait-another-24-hours" title="Permanent link">¶</a></h3>
<p>We need to wait until any changes made in the web site and metadata file(s) go live.</p>
-<h3 id="step-16-announce-the-new-release">Step 16: Announce the New Release</h3>
+<h3 id="step-16-announce-the-new-release">Step 16: Announce the New Release<a class="headerlink" href="#step-16-announce-the-new-release" title="Permanent link">¶</a></h3>
<p>An announcement message can be sent to [mailto:announce@apache.org], [mailto:announce@apachenews.org], [mailto:users@mina.apache.org] and [mailto:dev@mina.apache.org]. Please note that announcement messages are rejected unless your from-address ends with <code>@apache.org</code>. Plus, you shouldn't forget to post a news to the MINA site main page.</p>
Modified: websites/staging/directory/trunk/content/fortress/download/download-sources.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/download/download-sources.html (original)
+++ websites/staging/directory/trunk/content/fortress/download/download-sources.html Sun Jul 5 22:34:35 2015
@@ -242,21 +242,21 @@
<div class="preformatted">
<div class="preformattedContent">
<pre>$ pgpk -a KEYS
-$ pgpv fortress-core-1.0.0-M30-source-release.zip.asc</pre>
+$ pgpv fortress-core-1.0.0-M31-source-release.zip.asc</pre>
</div>
</div>
or
<div class="preformatted">
<div class="preformattedContent">
<pre>$ pgp -ka KEYS
-$ pgp fortress-core-1.0.0-M30-source-release.zip.asc</pre>
+$ pgp fortress-core-1.0.0-M31-source-release.zip.asc</pre>
</div>
</div>
or
<div class="preformatted">
<div class="preformattedContent">
<pre>$ gpg --import KEYS
-$ gpg --verify fortress-core-1.0.0-M30-source-release.zip.asc</pre>
+$ gpg --verify fortress-core-1.0.0-M31-source-release.zip.asc</pre>
</div>
</div>
Modified: websites/staging/directory/trunk/content/fortress/downloads.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/downloads.html (original)
+++ websites/staging/directory/trunk/content/fortress/downloads.html Sun Jul 5 22:34:35 2015
@@ -160,14 +160,25 @@
-<h1 id="downloads">Downloads</h1>
-<h2 id="jar-download">Jar Download</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="downloads">Downloads<a class="headerlink" href="#downloads" title="Permanent link">¶</a></h1>
+<h2 id="jar-download">Jar Download<a class="headerlink" href="#jar-download" title="Permanent link">¶</a></h2>
<p>The Apache Fortress Core is distributed as a jar.</p>
<ul>
<li><img alt="Download" src="../images/download-archive.png" /> <a href="download/download-archive.html">Download Archive JAR</a></li>
<li><img alt="Download" src="../images/download-sources.png" /> <a href="download/download-sources.html">Download Sources</a></li>
</ul>
-<h2 id="maven-dependency">Maven Dependency</h2>
+<h2 id="maven-dependency">Maven Dependency<a class="headerlink" href="#maven-dependency" title="Permanent link">¶</a></h2>
<p>The Apache Fortress Core is also available as a Maven dependency:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.directory.fortress<span class="nt"></groupId></span>
Modified: websites/staging/directory/trunk/content/fortress/history.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/history.html (original)
+++ websites/staging/directory/trunk/content/fortress/history.html Sun Jul 5 22:34:35 2015
@@ -160,7 +160,18 @@
-<h1 id="history">History</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="history">History<a class="headerlink" href="#history" title="Permanent link">¶</a></h1>
<p>To be added soon...</p>
Modified: websites/staging/directory/trunk/content/fortress/index.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/index.html (original)
+++ websites/staging/directory/trunk/content/fortress/index.html Sun Jul 5 22:34:35 2015
@@ -180,7 +180,18 @@
- <div class="news"><h1 id="news">News</h1>
+ <div class="news"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">¶</a></h1>
<h2 class="news">Apache Fortress Core 1.0-RC40 released !<em>posted on April 15th, 2015</em></h2>
<p>The Apache Directory Project is proud to announce th very first release of Fortress-core, the core library of the Fortress project.</p>
@@ -189,7 +200,7 @@
<p>It's still a release-candidate, and will be follow soon by a GA.</p>
<p>We are working on releasing Fortress-realm, Fortress-enMasse and Fortress-Commander in the next few weeks.</p>
<p>Here is the list of fixed issues since the code has been injected into the ASF repository:</p>
-<h2 id="bugs">Bugs :</h2>
+<h2 id="bugs">Bugs :<a class="headerlink" href="#bugs" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>6<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>6<span class="p">)</span> <span class="o">-</span> <span class="n">delPermObjs</span> <span class="n">causes</span> <span class="n">LDAP</span> 80 <span class="n">error</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>8<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>8<span class="p">)</span> <span class="o">-</span> <span class="n">Add</span> <span class="n">SSD</span> <span class="n">Constraint</span> <span class="n">check</span> <span class="n">to</span> <span class="n">updateRole</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>9<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>9<span class="p">)</span> <span class="o">-</span> <span class="n">CreateSession</span> <span class="n">error</span> <span class="n">on</span> <span class="n">ApacheDS</span> <span class="n">and</span> <span class="n">Ubuntu</span> 32
@@ -213,7 +224,7 @@
</pre></div>
-<h2 id="improvements">Improvements :</h2>
+<h2 id="improvements">Improvements :<a class="headerlink" href="#improvements" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>7<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>7<span class="p">)</span> <span class="o">-</span> <span class="n">Enhance</span> <span class="n">Role</span> <span class="n">Assignment</span> <span class="n">Func</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>22<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>22<span class="p">)</span> <span class="o">-</span> <span class="n">Switch</span> <span class="n">to</span> <span class="n">junit</span> 4<span class="p">.</span>11
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>23<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>23<span class="p">)</span> <span class="o">-</span> <span class="n">Make</span> <span class="n">the</span> <span class="n">PasswordPolicy</span> <span class="n">code</span> <span class="n">to</span> <span class="n">work</span> <span class="n">with</span> <span class="n">ApacheDS</span>
@@ -240,13 +251,13 @@
</pre></div>
-<h2 id="new-features">New Features :</h2>
+<h2 id="new-features">New Features :<a class="headerlink" href="#new-features" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>50<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>50<span class="p">)</span> <span class="o">-</span> <span class="n">Add</span> <span class="n">password</span> <span class="n">policy</span> <span class="n">support</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>78<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>78<span class="p">)</span> <span class="o">-</span> <span class="n">add</span> <span class="n">deserializer</span> <span class="n">to</span> <span class="n">realm</span> <span class="n">policymgr</span>
</pre></div>
-<h2 id="tasks">Tasks :</h2>
+<h2 id="tasks">Tasks :<a class="headerlink" href="#tasks" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>2<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>2<span class="p">)</span> <span class="o">-</span> <span class="n">Fulfill</span> <span class="n">the</span> <span class="n">IP</span> <span class="n">Clearance</span> <span class="n">form</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>30<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>30<span class="p">)</span> <span class="o">-</span> <span class="n">UnboundID</span> <span class="n">SDK</span> <span class="n">removal</span> <span class="n">preparations</span>
<span class="o">*</span> <span class="p">[</span><span class="n">FC</span><span class="o">-</span>40<span class="p">](</span><span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">issues</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jira</span><span class="o">/</span><span class="n">browse</span><span class="o">/</span><span class="n">FC</span><span class="o">-</span>40<span class="p">)</span> <span class="o">-</span> <span class="n">Use</span> <span class="n">the</span> <span class="n">LDAP</span> <span class="n">API</span> <span class="n">constants</span> <span class="n">instead</span> <span class="n">of</span> <span class="n">GlobalIDs</span> <span class="n">constants</span> <span class="n">when</span> <span class="n">possible</span>
Modified: websites/staging/directory/trunk/content/fortress/installation.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation.html Sun Jul 5 22:34:35 2015
@@ -160,7 +160,18 @@
-<h1 id="installation-guides">Installation guides</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="installation-guides">Installation guides<a class="headerlink" href="#installation-guides" title="Permanent link">¶</a></h1>
<p>The Installation guides show you how to do a base install of Fortress, using either ApacheDS or OpenLDAP:</p>
<ul>
<li><a href="installation/apacheds.html">Installation Guide for ApacheDS</a></li>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds.html Sun Jul 5 22:34:35 2015
@@ -160,9 +160,20 @@
-<h1 id="apacheds-installation-guide">ApacheDS Installation guide</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apacheds-installation-guide">ApacheDS Installation guide<a class="headerlink" href="#apacheds-installation-guide" title="Permanent link">¶</a></h1>
<p>Provide instructions to install an <strong>ApacheDS</strong> instance and setup for use with <strong>Fortress</strong>. In this configuration, there is an <strong>ApacheDS</strong> server running on a machine (<strong>ApacheDS Host</strong>) and <strong>Fortress</strong> agent which will be installed on a client machine (<strong>Fortress Host</strong>). Note that those two hosts can be shared - and this is such a configuration that we are going to use in this document.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h2>
<p>There a few mandatory elements that need to be installed on the <strong>ApacheDS Host</strong> :</p>
<ul>
<li>Java 7 or greated sdk</li>
@@ -175,18 +186,18 @@
<li>Git</li>
<li>Apache Directory Studio</li>
</ul>
-<h2 id="installing-apacheds">Installing ApacheDS</h2>
+<h2 id="installing-apacheds">Installing ApacheDS<a class="headerlink" href="#installing-apacheds" title="Permanent link">¶</a></h2>
<p>On the <strong>ApacheDS Host</strong> :</p>
<p>Follow the installation guide on <a href="http://directory.staging.apache.org/apacheds/downloads.html">the ApacheDS download pages</a> (each page has an installation description).</p>
<p>The base installation will install a server running on port <em>10389</em>, with a default user <em>uid=admin,ou=system</em> and the password <em>secret</em>. Please change those values !!!</p>
<p>Note that the server requires a Java 7 sdk to run.</p>
-<h2 id="installing-apache-directory-studio">Installing Apache Directory Studio</h2>
+<h2 id="installing-apache-directory-studio">Installing Apache Directory Studio<a class="headerlink" href="#installing-apache-directory-studio" title="Permanent link">¶</a></h2>
<p>On the <strong>Fortress Host</strong> :</p>
<p>We will install <strong>Apache Directory Studio</strong> which is a convenient tool when it comes to managing an <strong>LDAP</strong> server. Install using <a href="http://directory.apache.org/studio/downloads.html">the following documentation</a>. Again, each link contains directions on how to install this component.</p>
<p>Once installed, check the connection to the <strong>ApacheDS</strong> server installed during the previous step. Create a <em>connection</em>, set the <em>hostName</em> and <em>port</em> to be those where you installed the <strong>ApacheDS</strong> server, then check the Network Parameter, ensure no errors.</p>
<p>Check that the credentials you have set (defaulting to <em>uid=admin,ou=system</em> and <em>secret</em>) using <em>Simple Authentication</em>, and clicking on <em>Check Authentication</em> : work also.</p>
<p>The complete description of the steps are found <a href="http://directory.apache.org/studio/users-guide/ldap_browser/gettingstarted_create_connection.html">on this page</a></p>
-<h2 id="installing-fortress-core">Installing Fortress Core</h2>
+<h2 id="installing-fortress-core">Installing Fortress Core<a class="headerlink" href="#installing-fortress-core" title="Permanent link">¶</a></h2>
<p>Assuming that <strong>Git</strong>, <strong>Java 7</strong> and <strong>Apache Maven</strong> are installed on the <strong>Fortress Host</strong>, and that <strong>ApacheDS</strong> is running on the <strong>ApacheDS Host</strong>, we can now configure and install <strong>Fortress Core</strong> on the <strong>Fortress Host</strong></p>
<p>The setup will use your specific configuration to create everything needed on the LDAP server to operate <strong>Fortress</strong>. It will also inject specific schema elements into the ldap server; entries that are required for <em>Fortress</em> to work. Once done, the <strong>Fortress</strong> APIs are ready to use.</p>
<DIV class="info" markdown="1">
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/apacheds.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/apacheds.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/apacheds.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<p>These instructions are intended for new users who want to quickly learn how to install and test Apache Fortress and ApacheDS IAM software.</p>
<p>Follow the steps and ApacheDS will be installed, configured, loaded, and ready to use by <a href="section-IV.html">Section IV</a>. EnMasse Policy Server demo starts in <a href="section-VIII.html">Section VIII</a></p>
-<h3 id="table-of-contents">Table of contents</h3>
+<h3 id="table-of-contents">Table of contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h3>
<ul>
<li><a href="prerequisites.html">System Prerequisites</a></li>
<li><a href="guidelines.html">Guidelines and Tips for first-time users</a></li>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/guidelines.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/guidelines.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/guidelines.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="guidelines-and-tips-for-first-time-users">Guidelines and Tips for first-time users</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="guidelines-and-tips-for-first-time-users">Guidelines and Tips for first-time users<a class="headerlink" href="#guidelines-and-tips-for-first-time-users" title="Permanent link">¶</a></h1>
<p>In the document that follows, when you read [version] or [platform] substitute with current package info. For example - if the downloaded package version is 1.0.0 and platform is 'Debian Silver i386', the instructions show fortressBuilder-[platform]-[version].jar your file name would be fortressBuilder-Debian-Silver-i386-1.0.0.zip</p>
<p>Is your target machine windows? Go to <a href="../windows/windows.html">README-QUICKSTART-WINDOWS</a>.</p>
<p>The source code for this project is located here ./src.</p>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/prerequisites.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/prerequisites.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/prerequisites.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="system-prerequisites">System Prerequisites</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="system-prerequisites">System Prerequisites<a class="headerlink" href="#system-prerequisites" title="Permanent link">¶</a></h1>
<ul>
<li>Internet access to retrieve binary dependencies from online Maven repo.</li>
<li>Java SDK Version 7 or beyond installed to target environment</li>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-I.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-I.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-I.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h2 id="section-i-instructions-to-extract-and-configure-fortress-builder-package-to-target-system">Section I - Instructions to extract and configure Fortress Builder Package to Target System</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-i-instructions-to-extract-and-configure-fortress-builder-package-to-target-system">Section I - Instructions to extract and configure Fortress Builder Package to Target System<a class="headerlink" href="#section-i-instructions-to-extract-and-configure-fortress-builder-package-to-target-system" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>Obtain copy of directory-fortress-core and copy to hard drive on target server env.</p>
<p>https://git-wip-us.apache.org/repos/asf?p=directory-fortress-core.git;a=summary</p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Extract the zip. The location for archive can vary according to requirements. The location of package will be referred to as FORTRESS_HOME later on.</p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>Edit file named 'build.properties' and insert or change the following LDAP configuration parameters:</p>
<div class="codehilite"><pre><span class="n">ldap</span><span class="p">.</span><span class="n">server</span><span class="p">.</span><span class="n">type</span><span class="p">=</span><span class="n">apacheds</span>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-II.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-II.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-II.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h2 id="section-ii-instructions-to-run-the-fortress-ant-build">Section II - Instructions to run the Fortress Ant Build</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-ii-instructions-to-run-the-fortress-ant-build">Section II - Instructions to run the Fortress Ant Build<a class="headerlink" href="#section-ii-instructions-to-run-the-fortress-ant-build" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, edit the b.sh script to point to java home:</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">JAVA_HOME</span><span class="p">=</span><span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">jdk1</span><span class="p">.</span>7<span class="p">.</span>0<span class="n">_10</span>
</pre></div>
@@ -179,7 +190,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot3-edit-javahome.png" alt="Screenshot" width="766" height="111"/>
</CENTER></p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Run the distribution target:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">dist</span>
</pre></div>
@@ -189,7 +200,7 @@
<IMG src="../../images/Screenshot4-ant-dist.png" alt="Screenshot" width="766" height="58"/>
</CENTER></p>
<p>Note: The b.sh batch file referred to here uses Ant package that is local to Fortress quickstart package.</p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>Verify it ran correctly according to Ant:</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-III.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-III.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-III.html Sun Jul 5 22:34:35 2015
@@ -169,29 +169,40 @@
</div>
-<h2 id="section-iii-instructions-to-configure-apacheds-and-load-with-seed-data">Section III - Instructions to configure ApacheDS and load with seed data</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-iii-instructions-to-configure-apacheds-and-load-with-seed-data">Section III - Instructions to configure ApacheDS and load with seed data<a class="headerlink" href="#section-iii-instructions-to-configure-apacheds-and-load-with-seed-data" title="Permanent link">¶</a></h2>
<DIV class="note" markdown="1">
Important: This target reloads the ApacheDS configuration and data.
</DIV>
-<h3 id="step-1">Step 1</h3>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>Import Fortress ApacheDS schema into ApacheDS server using preferred ldif import tool. Fortress ApacheDS schema located here: FORTRESS_HOME/ldap/schema/apacheds-fortress.ldif</p>
<p>Screenshot of Apache Directory Studio import of Fortress schema file into ApacheDS: </p>
<p><CENTER>
<IMG src="../../images/Screenshot-Studio-Schema-Import.png" alt="Screenshot" width="766" height="461"/>
</CENTER></p>
<p>Note: The default for this setting is 'false' or disabled.</p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>The fortress 'init-apacheds' uses LDAPv3 to perform initial operations.</p>
<p>Edit build.properties, ensure the following line has been commented out:</p>
<p><CENTER>
<IMG src="../../images/Screenshot43-edit-disable-rest.png" alt="Screenshot"/>
</CENTER></p>
<p>Note: The default for this setting is 'false' or disabled.</p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, enter the following command from a system prompt:</p>
<p>./b.sh init-apacheds </p>
-<h3 id="step-4">Step 4</h3>
+<h3 id="step-4">Step 4<a class="headerlink" href="#step-4" title="Permanent link">¶</a></h3>
<p>Verify it ran correctly according to Ant.</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>
@@ -200,9 +211,9 @@
<p><CENTER>
<IMG src="../../images/Screenshot7-init-slapd-success.png" alt="Screenshot" width="766" height="101"/>
</CENTER></p>
-<h3 id="step-5">Step 5</h3>
+<h3 id="step-5">Step 5<a class="headerlink" href="#step-5" title="Permanent link">¶</a></h3>
<p>After above step completes, Symas ApacheDS will be installed, configured and loaded with fortress bootstrap config. This step also runs provisioning scripts which may be tailored according to requirements. Check out the xml load scripts in FORTRESS_HOME/ldap/setup folder.</p>
-<h3 id="step-5_1">Step 5</h3>
+<h3 id="step-5_1">Step 5<a class="headerlink" href="#step-5_1" title="Permanent link">¶</a></h3>
<p>Point your preferred LDAP browser, ours is Apache Directory Studio, to the installed directory. </p>
<p><To be completed></p>
<p><CENTER>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IV.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IV.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IV.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h2 id="section-iv-instructions-to-regression-test-fortress-and-apacheds-on-target-machine-optional">Section IV - Instructions to regression test Fortress and ApacheDS on target machine (optional)</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-iv-instructions-to-regression-test-fortress-and-apacheds-on-target-machine-optional">Section IV - Instructions to regression test Fortress and ApacheDS on target machine (optional)<a class="headerlink" href="#section-iv-instructions-to-regression-test-fortress-and-apacheds-on-target-machine-optional" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, enter the following command from a system prompt:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">test</span><span class="o">-</span><span class="n">full</span>
</pre></div>
@@ -180,7 +191,7 @@
<IMG src="../../images/Screenshot10-ant-test-init.png" alt="Screenshot"/>
</CENTER></p>
<p>Note: The Fortress regression tests will run for around 3 minutes.</p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Verify these tests ran with no ERRORS.</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>
@@ -189,7 +200,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot11-ant-test-success.png" alt="Screenshot" width="766" height="59"/>
</CENTER></p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>To re-run these tests: </p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">test</span><span class="o">-</span><span class="n">full</span>
</pre></div>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IX.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IX.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IX.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h2 id="section-xii-instructions-to-regression-test-enmasse-policy-server-on-target-machine-optional">Section XII - Instructions to regression test EnMasse Policy server on target machine (optional)</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-xii-instructions-to-regression-test-enmasse-policy-server-on-target-machine-optional">Section XII - Instructions to regression test EnMasse Policy server on target machine (optional)<a class="headerlink" href="#section-xii-instructions-to-regression-test-enmasse-policy-server-on-target-machine-optional" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>Edit file named 'build.properties' and enable REST protocol here:</p>
<div class="codehilite"><pre><span class="n">enable</span><span class="p">.</span><span class="n">mgr</span><span class="p">.</span><span class="n">impl</span><span class="p">.</span><span class="n">rest</span><span class="p">=</span><span class="n">true</span>
</pre></div>
@@ -188,9 +199,9 @@
<p><CENTER>
<IMG src="../../images/Screenshot41-enmasse-http-settings.png" alt="Screenshot" width="766" height="88"/>
</CENTER></p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Save and exit the text file editor</p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, enter the following command from a system prompt:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">test</span><span class="o">-</span><span class="n">full</span>
</pre></div>
@@ -201,7 +212,7 @@
<IMG src="../../images/Screenshot10-ant-test-init.png" alt="Screenshot"/>
</CENTER></p>
<p>Note: The EnMasse regression tests will run for around 20 minutes.</p>
-<h3 id="step-4">Step 4</h3>
+<h3 id="step-4">Step 4<a class="headerlink" href="#step-4" title="Permanent link">¶</a></h3>
<p>Verify these tests ran with no ERRORS.</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>
@@ -210,7 +221,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot43-ant-enmasse-test-success.png" alt="Screenshot"/>
</CENTER></p>
-<h3 id="step-5">Step 5</h3>
+<h3 id="step-5">Step 5<a class="headerlink" href="#step-5" title="Permanent link">¶</a></h3>
<p>This regression test may be rerun as often as necessary:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">test</span><span class="o">-</span><span class="n">full</span>
</pre></div>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-V.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-V.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-V.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h2 id="section-v-instructions-to-run-the-fortress-command-line-interpreter-cli-utility">Section V - Instructions to run the Fortress Command Line Interpreter (CLI) utility</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-v-instructions-to-run-the-fortress-command-line-interpreter-cli-utility">Section V - Instructions to run the Fortress Command Line Interpreter (CLI) utility<a class="headerlink" href="#section-v-instructions-to-run-the-fortress-command-line-interpreter-cli-utility" title="Permanent link">¶</a></h2>
<p>This command line tool provides an interactive session with the user based on a simple command line syntax.</p>
-<h3 id="step-1">Step 1</h3>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>To start the CLI, enter:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">cli</span>
</pre></div>
@@ -184,7 +195,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot14-cli.png" alt="Screenshot" width="766" height="78"/>
</CENTER></p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>enter the command:</p>
<div class="codehilite"><pre><span class="n">review</span> <span class="n">fuser</span> <span class="o">-</span><span class="n">u</span> <span class="n">demo</span>
</pre></div>
@@ -197,7 +208,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot16-cli-fuser.png" alt="Screenshot" width="766" height="682"/>
</CENTER></p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>To learn more about the CLI and what it can do, follow instructions in the command line interpreter reference manual in the javadoc located here:</p>
<div class="codehilite"><pre><span class="p">[</span><span class="n">Command</span> <span class="n">Line</span> <span class="n">Interpreter</span><span class="p">](</span><span class="n">link</span><span class="p">...)</span>
</pre></div>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VI.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VI.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VI.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h2 id="section-vi-instructions-to-run-fortress-console-optional">Section VI - Instructions to run Fortress Console (optional)</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-vi-instructions-to-run-fortress-console-optional">Section VI - Instructions to run Fortress Console (optional)<a class="headerlink" href="#section-vi-instructions-to-run-fortress-console-optional" title="Permanent link">¶</a></h2>
<p>For tasks like one-time setup of new users, password resets, searches the Fortress Console application can be used.</p>
-<h3 id="step-1">Step 1</h3>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, enter the following command from a system prompt:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">console</span>
</pre></div>
@@ -180,32 +191,32 @@
<p><CENTER>
<IMG src="../../images/Screenshot17-ant-console.png" alt="Screenshot" width="766" height="49"/>
</CENTER></p>
-<h3 id="some-console-screenshots">Some Console Screenshots...</h3>
-<h4 id="main-menu">Main Menu:</h4>
+<h3 id="some-console-screenshots">Some Console Screenshots...<a class="headerlink" href="#some-console-screenshots" title="Permanent link">¶</a></h3>
+<h4 id="main-menu">Main Menu:<a class="headerlink" href="#main-menu" title="Permanent link">¶</a></h4>
<p><CENTER>
<IMG src="../../images/Screenshot18-console-main.png" alt="Screenshot"/>
</CENTER></p>
-<h4 id="admin-manager-functions">Admin Manager Functions</h4>
+<h4 id="admin-manager-functions">Admin Manager Functions<a class="headerlink" href="#admin-manager-functions" title="Permanent link">¶</a></h4>
<p>Enter choice 1 and follow the screen prompts to edit RBAC data: </p>
<p><CENTER>
<IMG src="../../images/Screenshot19-console-admin.png" alt="Screenshot"/>
</CENTER></p>
-<h4 id="review-manager-functions">Review Manager Functions</h4>
+<h4 id="review-manager-functions">Review Manager Functions<a class="headerlink" href="#review-manager-functions" title="Permanent link">¶</a></h4>
<p>Enter choice 2 and follow the screen prompts to search RBAC data: </p>
<p><CENTER>
<IMG src="../../images/Screenshot20-console-review.png" alt="Screenshot"/>
</CENTER></p>
-<h4 id="access-manager-functions">Access Manager Functions</h4>
+<h4 id="access-manager-functions">Access Manager Functions<a class="headerlink" href="#access-manager-functions" title="Permanent link">¶</a></h4>
<p>Enter choice 3 and follow the screen prompts to test RBAC policies: </p>
<p><CENTER>
<IMG src="../../images/Screenshot21-console-access.png" alt="Screenshot"/>
</CENTER></p>
-<h4 id="delegated-admin-manager-functions">Delegated Admin Manager Functions</h4>
+<h4 id="delegated-admin-manager-functions">Delegated Admin Manager Functions<a class="headerlink" href="#delegated-admin-manager-functions" title="Permanent link">¶</a></h4>
<p>Enter choice 4 and follow the screen prompts to setup ARBAC delegated policies: </p>
<p><CENTER>
<IMG src="../../images/Screenshot22-console-deladmin.png" alt="Screenshot"/>
</CENTER></p>
-<h4 id="audit-manager-functions">Audit Manager Functions</h4>
+<h4 id="audit-manager-functions">Audit Manager Functions<a class="headerlink" href="#audit-manager-functions" title="Permanent link">¶</a></h4>
<p>Enter choice 8 and follow the screen prompts to search through the AUDIT log: </p>
<p><CENTER>
<IMG src="../../images/Screenshot23-console-audit.png" alt="Screenshot"/>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VII.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VII.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VII.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h2 id="section-vii-instructions-to-generate-and-view-javadoc-optional">Section VII - Instructions to generate and view Javadoc (optional)</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-vii-instructions-to-generate-and-view-javadoc-optional">Section VII - Instructions to generate and view Javadoc (optional)<a class="headerlink" href="#section-vii-instructions-to-generate-and-view-javadoc-optional" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>Run the javadoc target:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">javadoc</span>
</pre></div>
@@ -179,19 +190,19 @@
<p><CENTER>
<IMG src="../../images/Screenshot24-ant-javadoc.png" alt="Screenshot" width="766" height="61"/>
</CENTER></p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Navigate to where docs are generated:</p>
<p><CENTER>
<IMG src="../../images/Screenshot25-javadoc-listing.png" alt="Screenshot" width="766" height="114"/>
</CENTER></p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>Open 'index.html' using your preferred HTML Browser :</p>
<p><CENTER>
<IMG src="../../images/Screenshot26-javadoc.png" alt="Screenshot" width="766" height="463"/>
</CENTER></p>
-<h3 id="step-4">Step 4</h3>
+<h3 id="step-4">Step 4<a class="headerlink" href="#step-4" title="Permanent link">¶</a></h3>
<p>The javadoc provides coverage of the Fortress APIs and also provides explanations on how RBAC, ARBAC, PW Policies and Audit work.</p>
-<h3 id="step-5">Step 5</h3>
+<h3 id="step-5">Step 5<a class="headerlink" href="#step-5" title="Permanent link">¶</a></h3>
<p>Good places to start learning about Fortress : </p>
<ul>
<li>Fortress Manager Summary</li>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VIII.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VIII.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VIII.html Sun Jul 5 22:34:35 2015
@@ -169,14 +169,25 @@
</div>
-<h2 id="section-viii-instructions-to-install-enmasse-policy-server-demo-optional">Section VIII - Instructions to install EnMasse Policy Server Demo (optional)</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-viii-instructions-to-install-enmasse-policy-server-demo-optional">Section VIII - Instructions to install EnMasse Policy Server Demo (optional)<a class="headerlink" href="#section-viii-instructions-to-install-enmasse-policy-server-demo-optional" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>Run the install-enmasse-demo target:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">install</span><span class="o">-</span><span class="n">enmasse</span><span class="o">-</span><span class="n">demo</span>
</pre></div>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Verify it ran correctly according to Ant.</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>
@@ -185,7 +196,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot42-install-enmasse-demo-success.png" alt="Screenshot" width="766" height="278"/>
</CENTER></p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>After above step completes, Fortress EnMasse will be installed </p>
Modified: websites/staging/directory/trunk/content/fortress/installation/apacheds/section-X.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/apacheds/section-X.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/apacheds/section-X.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h2 id="section-x-more-utilities">Section X - More Utilities</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-x-more-utilities">Section X - More Utilities<a class="headerlink" href="#section-x-more-utilities" title="Permanent link">¶</a></h2>
<p>Other execution targets you may find useful:</p>
<ul>
<li>'test-samples' - contains examples of how the Fortress API's work check out the following javadoc for more info on the samples package: Samples Javadoc </li>
Modified: websites/staging/directory/trunk/content/fortress/installation/linux/guidelines.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/linux/guidelines.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/linux/guidelines.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="guidelines-and-tips-for-first-time-users">Guidelines and Tips for first-time users</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="guidelines-and-tips-for-first-time-users">Guidelines and Tips for first-time users<a class="headerlink" href="#guidelines-and-tips-for-first-time-users" title="Permanent link">¶</a></h1>
<p>In the document that follows, when you read [version] or [platform] substitute with current package info. For example - if the downloaded package version is 1.0.0 and platform is 'Debian Silver i386', the instructions show fortressBuilder-[platform]-[version].jar your file name would be fortressBuilder-Debian-Silver-i386-1.0.0.zip</p>
<p>Is your target machine windows? Go to <a href="../windows/windows.html">README-QUICKSTART-WINDOWS</a>.</p>
<p>The source code for this project is located here ./src.</p>
Modified: websites/staging/directory/trunk/content/fortress/installation/linux/linux.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/linux/linux.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/linux/linux.html Sun Jul 5 22:34:35 2015
@@ -179,9 +179,20 @@
</div>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<p>The intent of this document is to help new users with Apache Fortress IAM™ software using one of the the linux QUICKSTART packages located <a href="http://directory.apache.org/fortress/download.html">here</a></p>
-<p>For instructions on how to get Fortress connected to an existing OpenLDAP instance, follow the instructions inside SECTION 6 of this document: <a href="link%20to%20provide">README.txt</a></p>
-<h3 id="table-of-contents">Table of contents</h3>
+<p>For instructions on how to get Fortress connected to an existing OpenLDAP instance, follow the instructions inside SECTION 6 of this document: <a href="link to provide">README.txt</a></p>
+<h3 id="table-of-contents">Table of contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h3>
<ul>
<li><a href="prerequisites.html">System Prerequisites</a></li>
<li><a href="guidelines.html">Guidelines and Tips for first-time users</a></li>
Modified: websites/staging/directory/trunk/content/fortress/installation/linux/prerequisites.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/linux/prerequisites.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/linux/prerequisites.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h1 id="system-prerequisites">System Prerequisites</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="system-prerequisites">System Prerequisites<a class="headerlink" href="#system-prerequisites" title="Permanent link">¶</a></h1>
<ul>
<li>Internet access to retrieve binary dependencies from online Maven repo.</li>
<li>Java SDK Version 7 or beyond installed to target environment</li>
Modified: websites/staging/directory/trunk/content/fortress/installation/linux/section-I.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/linux/section-I.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/linux/section-I.html Sun Jul 5 22:34:35 2015
@@ -179,7 +179,18 @@
</div>
-<h2 id="section-i-instructions-to-download-extract-and-configure-fortress-builder-package-to-target-system">Section I - Instructions to download, extract and configure Fortress Builder Package to Target System</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-i-instructions-to-download-extract-and-configure-fortress-builder-package-to-target-system">Section I - Instructions to download, extract and configure Fortress Builder Package to Target System<a class="headerlink" href="#section-i-instructions-to-download-extract-and-configure-fortress-builder-package-to-target-system" title="Permanent link">¶</a></h2>
<ul>
<li>Download one of the linux packages from here: iamfortress.org/download</li>
<li>Copy fortressBuilder-[platform]-[version].zip to hard drive on target server env.</li>
Modified: websites/staging/directory/trunk/content/fortress/installation/linux/section-II.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/installation/linux/section-II.html (original)
+++ websites/staging/directory/trunk/content/fortress/installation/linux/section-II.html Sun Jul 5 22:34:35 2015
@@ -179,8 +179,19 @@
</div>
-<h2 id="section-ii-instructions-to-run-the-fortress-ant-build">Section II - Instructions to run the Fortress Ant Build</h2>
-<h3 id="step-1">Step 1</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="section-ii-instructions-to-run-the-fortress-ant-build">Section II - Instructions to run the Fortress Ant Build<a class="headerlink" href="#section-ii-instructions-to-run-the-fortress-ant-build" title="Permanent link">¶</a></h2>
+<h3 id="step-1">Step 1<a class="headerlink" href="#step-1" title="Permanent link">¶</a></h3>
<p>From FORTRESS_HOME root folder, edit the b.sh script to point to java home:</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">JAVA_HOME</span><span class="p">=</span><span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">jdk1</span><span class="p">.</span>7<span class="p">.</span>0<span class="n">_10</span>
</pre></div>
@@ -189,7 +200,7 @@
<p><CENTER>
<IMG src="../../images/Screenshot3-edit-javahome.png" alt="Screenshot" width="766" height="111"/>
</CENTER></p>
-<h3 id="step-2">Step 2</h3>
+<h3 id="step-2">Step 2<a class="headerlink" href="#step-2" title="Permanent link">¶</a></h3>
<p>Run the distribution target:</p>
<div class="codehilite"><pre><span class="o">./</span><span class="n">b</span><span class="p">.</span><span class="n">sh</span> <span class="n">dist</span>
</pre></div>
@@ -199,7 +210,7 @@
<IMG src="../../images/Screenshot4-ant-dist.png" alt="Screenshot" width="766" height="58"/>
</CENTER></p>
<p>Note: The b.sh batch file referred to here uses Ant package that is local to Fortress quickstart package.</p>
-<h3 id="step-3">Step 3</h3>
+<h3 id="step-3">Step 3<a class="headerlink" href="#step-3" title="Permanent link">¶</a></h3>
<p>Verify it ran correctly according to Ant:</p>
<div class="codehilite"><pre><span class="n">BUILD</span> <span class="n">SUCCESSFUL</span>
</pre></div>