mromy 2005/12/01 14:48:15 CET
Modified files:
core/src/webapp/html/startup howto_cluster.html
Log:
- udpated
Revision Changes Path
1.16 +38 -11 jahia/core/src/webapp/html/startup/howto_cluster.html
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia/core/src/webapp/html/startup/howto_cluster.html.diff?r1=1.15&r2=1.16&f=h
Index: howto_cluster.html
===================================================================
RCS file: /cvs/jahia/core/src/webapp/html/startup/howto_cluster.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- howto_cluster.html 30 Nov 2005 10:16:31 -0000 1.15
+++ howto_cluster.html 1 Dec 2005 13:48:15 -0000 1.16
@@ -46,9 +46,6 @@
font-family: Arial, Helvetica, sans-serif;
font-size: 12px;
font-weight: normal;
- list-style-type: lower-roman;
- list-style-position: outside;
- display: list-item;
}
DIV.box { width : 150px;
color : #666666;
@@ -131,12 +128,16 @@
<h1>How to setup clustering, database content storage of large data
and transactions </h1>
<p>
If you want to activate the
clustering configuration, you should
- modify a few configuration
files. </p>
+ modify a few configuration files.</p>
+ <p>
+ <span class="red">One very
important thing is to make sure the time is the same on all nodes of the
cluster.
+ Messages sent between
nodes to synchronize the state of the cluster use time stamps, so if nodes are
not
+ precisely
time-synchronized, problems will occur.<br/>We recommend setting up an NTP
client with frequent updates
+ on each server or any
other mechanism to ensure the time is the same on all servers.</span>
+ </p>
<h2>I - To activate in base content storage</h2>
To setup in base content storage, you
just have to select "in base storage" during the
configuration wizard, in the database
advanced configuration screen.<br/><br/>
- <b>Please note that currently,
in base content storage does not work with PostgreSQL. This will be fixed
- before the final
release.</b><br/>
<br/>
<span class="red">If you are using
MySQL, the <i>max_allowed_packet</i> parameter in the <strong>my.ini</strong>
will limit the maximum size
of a file to be stored in the database,
so make sure that it is configured to allow large enough files for your
needs.</span><br/><br/>
@@ -159,7 +160,7 @@
<li>Install the first instance
as for a stand-alone configuration.<br/>
During the configuration
wizard, select "in base content storing" if you prefer to store all
data in the
database. After configuration wizard is completed and installaton successful,
shutdown this instance of
- Jahia.<br/>
+ Jahia.
</li>
<li>Delete all the tables
created during the installation of the first instance of Jahia. Depending on
the database
used and if more
convenient, you may drop the database used and re-create an empty database with
the same name. When
@@ -171,7 +172,8 @@
by tomcat as well as
the shutdown port. This should be changed in the <i>tomcat/conf/server.xml</i>
file.<br/>
After configuration
wizard is completed and installaton successful, shutdown this second instance of
Jahia.<br/>
- </li><li>If you have not
selected in base content storage, you will need to have the directories
containing the large text files and
+ </li><li><h4>Sharing files and
bigtexts stored on disk</h4>
+ If you
have not selected in base content storage, you will need to have the
directories containing the large text files and
the files uploaded
through Jahia on a shared disk space. At least the following directories will
need to be shared amongst
all Jahia instances:
<br/>
<br/>
@@ -189,7 +191,12 @@
<i>F\:/directory/content/bigtext/</i><br/>
<i>F\:/directory/content/slide/</i><br/><br/>
if you
are doing a configuration under windows<br/><br/>
- <br>
+
<h4>Sharing templates</h4>
+ You may
also want to share the directory containing the templates, so that when you do
a modification on one templates, it is
+
simultaneously taken into account by all nodes. The following directory should
be shared :<br/>
+ <br/>
+
<i>jahia/jsp/jahia/templates/</i><br/>
+
<h4>Sharing Lucene search indexes</h4>
You
also need to share between all Jahia instances the directory where Lucene
stores its indexes. This can be configured in the
<i>jahia\WEB-INF\etc\spring\applicationcontext-basejahiaconfig.xml</i> file
:<br/><br/>
@@ -209,7 +216,12 @@
processingServer = true
</pre>
When set to
"true", the Jahia node WILL process these kinds of operations. If set to
"false", these operations will be handled
- to another
Jahia node which has been configured as a processing server. By default this
parameter is set to "true".<br/><br/>
+ to another
Jahia node which has been configured as a processing server. By default this
parameter is set to "true".<br/>
+
<h4>Sharing webapps</h4>
+ Web
application needs to support clustering on their own to be able to fully work
in a clustered Jahia environnement. Once a
+ webapp
has been deployed on a node (the deployed webapp will be available in
<i>tomcat\webapps</i>), you will need to manually copy
+ the
directory where the webapp has been deploayed to all other nodes in the
cluster.<br/>
+
<br/><br/><br/>
Then, for each
instance of Jahia, you will need to make the following modifications in the
Jahia configuration files:<li>Modify the
<i>jahia/WEB-INF/classes/treecache.xml</i> file and replace the following line
:<br/>
<p class="code"><attribute
name="CacheMode">LOCAL</attribute></p>
<p>with the line </p>
@@ -278,11 +290,26 @@
-->
</pre>
where <i>jvm1</i> is the name of the worker as declared in the
load-balancer.<br/>
+
+ <h4>Autocommit parameter</h4>
+ if you are using MySQL, you
should set the defaultAutoCommit parameter to "true" in the
<i>tomcat/conf/Catalina/localhost/jahia.xml</i>
+ file :
+
+ <pre class="code"><Resource
name="jdbc/jetspeed" auth="Container"
+ factory="org.apache.commons.dbcp.BasicDataSourceFactory"
+ type="javax.sql.DataSource" username="jahia"
password="jahia"
+ driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/jahia"
+ <span class="red">defaultAutoCommit="true"</span>
+ maxActive="100" maxIdle="30"
maxWait="10000"/></pre>
+ <br/><br/>
+
</p>
</p>
<h2>III - To setup and activate
transactions</h2>
<h3>Introduction
</h3>
- <p>Jahia can now be configured to use
transactions, and will soon require this in order to guarantee data integrity.
Clustering setups also <strong>require</strong> transactions to be setup
properly. This howto explains how to setup transactions with Tomcat, but it is
also possible to use the default transaction manager of a J2EE application
server, such as Apache Geronimo or JBoss. This guide only explains the steps to
configure transactions with Tomcat.</p>
+ <p>Jahia can now be configured to use
transactions, and will soon require this in order to guarantee data integrity.
+ However this is still work in
progress and may cause other unexpected problems.<br/>
+ This howto explains how to
setup transactions with Tomcat, but it is also possible to use the default
transaction manager of a J2EE application server, such as Apache Geronimo or
JBoss. This guide only explains the steps to configure transactions with
Tomcat.</p>
<p><span class="red">Warning</span> : the portlet service has not yet
been integrated with transactions. Using portlets with transactions will most
likely fail. </p>
<p>Requirements : </p>
<ul>
