Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Tutorial/4.0/cloud/Cloud Step-by-Step"
(→RabbitMQ) |
|||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ScoutPage|cat= | + | {{ScoutPage|cat=Tutorial 4.0}} |
| − | + | {{warning|This tutorial is still under cunstruction}} | |
| − | This tutorial | + | |
| − | == | + | == Introduction == |
| − | + | ||
| − | + | Since the Lune Release Eclipse Scout supports dynamic scalable server applications. | |
| − | + | The motivation behind adding this feature is described in this [http://www.bsiag.com/scout/eclipse-luna-scout-cloud-apps/ Scout blog post]. For further information please read the master thesis about [[media:eclipse_scout_in_the_cloud_master_thesis.pdf|Scout in the Cloud (German)]]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | With the cloud support added to Scout 4.0 it is possible to run several instances of the server application and place them behind a load balancer. For the synchronization between the server nodes it's necessary to use two additional external services. A Cache Service and a Message Queue. | |
| − | + | ||
| + | Scout developers are able to either use one of the default implementations for cache services and message queue services or implement their own custom synchronization service connectors. | ||
| + | The Scout default implementations are available from the [http://marketplace.eclipse.org Eclipse Marketplace]. | ||
| + | For chache services, default implementations are based on Memcached or Redis, and for message queue services the default implementations are based on RabbitMQ and AciveMQ. | ||
| − | == | + | == Preparation == |
| − | + | First we create a new Scout "Hello World" application as described in the [[Scout/Tutorial/4.0/HelloWorld|Hello World tutorial]]. | |
| − | + | ||
| − | + | == Add Cloud Support to your Application == | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | The second Step is to add the support of the cloud features to your application. Follow the [[{{BASEPAGENAME}}/add_cloud_support|instructions]]. | |
| − | + | ||
| − | === | + | == Deploy to the Cloud == |
| − | + | ||
| − | + | Finally you are able to deploy you eclipse scout server application to the cloud. | |
| + | How to do this on the example of Amazon Beanstalk you can find [[{{BASEPAGENAME}}/deploy_on_cloud|here]]. | ||
| − | + | == Deploy to a Local Cluster == | |
| − | + | If you want to test your application on your local machine you will fin the instructions [[{{BASEPAGENAME}}/local cloud|here]]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 06:34, 6 August 2014
The Scout documentation has been moved to https://eclipsescout.github.io/.
Contents
Introduction
Since the Lune Release Eclipse Scout supports dynamic scalable server applications. The motivation behind adding this feature is described in this Scout blog post. For further information please read the master thesis about Scout in the Cloud (German).
With the cloud support added to Scout 4.0 it is possible to run several instances of the server application and place them behind a load balancer. For the synchronization between the server nodes it's necessary to use two additional external services. A Cache Service and a Message Queue.
Scout developers are able to either use one of the default implementations for cache services and message queue services or implement their own custom synchronization service connectors. The Scout default implementations are available from the Eclipse Marketplace. For chache services, default implementations are based on Memcached or Redis, and for message queue services the default implementations are based on RabbitMQ and AciveMQ.
Preparation
First we create a new Scout "Hello World" application as described in the Hello World tutorial.
Add Cloud Support to your Application
The second Step is to add the support of the cloud features to your application. Follow the instructions.
Deploy to the Cloud
Finally you are able to deploy you eclipse scout server application to the cloud. How to do this on the example of Amazon Beanstalk you can find here.
Deploy to a Local Cluster
If you want to test your application on your local machine you will fin the instructions here.