X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=website%2Fman_serverwar.html;h=76c58f593fcef5bb24fa789ca8f3757f300f107c;hb=6338c0cebe13936bde3d3d2cbe6aca0c8f82f5f4;hp=af1fcf414a893d96eeadd8639246e378baed68aa;hpb=85f830bbd51a7277994bd4233141016304e210c9;p=jabaws.git diff --git a/website/man_serverwar.html b/website/man_serverwar.html index af1fcf4..76c58f5 100644 --- a/website/man_serverwar.html +++ b/website/man_serverwar.html @@ -16,7 +16,7 @@ @@ -107,28 +109,13 @@ configuration files so these are used instead.

Using the pre-compiled i386 binaries on Linux

-

Before the binaries that are bundled with JABAWS can be used, -they must first be made executable using the provided 'setexecflag.sh' script:

- -
    -
  1. cd to <webapplicationpath>/binaries/src
    2. - -
  2. run sh setexecflag.sh
    3. - -
  3. Make sure binaries supplied work under your OS.
    - For this run each binary, without any command line options or +

    JABAWS comes with pre-compiled x86 Linux binaries, thus on such systems JABAWS should work straight out of the box. If you are in any doubts or experience problems you may want to make sure that the binaries supplied work under your OS. To do this just execute each binary, without any command line options or input files. If you see an error message complaining about missing libraries or other problems, then you probably need to recompile the binaries.

    4. - -
  4. Restart the Tomcat.
    5. -
+"#recompbinaries">recompile the binaries.

-That's it! JABAWS should work at this point. Try it out using the JABAWS test client. If not, -read on... or have a look at deploying on Tomcat tips.
+You can try the JABAWS functionality with the JABAWS test client or have a look at deploying on Tomcat tips if you experience any problems.
Note: You may want to enable logging, as described here.
@@ -203,7 +190,13 @@ modify the paths in IUPred (Linux x86 | x64 | Mac)

Testing JABAWS Server

-

First of all make sure that Tomcat server is started successfully. If this was the case, then you should see JABAWS home page when you navigate to your Tomcat JABAWS context path e.g. http://myhost.compbio.ac.uk:8080/jabawsIf you see it, then it is time to make sure that web services are working too. Assuming that you have unpacked/deployed JABAWS from the server war file, you should be able to navigate to the test program which can be found in <webapplicationpath>/WEB-INF/lib/jabaws-client.jar file. To run the tests type: java -jar jabaws-client.jar -h=<Your web application server host name, port and JABAWS context path>

+

First of all make sure that Tomcat server is started successfully. If this was the case, then you should see JABAWS home page when you navigate to your Tomcat JABAWS context path e.g. http://myhost.compbio.ac.uk:8080/jabaws

+

Using JABAWS service status checker

+

If you see it, then it is time to make sure that web services are working too. The easiest way to do so is to access Services Status page available from the main JABAWS web page menu.

+

If you need to monitor web service health automatically when the best option is to use service checker that responds with the standard HTTP status code. To access this checker use the following URL: <jabaws_server>/HttpCodeResponseServiceStatus This page returns code 200, and no page context if all services are operational, 503 if one of the services have problems. You can also check each web service individually by providing the name of the web service to check at the end of the service checker URL like this: <jabaws_server>/HttpCodeResponseServiceStatus/ClustalWS

+

Upon request, the service status checker will examine the health of the ClustalWS web service only. If the service name is not valid, then the service checker will return code 400.

+

Using command line client

+

Alternatively, you should be able to use the test program which can be found in <webapplicationpath>/WEB-INF/lib/jabaws-client.jar file. To run the tests type: java -jar jabaws-client.jar -h=<Your web application server host name, port and JABAWS context path>

For example to test all JABAWS web services on host myhost.compbio.ac.uk type:

java -jar jabaws-client.jar -h=http://myhost.compbio.ac.uk:8080/jabaws

You can choose a particular web server using -s option like this java -jar jabaws-client.jar -h=http://myhost.compbio.ac.uk:8080/jabaws -s=ClustalWS This command line assumes that java executable is in your path and jabaws-client.jar is located in the current directory.

@@ -244,7 +237,7 @@ modify the paths in -