mcardle     2006/01/05 15:45:39 CET

  Modified files:
    core/src/webapp/html/startup howto_esi.html 
  Log:
  * update for portrange
  
  Revision  Changes    Path
  1.13      +22 -20    jahia/core/src/webapp/html/startup/howto_esi.html
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia/core/src/webapp/html/startup/howto_esi.html.diff?r1=1.12&r2=1.13&f=h
  
  
  
  Index: howto_esi.html
  ===================================================================
  RCS file: 
/home/cvs/repository/jahia/core/src/webapp/html/startup/howto_esi.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- howto_esi.html    15 Dec 2005 16:35:39 -0000      1.12
  +++ howto_esi.html    5 Jan 2006 14:45:39 -0000       1.13
  @@ -159,7 +159,7 @@
   # Note that the first port defined in esiServerPorts will also be used to 
generate the site URL;
   # please refer to the declaration of siteServerNameTestURLExpr below for 
more details.
   <br/>
  -# ESI invalidation messages can be either send via HTML reponse 
piggy-backing ( i.e. 
  +# ESI invalidation messages can be either send via HTML reponse 
piggy-backing ( i.e.
   # they are appended to Jahia HTML responses) or via a direct SOAP 
transmission to the ESI
   # server (default):
   esiUsePiggyBackInvalidation                                           = false
  @@ -168,6 +168,8 @@
   esiUseCookieUserIdentifiers                                = false
   #encrypt the user specific identifiers
   esiEncryptUserIdentifiers                                  = true
  +# This is the port range used to transfer the content of the invalidation 
messages
  +esiInvalidationPortRange                                = 6000-6500
   
   [...]
   </pre>
  @@ -186,29 +188,29 @@
   &lt;server className="net.sf.j2ep.servers.BaseServer"
                domainName="localhost:8080"
                isRewriting="true"&gt;
  -                         
  +
                &lt;rule className="net.sf.j2ep.rules.AcceptEverythingRule"/&gt;
  -&lt;/server&gt;</pre>                                                
  +&lt;/server&gt;</pre>
                                             <p>by : </p>
                                                        <pre class="code">
  -&lt;cluster-server className="net.sf.j2ep.servers.RoundRobinCluster" 
isRewriting="true" &gt;  
  - 
  -     &lt;server domainName="<span 
class="style1">YOUR_JAHIA_SERVER1:YOUR_JAHIA_SERVER2_PORT</span>"  /&gt;  
  - 
  -     &lt;server domainName="<span 
class="style1">YOUR_JAHIA_SERVER2_IP:YOUR_JAHIA_SERVER2_PORT</span>" /&gt;  
  - 
  -     &lt;rule className="net.sf.j2ep.rules.AcceptEverythingRule" /&gt; 
  - 
  +&lt;cluster-server className="net.sf.j2ep.servers.RoundRobinCluster" 
isRewriting="true" &gt;
  +
  +     &lt;server domainName="<span 
class="style1">YOUR_JAHIA_SERVER1:YOUR_JAHIA_SERVER2_PORT</span>"  /&gt;
  +
  +     &lt;server domainName="<span 
class="style1">YOUR_JAHIA_SERVER2_IP:YOUR_JAHIA_SERVER2_PORT</span>" /&gt;
  +
  +     &lt;rule className="net.sf.j2ep.rules.AcceptEverythingRule" /&gt;
  +
   &lt;/cluster-server&gt;</pre>
  -                                                     However this feature 
has not been thoroughly tested.<br /> 
  +                                                     However this feature 
has not been thoroughly tested.<br />
                                                 <br/>To obtain the same 
behaviour with a hardware load-balancer (like F5)
  -                                                     , use the configuration 
described on point 4, and replace the "YOUR_JAHIA_SERVER_IP:8080" value by the 
address of the 
  -                                                     hardware load-balancer. 
The load-balancer will then reroute the requests to multiple Jahia servers. 
  +                                                     , use the configuration 
described on point 4, and replace the "YOUR_JAHIA_SERVER_IP:8080" value by the 
address of the
  +                                                     hardware load-balancer. 
The load-balancer will then reroute the requests to multiple Jahia servers.
                                                        Make sure sticky 
sessions are enabled on the load-balancer.<br/><br/>
                                           </li>
                                           <li>Run the ESI server with the 
following command (or use the &quot;Start Jahia Cache Server&quot; icon in your 
Windows Start menu):<br/>
                                             <br/>
  -                                             
  +
                                                
<i>\YOUR_ESI_DIR\tomcat\bin\catalina start</i> (windows)<br/>
                                                <br/>
                                           </li>
  @@ -221,10 +223,10 @@
                                           </li>
                                           <li>You can now browse Jahia via the 
ESI server at http://<span class="code"><span 
class="style1">YOUR_ESI_SERVER_IP</span></span>:8081/jahia/Jahia. Note that 
Jahia is still accessible at http://<span class="code"><span 
class="style1">YOUR_JAHIA_SERVER_IP</span></span>:8080/jahia/Jahia.<br />
                                           </li>
  -                                        <li> If you need debug information 
on all ESI related processing, you can change to "debug" level all ESI related 
  -                                             classes in 
\YOUR_JAHIA_DIR\tomcat\webapps\jahia\WEB-INF\etc\config\log4j.xml.<br /> 
  +                                        <li> If you need debug information 
on all ESI related processing, you can change to "debug" level all ESI related
  +                                             classes in 
\YOUR_JAHIA_DIR\tomcat\webapps\jahia\WEB-INF\etc\config\log4j.xml.<br />
                                                <br/>
  -                                             You can also activate debug 
mode on the ESI server by replacing "info" values by "debug" in 
  +                                             You can also activate debug 
mode on the ESI server by replacing "info" values by "debug" in
                                                
\YOUR_ESI_DIR\tomcat\webapps\ROOT\WEB-INF\log4j.xml. You will need to restart 
the ESI server
                                                for any changes to be taken 
into account. <br/></li>
                                                <li> To access the 
administration page of the ESI server, please go to http://<span 
class="style1">YOUR_ESI_SERVER_IP</span>:8081/esiadmin/index.jsp or go to 
&quot;Server and Cache Status&quot; section in Jahia's administration menu. 
<br/>
  @@ -235,9 +237,9 @@
   <strong>Limitations :</strong><br/>
   <br/>
   Currently ESI cache invalidation may still be buggy, so you may need to use 
the "cache/offonce" parameter in the URL
  -to force a refresh of the cache.<br /> 
  +to force a refresh of the cache.<br />
   <br/>
  -Other attributes will be added to JESI tags to allow fine tuning of the ESI 
server behaviour when errors on 
  +Other attributes will be added to JESI tags to allow fine tuning of the ESI 
server behaviour when errors on
   fragments are encountered. <br />
   <br />
   Performance should also be improved in future releases of the ESI 
server.<br/>
  

Reply via email to