<a href="man_server_dev.html" >JABAWS Development</a>\r
</div>\r
<a href="download.html">Download</a> \r
-<a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS usage statistics">Usage Statistics</a>\r
+<a href="ServiceStatus" title="JABAWS webservices status">Services Status</a>\r
+<a href="contacts.html">Contact Us</a>\r
<a href="http://www.compbio.dundee.ac.uk" title="University of Dundee, The Barton Group" >Barton Group</a>\r
</div>\r
\r
just pass whatever is specified in this line directly to the\r
cluster submission library. This is how DRMAA itself treats this\r
settings. More exactly DRMAA <span class="hightlight">JobTemplate.setNativeSpecification()</span> function will be called.</p>\r
-\r
+<p>For further details and examples of configuration please refer to the <span class="hightlight">Executable.properties</span> file supplied with JABAWS.</p>\r
<h3><a name="setexecenv" />Defining Environment Variables for\r
Executables</h3>\r
\r
<h3><a name="settinglimit" id="settinglimit"></a>Limiting the size of the job accepted by JABAWS </h3>\r
<p>JABAWS can be configured to reject excessively large tasks. This is useful if you operate JABAWS service for many users. By defining a maximum allowed task size you can provide an even service for all users and prevents waist of resources on the tasks too large to complete successfully. You can define the maximum number of sequences and the maximum average sequence length that JABAWS accepts for each JABA Web Service independently. \r
Furthermore, you can define different limits for different presets of the same web service. <br />\r
-By default limits are set well in excess of what you may want to offer to the users outside your lab, to make sure that the tasks are never rejected. The default limit is 100000 sequences of 100000 letters on average for all of the JABA web services. You can adjust the limits according to your needs by editing <span class="hightlight">conf/settings/<X>Limit.xml</span> files.</p>\r
+By default limits are disabled. You can enable them by editing <span class="hightlight">conf/Executable.properties</span> file. You can adjust the limits according to your needs by editing <span class="hightlight">conf/settings/<X>Limit.xml</span> files. </p>\r
<h3><a name="diffbin" id="diffbin"></a>Using a different version of the alignment program with JABAWS</h3>\r
<p>JABAWS supplied with binaries and source code of the executables which version it supports. So normally you would not need to install your own executables. However, if you have a different version of an executable (e.g. an alignment program) which you prefer, you could use it as long as it supports all the functions JABAWS executable supported. This could be the case with more recent executable. If the options supported by your chosen executable is different when the standard JABAWS executable, than you need to edit <em>ExecutableName</em>Paramaters.xml configuration file. </p>\r
<h3><a name="mixuse" id="mixuse"></a>Load balancing </h3>\r
<p>If your cluster is busy and have significant waiting times you can achieve a faster response by allowing the server machine to calculate small tasks and the reserve the cluster for bigger jobs. This works especially well if your server is a powerful machine with many CPUs. To do this you need to enable and configure both the cluster and the local engines. Once this is done decide on the maximum size of a task to be run on the server locally. Then, edit <span class="hightlight">"# LocalEngineExecutionLimit #" </span>preset in<span class="hightlight"> <ServiceName>Limits.xml</span> file accordingly. JABAWS server then will balance the load according to the following rule: If the task size is smaller then the maximum task size for local engine, and the local engine has idle threads, then calculate task locally otherwise submit the task to the cluster. </p>\r
<h3><a name="testingJaba" id="testingJaba"></a>Testing JABA Web Services</h3>\r
-<p>You can use a command line client (part of the client only\r
+<p>Access <span class="code"><your_JABAWS_server_URL>/ServiceStatus</span> to test all web services. Each time you access this URL, all services are tested. You can test a particular web service by adding its name at the end of this URL. For example <span class="code">http://localhost:8080/jabaws/ServiceStatus/MuscleWS </span>will test MuscleWS webservice only. For production configuration we recommend prohibiting requests to this URL for non authenticated users to prevent excessive load on the server. </p>\r
+<p>Alternatively, you can use a command line client (part of the client only\r
package) to test your JABAWS installation as described <a href="man_client.html">here</a>. If you downloaded a JABAWS\r
server package, you can use <span class=\r
"hightlight"><your_jaba_context_name>/WEB-INF/lib/jaba-client.jar</span> to test JABAWS installation as described in <a href=\r
name of the executable</td>\r
</tr>\r
<tr>\r
+ <td>ExecutionStatistics</td>\r
+ <td>The database for storing the execution statistics. </td>\r
+ </tr>\r
+ <tr>\r
+ <td>statpages</td>\r
+ <td>Web pages for usage statistics visialization and webservices status queries. </td>\r
+ </tr>\r
+ <tr>\r
<td>jobsout/</td>\r
<td>Contains directories generated when running an individual executable. E.g. input and output files and some other task\r
related data. (optional)</td>\r
binaries.</td>\r
</tr>\r
<tr>\r
+ <td>binaries/windows</td>\r
+ <td>Contains binaries for MS Windows operating system. </td>\r
+ </tr>\r
+ <tr>\r
<td>binaries/matrices</td>\r
<td>Substitution matrices\r
<!-- what format ? --></td>\r
</table>\r
</div>\r
<!-- content end-->\r
-<div id="copyright">Last update: 10 August 2011<br />\r
+<div id="copyright">Last update: 16 September 2011<br />\r
Peter Troshin, Jim Procter and Geoff Barton, The Barton Group, University of\r
Dundee, UK</div>\r
</div>\r
git://source.jalview.org / jabaws.git / blobdiff