Author: buildbot
Date: Thu Oct 31 14:54:10 2013
New Revision: 884957

Log:
Staging update by buildbot for ace

Modified:
    websites/staging/ace/trunk/content/   (props changed)
    websites/staging/ace/trunk/content/dev-doc/configuring-relay-servers.html

Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 31 14:54:10 2013
@@ -1 +1 @@
-1537514
+1537515

Modified: 
websites/staging/ace/trunk/content/dev-doc/configuring-relay-servers.html
==============================================================================
--- websites/staging/ace/trunk/content/dev-doc/configuring-relay-servers.html 
(original)
+++ websites/staging/ace/trunk/content/dev-doc/configuring-relay-servers.html 
Thu Oct 31 14:54:10 2013
@@ -163,6 +163,18 @@
       <h1>Configuring and using ACE relay servers</h1>
       <div class="clear"></div>
       <div id="content"><p>When using Apache ACE in a large deployment 
scenario, in which many targets need to be provisioned, it might be necessary 
to scale the number of servers with additional relay servers. This document 
explains how to configure such relay servers for ACE. </p>
+<div class="toc">
+<ul>
+<li><a href="#overview">Overview</a></li>
+<li><a href="#log-synchronisation-between-target-and-relay">Log 
synchronisation between target and relay</a></li>
+<li><a href="#log-synchronisation-between-relay-and-main-server">Log 
synchronisation between relay and main server</a></li>
+<li><a href="#deployment-provider">Deployment provider</a></li>
+<li><a href="#deployment-servlet">Deployment servlet</a></li>
+<li><a href="#task-scheduler">Task scheduler</a></li>
+<li><a href="#target-configuration">Target configuration</a></li>
+<li><a href="#notes">Notes</a></li>
+</ul>
+</div>
 <h2 id="overview">Overview</h2>
 <p>In ACE, each target only talks to a single ACE server at a time. From this 
perspective, an ACE server only serves two major tasks: </p>
 <ol>


Reply via email to