X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=website%2Fman_serverwar.html;h=dc994bcca6b107eddf66ceff71a168de29f62be7;hb=1e8254e6a48302dd3e47e1f68cc51f6a6b9c33db;hp=5d092e0a343f862f5555d03e4135279a02c08086;hpb=b413eee53fa3cc22a6bd4e03c9ac64bf26b7c834;p=jabaws.git diff --git a/website/man_serverwar.html b/website/man_serverwar.html index 5d092e0..dc994bc 100644 --- a/website/man_serverwar.html +++ b/website/man_serverwar.html @@ -1,8 +1,9 @@ - + - + Java Bioinformatics Analyses Web Services (JABAWS) Server Web Aplication aRchive manual @@ -14,18 +15,17 @@
Home - Manual + Getting Started + Manual Download +Contact Us Barton Group
@@ -70,18 +71,18 @@ class="headeru">Services version 2.4 of the Java Servlet specification, and a Java 6 runtime environment. We recommend using an official Oracle Java 6 runtime environment, and Apache-Tomcat web application server version 6, but other versions may work as well.

+href="http://tomcat.apache.org/download-60.cgi">Apache-Tomcat web application server version 6, but other versions may work as well.
Please Note: The JABAWS WAR is not generally compatible with older Mac systems based on the PowerPC architecture, since Java 1.6 is not available to run JABAWS.

-

JABAWS Web Application aRchive can run on any host operating system that supports Java. However JABAWS depends on the third party programs which are not available for all operating systems. In particular, only Clustal and Muscle are currently available for MS Windows platform. +

JABAWS Web Application aRchive can run on any host operating system that supports Java 1.6. However JABAWS depends on a number of third party programs which are not available for all operating systems. In particular, only Clustal and Muscle are currently available for MS Windows platform.

-

JABAWS comes with pre-compiled MS Windows and Linux IA32 binaries and contains all the binaries sources.

+

JABAWS comes with pre-compiled MS Windows and Linux IA32 binaries, as well as the source code and build scripts necessary to recompile them.

To run JABAWS on the cluster you must have shared disk space accessible from all cluster nodes.

Installing the JABAWS WAR file

JABAWS is distributed as a web application archive (WAR). To deploy JABAWS in Apache-Tomcat - simply drop the war file into the webapps directory of a running -Tomcat, and it will do the rest. If you used this deployment procedure, do not remove jabaws war file, otherwise Tomcat will undeploy your application!

+Tomcat, and it will do the rest. If you used this deployment procedure, do not remove the jabaws WAR file, otherwise Tomcat will undeploy your application! The context path for your deployed application will be the same as the name of the war file. For example, assuming the Tomcat server is running on the localhost:8080 and jaba.war file is put into the <tomcat server root>/webapps directory, the deployed application from the jaba.war file then can be accessed by this URL http://localhost:8080/jaba.

For any other web application server, please follow your server's specific deployment procedure for 'WAR' files. If you install JABAWS on a MS Windows machine, then @@ -117,7 +118,7 @@ they must first be made executable using the provided recompile the binaries. with +"#recompbinaries">recompile the binaries.

  • Restart the Tomcat.
    • @@ -230,16 +231,16 @@ modify the paths in <?xml version="1.0" encoding="UTF-8"?>
    <Context antiResourceLocking="false" privileged="true" />

    This should be sufficient to prevent Tomcat from removing your JABAWS from WEBAPPS. For more information about the Tomcat deployer read this documentation on the Apache-Tomcat web site.

    -

    Apache-Tomcat fails to deploy jaba.war file

    +

    Apache-Tomcat fails to deploy jabaws.war file

    • Make sure Tomcat have sufficient access rights to read your war file.
    • Restart the Tomcat, sometimes it will not since that the new war file is added without restart
      • -
    • If Tomcat still refuses to unpack the war file, unpack it manually into web application folder (the war file is just a zip archive). Restart the Tomcat.
      • +
    • If Tomcat still refuses to unpack the war file, unpack it manually into web application folder (the war file is just a zip archive). Restart the Tomcat.
    -