You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wadi-commits@incubator.apache.org by ju...@apache.org on 2005/12/19 21:12:09 UTC
svn commit: r357801 - in
/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started:
evacuation.xml index.xml install.xml jboss.xml jetty.xml location.xml
partitioning.xml tomcat.xml
Author: jules
Date: Mon Dec 19 13:12:01 2005
New Revision: 357801
URL: http://svn.apache.org/viewcvs?rev=357801&view=rev
Log:
further improvements to getting started doc
Modified:
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/evacuation.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/index.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/install.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jboss.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jetty.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/location.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/partitioning.xml
incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/tomcat.xml
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/evacuation.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/evacuation.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/evacuation.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/evacuation.xml Mon Dec 19 13:12:01 2005
@@ -8,15 +8,15 @@
"Run for your lives!"
<p>
The most common reason for a node to leave a cluster is
- shutdown for scheduled for maintenance. With the increasing
+ shutdown for scheduled maintenance. With the increasing
frequency of software updates, this is becoming more and more
- common and with the increasing number of nodes in your
- cluster, more and more complex and error prone.
+ common and with the gorwing number of nodes in your cluster,
+ more and more complex and error prone.
</p>
<p>
Every time a node leaves a cluster, the sessions that it is
carrying will become unavailable, unless they can be evacuated
- to surviving nodes, as it leaves.
+ to surviving nodes.
</p>
Let's take a look at WADI doing this.
<p>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/index.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/index.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/index.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/index.xml Mon Dec 19 13:12:01 2005
@@ -6,25 +6,50 @@
<body>
<section name="Getting Started with WADI">
<p>
- To familiarise yourself with WADI, you will need to follow the following steps:
+ To familiarise yourself with WADI, we provide a number of
+ simple demonstrations that you may walk through.
</p>
<p>
- If you are impatient, forget about running the s/w and go
- straight to the demos. You should be able to glean quite a lot
- from just reading through them.
+ If you are pressed for time, forget about the installation
+ step and running the s/w. Just go straight to the demos. You
+ should be able to glean quite a lot from just reading through
+ them.
</p>
<p>
- NOTE - say something about this release being a 'technology
- preview' and how to treat it gently...
+ WADI-2.0M1 is a technology preview release. We are not yet
+ production ready. In order to get best results from the
+ software, certain temporary guidelines are suggested.
+ <ul>
+ <li>
+ leave a reasonable pause (e.g. 5 seconds) between starting
+ and stopping nodes.
+ </li>
+ <li>
+ do not 'kill -9' a node.
+ </li>
+ </ul>
+ These guidelines are to help to you avoid stumbling on issues
+ in the current release of which we are aware. They will be
+ relaxed as soon as these issues are resolved.
</p>
<p>
- NOTE - say something about setting up the browser - cookies
- required (Konqueror may not work - and why)
+ The demonstration web application relies on the tying of the
+ web session to the browser via a cookie. Please ensure that
+ you have cookies enabled in your browser.
+ </p>
+ <p>
+ NOTE: Some browsers (Konqueror), include the server port in a
+ cookie's domain. This makes them unsuitable for this
+ demonstration, since you will be making requests through more
+ than one port on the same host, whilst requiring that the same
+ cookie is used for all requests. This issue does not affect
+ the load-balancing demonstration, since all requests are made
+ through a single port - the one on which the load-balancer is
+ listening.
</p>
<p>
<ol>
<li><a href="./install.html">installation guide</a> (REHASH)</li>
- <li><a href="./start.html">start</a> the required services (REHASH)</li>
<li>
walk through some demos:
<ul>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/install.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/install.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/install.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/install.xml Mon Dec 19 13:12:01 2005
@@ -6,34 +6,75 @@
<body>
<section name="Getting Started: Installation">
<p>
- You can put together a heterogeneous cluster of <a href="./tomcat.html">Tomcat</a>, <a href="./jetty.html">Jetty</a>,<a href="./geronimo.html">Geronimo</a> and <a href="./jboss.html">JBoss</a> instances.
+ To install WADI:
+ <ul>
+ <li>
+ Either:
+ <ol>
+ <li>download a copy of WADI 2.0M1</li>
+ <li>unpack it somewhere</li>
+ <li>set WADI_HOME to this dir and export it</li>
+ </ol>
+ </li>
+ <li>
+ Or:
+ <ol>
+ <li>check out the latest WADI src from CVS</li>
+ <li>Build it</li>
+ <li>set WADI_HOME to the top of this tree and export it</li>
+ </ol>
+ </li>
+ </ul>
+ </p>
+
+ <p>
+ WADI nodes use a machine generated unique id to distinguish
+ each other. For the purposes of logging and monitoring, WADI
+ expects each node to also be given a more user-friendly id
+ (ideally unique). This second id - the node's name - is used
+ to label its configuration. The WADI demonstration uses
+ colours (<font color="red">red</font>, <font
+ color="green">green</font>, <font color="blue">blue</font>,
+ ...) as node names. Configurations corresponding to these
+ names may be found in $WADI_HOME/conf.
</p>
<p>
- If you are using a clustered configuration
- <ol>
- <li>Download a copy of <a href="http://dist.codehaus.org/activemq/distributions">activemq-3.2.1</a> - unpack it somewhere</li>
+ WADI integrates with a number of different web containers. To
+ walk through the 'Getting Started' documentation, you will
+ need at least one of the following installed and available to
+ WADI. Choosing more than one container will allow you to test
+ WADI's ability to cluster a mixed set of containers.
+
+ <ul>
+ <li>Installing <a href="./tomcat.html">Tomcat 5.0.x, 5.5.x</a></li>
+ <li>Installing <a href="./jetty.html">Jetty 5, 6</a></li>
+ <li>Installing <a href="./geronimo.html">Geronimo-1.0</a></li>
+ <li>Installing <a href="./jboss.html">JBoss-4.x</a></li>
+ </ul>
+ </p>
+
+ <p>
+ WADI nodes speak to each other via asynchronous messages over
+ ActiveMQ. ActiveMQ may be configured with a variety of
+ protocol stacks. Ultimately, WADI will use ActiveMQ's peer://
+ protocol. This allows peers in a cluster to message each other
+ directly. Currently, due to a couple of issues in the peer://
+ stack, the demonstration needs to be run on the tcp://
+ stack. This necessitates the running of a standalone message
+ broker to which all nodes connect and via which all messages
+ are exchanged. This is an obvious single point of failure and
+ will be removed as soon as the issues with peer:// have been
+ resolved. We are working on this as a priority.
+
+ <ul>
+ <li>Download a copy of <a href="http://dist.codehaus.org/activemq/distributions">activemq-3.2.1</a></li>
+ <li>Unpack it somewhere</li>
<li>Set ACTIVEMQ_HOME to this dir and export it</li>
- <li>Then
- <ul>
- <li>
- Either:
- <ol>
- <li>download a copy of WADI 2.0-SNAPSHOT - unpack it somewhere</li>
- <li>set WADI_HOME to this dir and export it</li>
- </ol>
- </li>
- <li>
- Or:
- <ol>
- <li>check out the latest WADI src from CVS</li>
- <li>Build it</li>
- <li>set WADI_HOME to the top of this tree and export it</li>
- </ol>
- </li>
- </ul>
- </li>
- </ol>
+ <li>To start up the ActiveMQ broker: cd $ACTIVEMQ_HOME/bin; sh activemq.sh</li>
+ <li>To shut down the ActiveMQ broker: Ctl-c it</li>
+ </ul>
</p>
+
</section>
</body>
</document>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jboss.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jboss.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jboss.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jboss.xml Mon Dec 19 13:12:01 2005
@@ -1,46 +1,51 @@
<?xml version="1.0"?>
<document>
- <properties>
- <title>Getting Started - JBoss</title>
- </properties>
- <body>
- <section name="Getting Started - JBoss">
- <p>
- <ol>
- <li>download a copy of <a href="http://www.jboss.com/products/jbossas/downloads">JBoss4.0+</a> - unpack it somewhere</li>
- <li>set JBOSS4_HOME to this directory and export it</li>
- <li>Copy $WADI_HOME/lib/wadi-jboss4-*.jar to e.g. $JBOSS4_HOME/server/default/lib (contains logging integration - see below)</li>
- <li>Create a wadi.sar containing all the jars from $WADI_HOME/lib (except wadi-jboss4-*.sar) and a META-INF/jboss-service.xml (use e.g. $WADI_HOME/conf/jboss-service.xml)</li>
- <li>copy the sar into e.g. $JBOSS4_HOME/server/default/deploy</li>
- <li>copy $WADI_HOME/webapps/wadi-webapp-*.war into the same dir</li>
- <li>In $JBOSS4_HOME/bin, start your JBoss like this
- <code><pre>JAVA_OPTS="-Dx=... -Dy=..." ./run.sh</pre></code>
- where x,y..z are properties from your chosen conf/node.*.properties file.
- </li>
- <li>If you are using the DiscStore, you may have to create a 'sessions' dir underneath java.io.tmpdir for WADI to page sessions in and out of.</li>
- </ol>
-
- Logging Integration :
- <br/>
- <br/>
- JBoss4 uses a customised log4j (adds 'trace' level) for logging. WADI uses the commons-logging API. By default, WADI will log out to JBosses loggers, but WADI trace-level will be collapsed into JBoss debug-level. This can be annoying. wadi-jboss4-*.jar contains a Log class that bridges the gap between the two logging systems and channels WADI-trace to JBoss-trace. It cannot be installed via the wadi.sar, since it must be available to log4j at startup time, hence the alternate deployment location.
- <br/>
- <br/>
- Actually getting trace output from JBoss can be quite problematic in itself. Here is how I achieve it.
-
- <ol>
- <li>Remove the 'Threshold' attribute from your <appender/> clause - Setting it to 'TRACE' does not seem to work (probably because this is a custom log level).</li>
- <li>To enable WADI trace level logging, include a category clause e.g. :
- <code><pre><category name="org.codehaus.wadi"><priority value="TRACE" class="org.jboss.logging.XLevel"/></category></pre></code>
- </li>
- <li>In order to get the logging bridge installed add a:
- <code><pre>-Dorg.apache.commons.logging.Log=org.codehaus.wadi.jboss4.JBossLog</pre></code>
- to your JAVA_OPTS when starting JBoss.
- </li>
- </ol>
-
- An example log4j.xml is included in $WADI_HOME/conf/jboss-log4j.xml. This may be copied to or merged with e.g. $JBOSS_HOME/server/default/conf/log4j.xml
- </p>
- </section>
- </body>
+ <properties>
+ <title>Getting Started - JBoss</title>
+ </properties>
+ <body>
+ <section name="Getting Started - JBoss">
+ <p>
+ <ol>
+ <li>download a copy of <a href="http://www.jboss.com/products/jbossas/downloads">JBoss4.0+</a> - unpack it somewhere</li>
+ <li>set JBOSS4_HOME to this directory and export it</li>
+ <li>Copy $WADI_HOME/lib/wadi-jboss4-*.jar to e.g. $JBOSS4_HOME/server/default/lib (contains logging integration - see below)</li>
+ <li>Create a wadi.sar containing all the jars from $WADI_HOME/lib (except wadi-jboss4-*.sar) and a META-INF/jboss-service.xml (use e.g. $WADI_HOME/conf/jboss-service.xml)</li>
+ <li>copy the sar into e.g. $JBOSS4_HOME/server/default/deploy</li>
+ <li>copy $WADI_HOME/webapps/wadi-webapp-*.war into the same dir</li>
+ <li>In $JBOSS4_HOME/bin, start your JBoss like this
+ <code><pre>JAVA_OPTS="-Dx=... -Dy=..." ./run.sh</pre></code>
+ where x,y..z are properties from your chosen conf/node.*.properties file.
+ </li>
+ <li>If you are using the DiscStore, you may have to create a 'sessions' dir underneath java.io.tmpdir for WADI to page sessions in and out of.</li>
+ </ol>
+
+ Logging Integration :
+ <br/>
+ <br/>
+ JBoss4 uses a customised log4j (adds 'trace' level) for logging. WADI uses the commons-logging API. By default, WADI will log out to JBosses loggers, but WADI trace-level will be collapsed into JBoss debug-level. This can be annoying. wadi-jboss4-*.jar contains a Log class that bridges the gap between the two logging systems and channels WADI-trace to JBoss-trace. It cannot be installed via the wadi.sar, since it must be available to log4j at startup time, hence the alternate deployment location.
+ <br/>
+ <br/>
+ Actually getting trace output from JBoss can be quite problematic in itself. Here is how I achieve it.
+
+ <ol>
+ <li>Remove the 'Threshold' attribute from your <appender/> clause - Setting it to 'TRACE' does not seem to work (probably because this is a custom log level).</li>
+ <li>To enable WADI trace level logging, include a category clause e.g. :
+ <code><pre><category name="org.codehaus.wadi"><priority value="TRACE" class="org.jboss.logging.XLevel"/></category></pre></code>
+ </li>
+ <li>In order to get the logging bridge installed add a:
+ <code><pre>-Dorg.apache.commons.logging.Log=org.codehaus.wadi.jboss4.JBossLog</pre></code>
+ to your JAVA_OPTS when starting JBoss.
+ </li>
+ </ol>
+
+ An example log4j.xml is included in $WADI_HOME/conf/jboss-log4j.xml. This may be copied to or merged with e.g. $JBOSS_HOME/server/default/conf/log4j.xml
+ </p>
+
+ <p>
+ JBoss is started in the usual way: "cd $JBOSS4_HOME/bin;
+ ./run.sh'".
+ </p>
+ </section>
+ </body>
</document>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jetty.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jetty.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jetty.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/jetty.xml Mon Dec 19 13:12:01 2005
@@ -1,26 +1,53 @@
<?xml version="1.0"?>
<document>
- <properties>
- <title>Getting Started - Jetty</title>
- </properties>
- <body>
- <section name="Getting Started - Jetty">
- <p>
- Either:
- <ol>
- <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=7322">Jetty 5+</a> - unpack it somewhere</li>
- <li>set JETTY5_HOME to this directory and export it</li>
- </ol>
- Or:
- <ol>
- <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=7322">Jetty 6+</a> - unpack it somewhere</li>
- <li>set JETTY6_HOME to this directory and export it</li>
- </ol>
-
- Finally, to start the node :
-
- from $WADI_HOME/bin run e.g. './node.sh jetty5 <font color="red">red</font>' or './node.sh jetty6 <font color="red">red</font>'
- </p>
- </section>
- </body>
+ <properties>
+ <title>Getting Started - Jetty</title>
+ </properties>
+ <body>
+ <section name="Getting Started - Jetty">
+
+ <p>
+ Either:
+ <ol>
+ <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=7322">Jetty 5+</a> - unpack it somewhere</li>
+ <li>set JETTY5_HOME to this directory and export it</li>
+ </ol>
+ Or:
+ <ol>
+ <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=7322">Jetty 6+</a> - unpack it somewhere</li>
+ <li>set JETTY6_HOME to this directory and export it</li>
+ </ol>
+ </p>
+
+ <p>
+ TODO - What about running Jetty with a JMX Agent ?
+ </p>
+
+
+ <p>
+ There are two ways to start a Jetty node :
+ <ul>
+ Either:
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh <container> <id>"
+ <ul>
+ e.g.
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh jetty5 red"
+ </li>
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh jetty6 green"
+ </li>
+ </ul>
+ </li>
+ Or:
+ <li>
+ Copy the WADI jars into your Jetty tree, configure your Jetty with values from the relevant wadi configuration and start Jetty
+ in the usual way - TO BE DOCUMENTED.
+ </li>
+ </ul>
+ </p>
+
+ </section>
+ </body>
</document>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/location.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/location.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/location.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/location.xml Mon Dec 19 13:12:01 2005
@@ -143,11 +143,6 @@
moved to the <font color="green">green</font> node.
</p>
<p>
- NOTE - some browsers partition cookies by host and some by
- host:port - Konqueror seems to do the latter - breaking this
- demo... - what about Internet Explorer ?
- </p>
- <p>
Just to be sure, refresh the page a couple of times.
</p>
<p>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/partitioning.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/partitioning.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/partitioning.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/partitioning.xml Mon Dec 19 13:12:01 2005
@@ -9,11 +9,9 @@
<p>
Partitioning is a strategy commonly used to aid in
scalability. You divide a large problem into smaller pieces
- that are independant of each other. Because they are
- demonstrably independant of each other, these problems may be
- e.g. solved concurrently with no contention on any shared
- resource and therefore no requirement to be running in the
- same JVM.
+ that are demonstrably independant of each other. Because they
+ are independant of each other, these problems may be solved
+ concurrently with no contention on any shared resource.
</p>
<p>
Many existing clustering solutions require that a cluster is
@@ -30,7 +28,7 @@
</p>
We can watch this happening in a very simple WADI demo.
<p>
- We start a <font color="red">red</font> node. As it comes on line WADI outputs e.g. the following:
+ We start a <font color="red">red</font> node. As it comes online WADI outputs e.g. the following:
</p>
<p>
<code>
Modified: incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/tomcat.xml
URL: http://svn.apache.org/viewcvs/incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/tomcat.xml?rev=357801&r1=357800&r2=357801&view=diff
==============================================================================
--- incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/tomcat.xml (original)
+++ incubator/wadi/trunk/wadi-site/src/site/xdoc/getting-started/tomcat.xml Mon Dec 19 13:12:01 2005
@@ -1,33 +1,65 @@
<?xml version="1.0"?>
<document>
- <properties>
- <title>Getting Started - Tomcat</title>
- </properties>
- <body>
- <section name="Getting Started - Tomcat">
- <p>
- Either:
- <ol>
- <li>download a copy of <a href="http://tomcat.apache.org/download-55.cgi">Tomcat 5.0.28+</a> - unpack it somewhere</li>
- <li>set TOMCAT50_HOME to this directory and export it</li>
- </ol>
- Or:
- <ol>
- <li>download a copy of <a href="http://tomcat.apache.org/download-55.cgi">Tomcat 5.5.9+</a> - unpack it somewhere</li>
- <li>set TOMCAT55_HOME to this directory and export it</li>
- </ol>
- If you would like to make use of the Spring JMX integration for WADI so that you can browse WADI's MBeans via e.g. mc4j (recommended), you will need to do the following :
- <ol>
- <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=47745">mx4j-3.0.1</a> - unpack it somewhere</li>
- <li>set MX4J_HOME to this directory and export it</li>
- <li>If using Tomcat-50, remove $TOMCAT50_HOME/bin/jmx.jar</li>
- <li>copy $MX4J_HOME/lib/{mx4j.jar,mx4j-remote.jar,mx4j-tools.jar} into $TOMCAT50_HOME/server/lib or $TOMCAT55_HOME/server/lib</li>
- </ol>
-
- Finally, to start the node :
-
- from $WADI_HOME/bin run e.g. './node.sh tomcat50 <font color="red">red</font>' or './node.sh tomcat55 <font color="red">red</font>'
- </p>
- </section>
- </body>
+ <properties>
+ <title>Getting Started - Tomcat</title>
+ </properties>
+ <body>
+ <section name="Getting Started - Tomcat">
+
+ <p>
+
+ Either:
+ <ol>
+ <li>download a copy of <a href="http://tomcat.apache.org/download-55.cgi">Tomcat 5.0.28+</a> - unpack it somewhere</li>
+ <li>set TOMCAT50_HOME to this directory and export it</li>
+ </ol>
+
+ Or:
+ <ol>
+ <li>download a copy of <a href="http://tomcat.apache.org/download-55.cgi">Tomcat 5.5.9+</a> - unpack it somewhere</li>
+ <li>set TOMCAT55_HOME to this directory and export it</li>
+ </ol>
+
+ </p>
+
+ <p>
+ Optionally, if you would like to make use of the Spring JMX integration
+ for WADI so that you can browse WADI's MBeans via e.g. mc4j
+ (recommended), you will need to do the following :
+
+ <ol>
+ <li>download a copy of <a href="http://sourceforge.net/project/showfiles.php?group_id=47745">mx4j-3.0.1</a> - unpack it somewhere</li>
+ <li>set MX4J_HOME to this directory and export it</li>
+ <li>If using Tomcat-50, remove $TOMCAT50_HOME/bin/jmx.jar</li>
+ <li>copy $MX4J_HOME/lib/{mx4j.jar,mx4j-remote.jar,mx4j-tools.jar} into $TOMCAT50_HOME/server/lib or $TOMCAT55_HOME/server/lib</li>
+ </ol>
+ </p>
+
+ <p>
+ There are two ways to start a Tomcat node :
+ <ul>
+ EITHER:
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh <container> <id>"
+ <ul>
+ e.g.
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh tomcat50 red"
+ </li>
+ <li>
+ "cd $WADI_HOME/bin; ./node.sh tomcat55 green"
+ </li>
+ </ul>
+ </li>
+ OR:
+ <li>
+ Copy the WADI jars into your Tomcat tree, configure your Tomcat with values from the relevant wadi configuration and start Tomcat
+ in the usual way - TO BE DOCUMENTED.
+ </li>
+ </ul>
+
+ </p>
+
+ </section>
+ </body>
</document>