From 0fb93e9e48de149bef44a075084ac463d03b4afc Mon Sep 17 00:00:00 2001
From: pvtroshin <pvtroshin@e3abac25-378b-4346-85de-24260fe3988d>
Date: Fri, 16 Sep 2011 15:17:24 +0000
Subject: [PATCH] Service status pages update

git-svn-id: link to svn.lifesci.dundee.ac.uk/svn/barton/ptroshin/JABA2@4592 e3abac25-378b-4346-85de-24260fe3988d
---
 statpages/ServicesStatus.jsp |    4 ++++
 website/man_serverwar.html   |    7 ++++++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/statpages/ServicesStatus.jsp b/statpages/ServicesStatus.jsp
index 75f5f8e..533f172 100644
--- a/statpages/ServicesStatus.jsp
+++ b/statpages/ServicesStatus.jsp
@@ -69,5 +69,9 @@ TODO refactor
 
 </c:forEach>
 </table>
+<p>If you would like to integrate JABAWS with automated health check system you may want to use 
+the HTTP code response service checker. It responds with HTTP status code depending on the status 
+of the web service.
+For more information please refer to <a href="man_serverwar.html#usingWsTester">Testing JABAWS server</a> help page.</p>
 </div><!-- margin div -->	
 <jsp:include page="footer.jsp" />
\ No newline at end of file
diff --git a/website/man_serverwar.html b/website/man_serverwar.html
index ddd7204..88bc96a 100644
--- a/website/man_serverwar.html
+++ b/website/man_serverwar.html
@@ -190,7 +190,12 @@ modify the paths in <span class=
   <li>IUPred (Linux <a href="http://www.compbio.dundee.ac.uk/jabaws/archive/binaries/linux_x86/iupred">x86</a> | <a href="http://www.compbio.dundee.ac.uk/jabaws/archive/binaries/linux_x64/iupred">x64</a> | <a href="http://www.compbio.dundee.ac.uk/jabaws/archive/binaries/mac/iupred">Mac</a>)</li>
 </ul>
 <h3><a name="usingWsTester" id="usingWsTester"></a>Testing JABAWS Server </h3>
-<p>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. <span class="code">http://myhost.compbio.ac.uk:8080/jabaws</span>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 ServiceStatus web page. </p>
+<p>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. <span class="code">http://myhost.compbio.ac.uk:8080/jabaws</span></p>
+<p><strong>Using JABAWS service status checker</strong></p>
+<p>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. </p>
+<p>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: <span class="code">&lt;jabaws_server&gt;/HttpCodeResponseServiceStatus</span>  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: <span class="code">&lt;jabaws_server&gt;/HttpCodeResponseServiceStatus/ClustalWS</span></p>
+<p>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. </p>
+<p><strong>Using command line client</strong> </p>
 <p>Alternatively, you should be able to use the test program which can be found in &lt;webapplicationpath&gt;/WEB-INF/lib/jabaws-client.jar file. To run the tests type:<span class="code"> java -jar jabaws-client.jar -h=&lt;Your web application server host name, port and JABAWS context path&gt;</span></p>
 <p>For example to test all JABAWS web services on host myhost.compbio.ac.uk type: </p>
 <p class="code">java -jar jabaws-client.jar -h=http://myhost.compbio.ac.uk:8080/jabaws </p>
-- 
1.7.10.2