<a href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a> \r
-<a class="selected" 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 class="selected" 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
<!--body end -->\r
</div>\r
\r
-<div id="copyright">Last update: 10 August 2011<br />\r
+<div id="copyright">Last update: 16 September 2011<br />\r
Peter Troshin and Geoff Barton, The Barton Group, University of\r
Dundee, UK</div>\r
\r
<p>JABAWS are the standard JAX-WS web services, which are WS-I basic profile compatible. </p>\r
</div>\r
<!-- content end--> \r
-<div id="copyright">Last update: 19 August 2010<br/>Peter Troshin, The Barton Group, University of Dundee, UK</div>\r
+<div id="copyright">Last update: 16 September 2011<br/>\r
+ Peter Troshin, The Barton Group, University of Dundee, UK</div>\r
</div><!-- wrapper end-->\r
</div> <!-- page end-->\r
<!-- Google analitics -->\r
<a href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a class="selected" 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
\r
</div>\r
<!-- wrapper end-->\r
-<div id="copyright">Last update: 10 August 2011<br />\r
+<div id="copyright">Last update: 16 September 2011<br />\r
Peter Troshin and Geoff Barton, The Barton Group, University of\r
Dundee, UK</div>\r
\r
<a href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a> \r
- <a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS server 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></div>\r
\r
<!-- panel end-->\r
<div class="brick_header"><h2>For Users</h2></div>\r
<div class="brick_content">\r
<strong>The Server: </strong><a href="http://www.compbio.dundee.ac.uk/jabaws/archive/jabaws-vm.zip">JABAWS Virtual Appliance:</a> (520M)\r
- or <a href="man_awscloud.html" title="Amazon Machine Image">JABAWS AMI</a> for the Amazon EC2 Cloud<br/>\r
+ or <a href="man_awscloud.html">use JABAWS on Amazon Webservices Cloud</a><br/>\r
<strong>The Client: </strong><a href="http://www.jalview.org/download.html">Jalview</a> (18M)\r
<p>To use JABA Web Services on most operating systems, just download and <a href="manual_qs_va.html#qsc">install</a> the JABAWS Virtual Appliance (VA) or even easier - just start JABAWS machine on the cloud and point Jalview at it!</p>\r
</div>\r
</div>\r
\r
<!-- content end-->\r
-<div id="copyright">Last update: 2 August 2011<br />\r
+<div id="copyright">Last update: 16 September 2011<br />\r
This site is best viewed in Firefox 3.6, Google Chrome 10, Internet Explorer 8 or above </div>\r
</div>\r
\r
<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></div>\r
\r
<!-- panel end-->\r
</div> \r
<!-- about end-->\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 Dundee, UK</div>\r
\r
</div>\r
<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
<h2>JABAWS Server in the Amazon Cloud</h2>\r
<ul>\r
<li><a href="#jabawsOnCloud">JABAWS on the Cloud</a></li>\r
- <li><a href="#jabawsOnCloudHow">How to use JABAWS on the Amazon EC2 cloud</a></li>\r
- </ul>\r
+ <li><a href="man_awscloud_ec2.html">How to use JABAWS on the Amazon EC2 cloud</a></li>\r
+ <li><a href="man_awscloud_bs.html">How to use JABAWS WAR on Amazon Elastic Beanstalk</a> </li>\r
+</ul>\r
<div id="jabaws_on_cloud">\r
<h3><a name="jabawsOnCloud" id="jabawsOnCloud"></a>JABAWS on the Cloud</h3>\r
<p>We provide pre-configured JABAWS Amazon Machine Image (AMI) which you can use on the <a href="http://aws.amazon.com/what-is-aws">Amazon EC2 cloud</a>. Typical use cases are </p>\r
<li>your organization already uses the Amazon cloud and you do not want to do any special arrangements for the JABAWS </li>\r
<li>you want to benefit from the Amazon automatic scaling and monitoring to make sure JABAWS is always ready </li>\r
</ul>\r
-<p>If you know what to do than JABAWS AMI ID is <strong>ami-40fecd34</strong>, manifest <strong>846107356395/JABAWS2</strong> to get you started, if not read on. </p>\r
-<h3><a name="jabawsOnCloudHow" id="jabawsOnCloudHow"/></a>How to use JABAWS on the Amazon EC2 cloud </h3>\r
-<ol>\r
- <li><a href="https://www.amazon.com/ap/signin/175-8261537-7969810?_encoding=UTF8&openid.assoc_handle=aws&openid.return_to=https%3A//aws-portal.amazon.com/gp/aws/developer/registration/index.html/175-8261537-7969810&openid.mode=checkid_setup&openid.ns=http%3A//specs.openid.net/auth/2.0&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.pape.max_auth_age=600&siteState=awsMode%3A%3Aregistration%3A%3AheaderMessage%3A%3AAmazon Web Services Sign Up%3A%3A&pageId=aws.ssop&openid.pape.preferred_auth_policies=http%3A//schemas.openid.net/pape/policies/2007/06/multi-factor-physical&marketplaceId=ATVPDKIKX0DER&accountStatusPolicy=P1&openid.ns.pape=http%3A//specs.openid.net/extensions/pape/1.0&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&authCookies=1">Create Amazon Web Services account</a>. </li>\r
- <li><a href="https://console.aws.amazon.com/ec2/home?region=eu-west-1#selectInstance=&launchAmi=&s=Home">Log in into the Amazon Web Services (AWS) console.</a> Make sure you are in the EU West (Ireland) region. JABAWS image is not available in other regions as yet. See marker 1. </li>\r
- <li>Click on "Launch Instance" button marker 2. </li>\r
-\r
-<img src="images/aws_console_launch.gif" alt="AWS console" width="687" height="704">\r
-<li>Go to the "Community AMI" tab and search for JABAWS, then click select.</li>\r
-<img src="images/aws_launch.gif" alt="select AMI" width="864" height="262">\r
- <li>Choose the "hardware" for your JABAWS server instance. "Large" instance should be sufficient for a single user needs. If you are planning to use this instance as a server for the lab, you may want to select a more powerful machine. Once you have chosen the hardware click continue. </li>\r
-\r
- <img src="images/aws_launch_instance.gif" alt="select hardware" width="872" height="590">\r
-\r
- <li>You should not need to customize anything on this page, continue to the next. </li>\r
-\r
- <img src="images/aws_launch_instance2.gif" alt="keys" width="872" height="592">\r
-\r
- <li> At the "Create a key pair" step, choose "Proceed without a key pair" unless you want to access JABAWS server via SSH. </li>\r
-\r
-<img src="images/aws_launch_instance3.gif" width="872" height="592">\r
- <li>Create a new security group with a single HTTP (80) port as shown below. You may want to add SSH (22) port if you are planning to manage your instance via SSH. For starting/stopping your JABAWS instance SSH is not necessary, you can do this from the Amazon Webservices Console (AWS). </li>\r
-\r
- <img src="images/aws_launch_instance_sec_group.gif" alt="ese" width="856" height="588">\r
- <li>Review the configuration and launch the instance, then click "view your instances on the Instances page". </li>\r
-<img src="images/aws_launch_instance5.gif" width="870" height="430">\r
-<li>At this point you should have JABAWS instance up and running. Your AWS console should look something like this: </li>\r
-<img src="images/aws_launch_instance_done.gif" width="812" height="848">\r
-<li>Now you can consume JABAWS web services by accessing the public DNS address of your JABAWS server instance. For instance, to register it with Jalview, just add the new JABAWS web server. Prefix your instance public DNS address with http:// e.g. type: http://<public DNS>. The JABAWS instance on the screenshot can be accessed on http://ec2-46-137-50-196.eu-west-1.compute.amazonaws.com. </li>\r
-</ol>\r
-<p>If you need to run JABAWS for large organization you might want to configure load balancer and auto scaling. Please get in contact with us if you are interested in exploring such configurations. </p>\r
-<p> </p>\r
-</div><!-- end of jabaws_on_cloud div -->\r
+<p>If you know what to do than JABAWS AMI ID is <strong>ami-40fecd34</strong>, manifest <strong>846107356395/JABAWS2</strong> to get you started, if not please refer to <a href="man_awscloud_ec2.html">How to use JABAWS on the Amazon EC2 cloud</a> pages. </p>\r
+<p>Alternatively you can use JABAWS on the <a href="http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/index.html?GettingStarted.html">Amazon Elastic BeanStalk</a>. You may want to use this option to deploy JABAWS in the cluster configuration.</p>\r
+</div> \r
+<!-- end of jabaws_on_cloud div -->\r
</div>\r
-\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
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<!DOCTYPE html PUBLIC "XHTML 1.0 Strict"\r
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
+<html xmlns="http://www.w3.org/1999/xhtml">\r
+<head>\r
+<meta name="Last-modified" content="Mon, 4 Apr 2011 12:00:00 GMT"/>\r
+<title>Java Bioinformatics Analyses Web Services (JABAWS) Server Virtual Appliance Manual</title>\r
+<link href="ws.css" rel="stylesheet" type="text/css" media=\r
+"screen, projection, handheld, tv" />\r
+<link rel="stylesheet" type="text/css" media="print" href=\r
+"print.css" />\r
+<script type="text/javascript" src="prototype-1.6.0.3.js"></script>\r
+<style type="text/css">\r
+<!--\r
+.style1 {font-family: Verdana, Arial, Helvetica, sans-serif}\r
+-->\r
+</style>\r
+</head>\r
+<body>\r
+<div id="page">\r
+<div id="banner">\r
+<table> \r
+<tr><td style="width:158px;"><a href="http://www.dundee.ac.uk"><img src="images/uod_lt_long.gif" alt="University of Dundee" width="158" height="90" class="logo" title="University of Dundee" longdesc="http://www.dundee.ac.uk"/></a></td>\r
+<td class="bg"><img src="images/jabaws2.png" alt="JABAWS-2.0:Disorder" width="353" height="67" title="JABAWS-2.0:Disorder"/></td>\r
+<td class="bg"><img src="images/banner_right.png" alt="Disorder" width="200" height="80"/></td>\r
+</tr>\r
+</table>\r
+</div><!-- banner end-->\r
+\r
+<div id="wrapper">\r
+<div id="panel"><a href="index.html">Home</a> \r
+ <a href="quick_start.html">Getting Started</a> \r
+ <a class="selected" href="man_about.html">Manual</a> \r
+ <div id="submenu">\r
+ <a href="man_about.html">About</a>\r
+ <a href="man_servervm.html" title="JABAWS Server as Virtual Appliance">Server VA</a>\r
+ <a class="selected" href="man_awscloud.html" title="JABAWS Server in the Amazon EC2 Cloud">Server in the Cloud</a>\r
+ <a href="man_serverwar.html" title="JABAWS Server as Web Application aRchive">Server WAR</a>\r
+ <a href="man_configuration.html" >Server<br/>\r
+ Configuration</a>\r
+ <a href="man_client.html" title="JABAWS Command Line Client">CMD Client</a>\r
+ <a href="man_stats.html" title="JABAWS Usage Statistics">Usage Statistics</a>\r
+ <a href="man_dev.html" title="Accessing JABAWS from your program">Accessing<br/>\r
+ JABAWS</a> \r
+ <a href="man_server_dev.html" >JABAWS Development</a>\r
+ </div>\r
+<a href="download.html">Download</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
+<!-- panel end-->\r
+<div id="content">\r
+<h2 id="headtitle">JABAWS MANUAL</h2>\r
+\r
+<h2>How to use JABAWS on Amazon Elastic Beanstalk</h2>\r
+<div id="jabaws_on_cloud">\r
+ <ol>\r
+ <li><a href="https://www.amazon.com/ap/signin/175-8261537-7969810?_encoding=UTF8&openid.assoc_handle=aws&openid.return_to=https%3A//aws-portal.amazon.com/gp/aws/developer/registration/index.html/175-8261537-7969810&openid.mode=checkid_setup&openid.ns=http%3A//specs.openid.net/auth/2.0&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.pape.max_auth_age=600&siteState=awsMode%3A%3Aregistration%3A%3AheaderMessage%3A%3AAmazon Web Services Sign Up%3A%3A&pageId=aws.ssop&openid.pape.preferred_auth_policies=http%3A//schemas.openid.net/pape/policies/2007/06/multi-factor-physical&marketplaceId=ATVPDKIKX0DER&accountStatusPolicy=P1&openid.ns.pape=http%3A//specs.openid.net/extensions/pape/1.0&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&authCookies=1">Create Amazon Web Services account</a>. </li>\r
+ <li><a href="https://console.aws.amazon.com/ec2/home?region=eu-west-1#selectInstance=&launchAmi=&s=Home">Log in into the Amazon Web Services (AWS) console</a> and switch to AWS Elastic Beanstalk view.</li>\r
+ <img src="images/aws_bs_launch.gif" alt="Elastic Beanstalk launch JABAWS war step 1" width="852" height="418">\r
+ <li>Create a new Beanstalk application by uploading JABAWS war file </li>\r
+ <img src="images/aws_bs_launch1.gif" alt="Elastic Beanstalk launch JABAWS war step 2" width="532" height="388"> \r
+ <li>Give a name to your JABAWS instance. This name will be a part of the access URL for your JABAWS. </li>\r
+ <img src="images/aws_bs_launch2.gif" alt="Elastic Beanstalk launch JABAWS war step 3" width="530" height="492">\r
+\r
+<li>Choose the type of hardware you want to run JABAWS on. </li>\r
+<img src="images/aws_bs_launch3.gif" alt="Elastic Beanstalk launch JABAWS war step 4"/> \r
+<li>If everything goes well you should be able to access your JABAWS on http://jabaws.elasticbeanstalk.com</li>\r
+<img src="images/aws_bs_done.gif" alt="Elastic Beanstalk launch JABAWS war " width="682" height="422"> \r
+</ol>\r
+<p> </p>\r
+</div> <!-- end of jabaws_on_cloud div -->\r
+</div>\r
+<!-- content end-->\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
+\r
+<!-- wrapper end-->\r
+</div>\r
+<!-- page end-->\r
+\r
+<!-- Google analitics -->\r
+<script type="text/javascript">\r
+var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");\r
+document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));\r
+</script>\r
+<script type="text/javascript">\r
+try{\r
+var pageTracker = _gat._getTracker("UA-5356328-1");\r
+pageTracker._trackPageview();\r
+} catch(err) {}\r
+</script>\r
+</body>\r
+</html>\r
+\r
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<!DOCTYPE html PUBLIC "XHTML 1.0 Strict"\r
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">\r
+<html xmlns="http://www.w3.org/1999/xhtml">\r
+<head>\r
+<meta name="Last-modified" content="Mon, 4 Apr 2011 12:00:00 GMT"/>\r
+<title>Java Bioinformatics Analyses Web Services (JABAWS) Server Virtual Appliance Manual</title>\r
+<link href="ws.css" rel="stylesheet" type="text/css" media=\r
+"screen, projection, handheld, tv" />\r
+<link rel="stylesheet" type="text/css" media="print" href=\r
+"print.css" />\r
+<script type="text/javascript" src="prototype-1.6.0.3.js"></script>\r
+<style type="text/css">\r
+<!--\r
+.style1 {font-family: Verdana, Arial, Helvetica, sans-serif}\r
+-->\r
+</style>\r
+</head>\r
+<body>\r
+<div id="page">\r
+<div id="banner">\r
+<table> \r
+<tr><td style="width:158px;"><a href="http://www.dundee.ac.uk"><img src="images/uod_lt_long.gif" alt="University of Dundee" width="158" height="90" class="logo" title="University of Dundee" longdesc="http://www.dundee.ac.uk"/></a></td>\r
+<td class="bg"><img src="images/jabaws2.png" alt="JABAWS-2.0:Disorder" width="353" height="67" title="JABAWS-2.0:Disorder"/></td>\r
+<td class="bg"><img src="images/banner_right.png" alt="Disorder" width="200" height="80"/></td>\r
+</tr>\r
+</table>\r
+</div><!-- banner end-->\r
+\r
+<div id="wrapper">\r
+<div id="panel"><a href="index.html">Home</a> \r
+ <a href="quick_start.html">Getting Started</a> \r
+ <a class="selected" href="man_about.html">Manual</a> \r
+ <div id="submenu">\r
+ <a href="man_about.html">About</a>\r
+ <a href="man_servervm.html" title="JABAWS Server as Virtual Appliance">Server VA</a>\r
+ <a class="selected" href="man_awscloud.html" title="JABAWS Server in the Amazon EC2 Cloud">Server in the Cloud</a>\r
+ <a href="man_serverwar.html" title="JABAWS Server as Web Application aRchive">Server WAR</a>\r
+ <a href="man_configuration.html" >Server<br/>\r
+ Configuration</a>\r
+ <a href="man_client.html" title="JABAWS Command Line Client">CMD Client</a>\r
+ <a href="man_stats.html" title="JABAWS Usage Statistics">Usage Statistics</a>\r
+ <a href="man_dev.html" title="Accessing JABAWS from your program">Accessing<br/>\r
+ JABAWS</a> \r
+ <a href="man_server_dev.html" >JABAWS Development</a>\r
+ </div>\r
+<a href="download.html">Download</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
+<!-- panel end-->\r
+<div id="content">\r
+<h2 id="headtitle">JABAWS MANUAL</h2>\r
+\r
+<h2><a name="jabawsOnCloudHow" id="jabawsOnCloudHow"/></a>How to use JABAWS on the Amazon EC2 cloud </h2>\r
+<div id="jabaws_on_cloud">\r
+ <ol>\r
+ <li><a href="https://www.amazon.com/ap/signin/175-8261537-7969810?_encoding=UTF8&openid.assoc_handle=aws&openid.return_to=https%3A//aws-portal.amazon.com/gp/aws/developer/registration/index.html/175-8261537-7969810&openid.mode=checkid_setup&openid.ns=http%3A//specs.openid.net/auth/2.0&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.pape.max_auth_age=600&siteState=awsMode%3A%3Aregistration%3A%3AheaderMessage%3A%3AAmazon Web Services Sign Up%3A%3A&pageId=aws.ssop&openid.pape.preferred_auth_policies=http%3A//schemas.openid.net/pape/policies/2007/06/multi-factor-physical&marketplaceId=ATVPDKIKX0DER&accountStatusPolicy=P1&openid.ns.pape=http%3A//specs.openid.net/extensions/pape/1.0&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&authCookies=1">Create Amazon Web Services account</a>. </li>\r
+ <li><a href="https://console.aws.amazon.com/ec2/home?region=eu-west-1#selectInstance=&launchAmi=&s=Home">Log in into the Amazon Web Services (AWS) console.</a> Make sure you are in the EU West (Ireland) region. JABAWS image is not available in other regions as yet. See marker 1. </li>\r
+ <li>Click on "Launch Instance" button marker 2. </li>\r
+\r
+<img src="images/aws_console_launch.gif" alt="AWS console" width="687" height="704">\r
+<li>Go to the "Community AMI" tab and search for JABAWS, then click select.</li>\r
+<img src="images/aws_launch.gif" alt="select AMI" width="864" height="262">\r
+ <li>Choose the "hardware" for your JABAWS server instance. "Large" instance should be sufficient for a single user needs. If you are planning to use this instance as a server for the lab, you may want to select a more powerful machine. Once you have chosen the hardware click continue. </li>\r
+\r
+ <img src="images/aws_launch_instance.gif" alt="select hardware" width="872" height="590">\r
+\r
+ <li>You should not need to customize anything on this page, continue to the next. </li>\r
+\r
+ <img src="images/aws_launch_instance2.gif" alt="keys" width="872" height="592">\r
+\r
+ <li> At the "Create a key pair" step, choose "Proceed without a key pair" unless you want to access JABAWS server via SSH. </li>\r
+\r
+<img src="images/aws_launch_instance3.gif" width="872" height="592">\r
+ <li>Create a new security group with a single HTTP (80) port as shown below. You may want to add SSH (22) port if you are planning to manage your instance via SSH. For starting/stopping your JABAWS instance SSH is not necessary, you can do this from the Amazon Webservices Console (AWS). </li>\r
+\r
+ <img src="images/aws_launch_instance_sec_group.gif" alt="ese" width="856" height="588">\r
+ <li>Review the configuration and launch the instance, then click "view your instances on the Instances page". </li>\r
+<img src="images/aws_launch_instance5.gif" width="870" height="430">\r
+<li>At this point you should have JABAWS instance up and running. Your AWS console should look something like this: </li>\r
+<img src="images/aws_launch_instance_done.gif" width="812" height="848">\r
+<li>Now you can consume JABAWS web services by accessing the public DNS address of your JABAWS server instance. For instance, to register it with Jalview, just add the new JABAWS web server. Prefix your instance public DNS address with http:// e.g. type: http://<public DNS>. The JABAWS instance on the screenshot can be accessed on http://ec2-46-137-50-196.eu-west-1.compute.amazonaws.com. </li>\r
+</ol>\r
+<p>If you need to run JABAWS for large organization you might want to configure load balancer and auto scaling. Please get in contact with us if you are interested in exploring such configurations. </p>\r
+<p> </p>\r
+</div> <!-- end of jabaws_on_cloud div -->\r
+</div>\r
+<!-- content end-->\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
+\r
+<!-- wrapper end-->\r
+</div>\r
+<!-- page end-->\r
+\r
+<!-- Google analitics -->\r
+<script type="text/javascript">\r
+var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");\r
+document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));\r
+</script>\r
+<script type="text/javascript">\r
+try{\r
+var pageTracker = _gat._getTracker("UA-5356328-1");\r
+pageTracker._trackPageview();\r
+} catch(err) {}\r
+</script>\r
+</body>\r
+</html>\r
+\r
<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
</div>\r
\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
<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
<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 server 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
\r
</div>\r
</div>\r
\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
<a class="selected" 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
<!-- panel end-->\r
<p> </p>\r
</div>\r
<!-- content end--> \r
-<div id="copyright">Last update: 2 August 2011<br/>\r
+<div id="copyright">Last update: 16 September 2011<br/>\r
Peter Troshin, The Barton Group, University of Dundee, UK</div>\r
</div><!-- wrapper end-->\r
</div> <!-- page end-->\r
<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
</div>\r
\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
<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 server 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></div>\r
\r
<!-- panel end-->\r
\r
<h3><a name="useprebin" id="useprebin"></a>Using the pre-compiled i386 binaries on Linux</h3>\r
\r
-<p>Before the binaries that are bundled with JABAWS can be used,\r
-they must first be made executable using the provided <a name=\r
-"setexecflag" id="setexecflag">'setexecflag.sh'</a> script:</p>\r
-\r
-<ol>\r
-<li>cd to <span class=\r
-"hightlight"><webapplicationpath>/binaries/src</span></li>\r
-\r
-<li>run <span class="hightlight">sh setexecflag.sh</span></li>\r
-\r
-<li>Make sure binaries supplied work under your OS.<br />\r
- For this run each binary, without any command line options or\r
+<p>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\r
input files. If you see an error message complaining about missing\r
libraries or other problems, then you probably need to <a href=\r
-"#recompbinaries">recompile the binaries</a>.</li>\r
-\r
-<li>Restart the Tomcat.</li>\r
-</ol>\r
+"#recompbinaries">recompile the binaries</a>.</p>\r
\r
-That's it! JABAWS should work at this point. Try it out using the JABAWS<a\r
-href="#usingWsTester"> test client</a>. If not,\r
-read on... or have a look at <a href="http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html">deploying on Tomcat</a> tips.<br />\r
+You can try the JABAWS functionality with the JABAWS<a\r
+href="#usingWsTester"> test client</a> or have a look at <a href="http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html">deploying on Tomcat</a> tips if you experience any problems.<br />\r
<em>Note: You may want to enable logging, <a href="man_configuration.html#logfiles"> as described here</a></em>.<br />\r
\r
\r
<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>\r
</ul>\r
<h3><a name="usingWsTester" id="usingWsTester"></a>Testing JABAWS Server </h3>\r
-<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. 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:<span class="code"> java -jar jabaws-client.jar -h=<Your web application server host name, port and JABAWS context path></span></p>\r
+<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>\r
+<p>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:<span class="code"> java -jar jabaws-client.jar -h=<Your web application server host name, port and JABAWS context path></span></p>\r
<p>For example to test all JABAWS web services on host myhost.compbio.ac.uk type: </p>\r
<p class="code">java -jar jabaws-client.jar -h=http://myhost.compbio.ac.uk:8080/jabaws </p>\r
<p>You can choose a particular web server using -s option like this <span class="code">java -jar jabaws-client.jar -h=http://myhost.compbio.ac.uk:8080/jabaws -s=ClustalWS </span>This command line assumes that java executable is in your path and jabaws-client.jar is located in the current directory.</p>\r
</div>\r
\r
<!-- content end-->\r
-<div id="copyright">Last update: 1 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
<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 server 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
</div>\r
\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
<a class="selected" href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a>\r
- <a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS server 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></div>\r
\r
<!-- panel end--> \r
</tr>\r
<tr>\r
<td>Running JABAWS on the <strong>cloud</strong>, for one or many users</td>\r
- <td><a href="man_awscloud.html">JABAWS AMI</a></td>\r
+ <td><a href="man_awscloud.html">JABAWS on the Amazon cloud </a></td>\r
</tr>\r
<tr>\r
<td>Running JABAWS for my group, lab, or organization on the <strong>local</strong> infrastructure </td>\r
<!-- about end-->\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 Dundee, UK</div>\r
</div><!-- wrapper end-->\r
</div> <!-- page end-->\r
<a class="selected" href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a>\r
- <a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS server 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></div>\r
<!-- panel end-->\r
<div id="content">\r
</tr>\r
<tr>\r
<td>Running JABAWS on the <strong>cloud</strong>, for one or many users</td>\r
- <td><a href="man_awscloud.html">JABAWS AMI</a></td>\r
+ <td><a href="man_awscloud.html">JABAWS on the Amazon cloud </a></td>\r
</tr>\r
<tr>\r
<td>Running JABAWS for my group, lab, or organization on the <strong>local</strong> infrastructure </td>\r
<p>If you work on Mac do the same using <a href="http://www.vmware.com/products/fusion/overview.html">VMware Fusion</a>, or for free alternative use a WAR JABAWS package. </p>\r
<div id="testing_jabaws">\r
<h3>Testing</h3>\r
-<p>The easiest way to test that your JABAWS Virtual appliance is working is to use Jalview.</p>\r
-<ol>\r
- <li>Launch the desktop version of <a href="http://www.jalview.org/download.html">Jalview</a></li>\r
+<p>To check that your JABAWS virtual appliance is working visit the Services Status page available from the main JABAWS menu. For this enter the JABAWS URL for your new server into a web browser. This is shown once the appliance is booted up. </p>\r
+<p>Alternatively you can use Jalview to complete the testing. </p>\r
+<ol><li>Launch the desktop version of <a href="http://www.jalview.org/download.html">Jalview</a></li>\r
<li>Open the Jalview desktop's preferences panel (from the Tools->Preferences menu option), select the <span class="hightlight">Webservices</span> panel and press the <span class="hightlight">New Service URL</span> button.</li>\r
<li>Enter the JABAWS URL for your new server. This is shown once the appliance is booted up.</li>\r
</ol>\r
<!-- about end-->\r
</div>\r
<!-- content end--> \r
-<div id="copyright">Last update: 1 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 Dundee, UK</div>\r
</div><!-- wrapper end-->\r
</div> <!-- page end-->\r
<a class="selected" href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a>\r
- <a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS server 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
\r
</div><!-- panel end-->\r
</tr>\r
<tr>\r
<td>Running JABAWS on the <strong>cloud</strong>, for one or many users</td>\r
- <td><a href="man_awscloud.html">JABAWS AMI</a></td>\r
+ <td><a href="man_awscloud.html">JABAWS on the Amazon cloud </a></td>\r
</tr>\r
<tr>\r
<td>Running JABAWS for my group, lab, or organization on the <strong>local</strong> infrastructure </td>\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
+ <li> You then need to complete the installation of the executable binaries (this is optional if you use 32 bit version of Linux):</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
+ <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
</ol> \r
\r
<h3>Testing</h3>\r
-<p>You can test that your JABAWS server is working in two ways.</p>\r
+<p>You can test that your JABAWS server is working in several ways.</p>\r
<ol>\r
+<li>Visit Services Status page available from the main menu using your web browser.</li>\r
+\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 <Path to tomcat WebApp directory>/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
+ <span class="code">java -jar <Path to tomcat WebApp directory>/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
<li>Alternately, you can point Jalview at your new server:\r
<ul>\r
<li>Launch the desktop version of <a href="http://www.jalview.org/download.html">Jalview</a></li>\r
<!-- TODO put JABAWS CMD test instructions here -->\r
</div> <!-- content end-->\r
<!-- about 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 Dundee, UK</div>\r
\r
</div><!-- wrapper end -->\r
<a class="selected" href="quick_start.html">Getting Started</a> \r
<a href="man_about.html">Manual</a> \r
<a href="download.html">Download</a>\r
- <a href="contacts.html">Contact Us</a>\r
<a href="PublicAnnualStat" title="JABAWS server 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></div>\r
\r
<!-- panel end-->\r
</tr>\r
<tr>\r
<td>Running JABAWS on the <strong>cloud</strong>, for one or many users</td>\r
- <td><a href="man_awscloud.html">JABAWS AMI</a></td>\r
+ <td><a href="man_awscloud.html">JABAWS on the Amazon cloud</a></td>\r
</tr>\r
<tr>\r
<td>Running JABAWS for my group, lab, or organization on the <strong>local</strong> infrastructure </td>\r
<!-- about end-->\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 Dundee, UK</div>\r
</div><!-- wrapper end-->\r
</div> <!-- page end-->\r