website docs update

[jabaws.git] / website / manual_qs_war.html

diff --git a/website/manual_qs_war.html b/website/manual_qs_war.html
index 9fbc23c..481d802 100644 (file)
--- a/website/manual_qs_war.html
+++ b/website/manual_qs_war.html
@@ -64,15 +64,17 @@
 <p>This is for anyone who wants to run JABAWS for their group, lab or organization, or wants to enable their local JABA server to use the cluster or perform very large tasks.</p>\r
 \r
 <ol>\r
-<li>Download the <a href="http://www.compbio.dundee.ac.uk/jabaws/archive/jaba.war">JABAWS WAR with all binaries</a> (45M)</li>\r
-  <li>Download and install <a href="http://tomcat.apache.org/download-60.cgi">Apache-Tomcat</a>.<br/>\r
-   <span class="hightlight">You will need at least version 5.5 of Tomcat (we would recommend version 6.0) and at least version 1.6 (i.e. JAVA 6) of Java.</span></li>\r
+<li>Download the <a href="http://www.compbio.dundee.ac.uk/jabaws/download.html">JABAWS WAR for your platform </a></li>\r
+  <li>Download and install <a href="http://tomcat.apache.org/download-70.cgi">Apache-Tomcat</a>.<br/>\r
+   <span class="hightlight">You will need at least version 5.5 of Tomcat (we would recommend version 7.0) and at least version 1.6 (i.e. JAVA 6) of Java.</span></li>\r
   <li>Drop the JABAWS WAR file into <span class="hightlight">tomcat/webapps</span> directory.</li>\r
   <li>(Re)start the Tomcat.</li>\r
   <li>Once the tomcat has started, it should automatically unpack the WAR into the webapps directory (if it doesn't, then you'll need to do this manually, it's just a zip archive in the end).</li>\r
   <li>You then need to complete the installation of the executable binaries:</li>\r
-   <ul><li>If you are on Linux<br/><span class="hightlight">cd</span> to <span class="hightlight"> webapps/jabaws/binaries/src/</span> and execute <span class="hightlight">./setexecflag.sh </span> script to ensure the JABAWS binaries can be executed. </li>\r
-       <li>If you are on a Mac (OSX intel mac only) or other unix-like architecture with gnu compilers available:</li>\r
+   <ul>\r
+     <li>If you are on Linux or Mac (OSX intel Mac only) <br/>\r
+       <span class="hightlight">cd</span> to <span class="hightlight"> webapps/jabaws/binaries/src/</span> and execute <span class="hightlight">./setexecflag.sh </span> script to ensure the JABAWS binaries can be executed. </li>\r
+       <li>If you are on other unix-like architecture with gnu compilers available or you'd like to get a maximum performance:</li>\r
        <li> <span class="hightlight">cd</span> to <span class="hightlight">webapps/jabaws/binaries/src/</span> and execute <span class="hightlight">./compilebin.sh  </span> script to compile all binaries JABAWS depends on. </li>\r
   <li><span class="hightlight">cd</span> to <span class="hightlight"> webapps/jabaws/binaries/src/ </span>and execute <span class="hightlight">./setexecflag.sh </span> script. </li>\r
   </ul>\r
@@ -82,7 +84,7 @@
 <p>You can test that your JABAWS server is working in two ways.</p>\r
 <ol>\r
 <li>If you are working on the command line, then use the command line client shipped with the JABAWS war to test it by running:\r
-<span class="code">java -jar &lt;Path to tomcat WebApp directory&gt;/jabaws/WEB-INF/lib/jaba-client.jar -h http://localhost:8080/jabaws</span>\r
+<span class="code">java -jar &lt;Path to tomcat WebApp directory&gt;/jabaws/WEB-INF/lib/jaba-client.jar -h=http://localhost:8080/jabaws</span>\r
 In this example we assumed that your JABAWS server URL is <span class="hightlight">http://localhost:8080</span> and JABAWS context path is <span class="hightlight">jabaws</span>\r
 </li>\r
 \r
@@ -97,7 +99,7 @@ In this example we assumed that your JABAWS server URL is <span class="hightligh
 <!--  TODO put JABAWS CMD test instructions here -->\r
 </div> <!-- content end-->\r
 <!-- about end-->\r
-<div id="copyright">Last update: 1 April 2011<br/>\r
+<div id="copyright">Last update: 10 August 2011<br/>\r
 Peter Troshin, Jim Procter and Geoff Barton, The Barton Group, University of Dundee, UK</div>\r
 \r
 </div><!-- wrapper end -->\r