<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
git://source.jalview.org / jabaws.git / blobdiff