Sea Cloud

Funtionality:

The SeaCloud (for Services/Events Administration Cloud) is the frontal of Soceda RunTime Framework. It allows to client to subscribe to a specific producer, to add CEP rules or deploy BPEL process.

Technical Requirements:

The SeaCloud needs Java 6 or higher to run. On some node deployments, specific network ports needs to be open to enable node to node communication.
The source code is available at: https://svn.petalslink.org/svnroot/trunk/research/commons/seacloud

Prerequisites:
  1. Download java jdk 1.6
  2. Set JAVA_HOME in your classpath
  3. Copy this endorsed directory in jre library: $JAVA_HOME/jre/lib (for linux/windows) and $JAVA_HOME/lib (for mac)
  4. Download maven 2.2.1
  5. Set MAVEN_HOME in your classpath
  6. Set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=256m in your classpath
  • To get Project source code, you must:
    1. Install a svn client such as TortoiseSVN for Windows or use the native SVN client from your Unix-based distribution
    2. Perform a svn checkout at this url source code
  • To compile Project source code, you must:
    1. Write this command lin on the prompt of your shell: mvn install
If you want compile without run all tests, write: mvn install -Dmaven.test.skip
  • To import Project in Eclipse, you must:
    1. Download the source code
    2. Invoke the Eclipse plugin from the shell like 'mvn eclipse:eclipse'
    3. Open Eclipse IDE and click on: File => Import
    4. In Wizzard, choose: General => Existing Projects in Workspace
    5. Select the root directory of the project and click on finish

Components Architecture:

The SeaCloud is composed of 3 components:

  • SubscribeDeployer: This component is in charge of realizing a subscription from a client request. To do this, it must realize a check on Event Cloud to get the identifier of valid Event Cloud Node in a first time and then send the subscribe request on this valid Event Cloud Node.
  • CEPRulesDecomposer: This component is in charge to decompose the CEP rules sent by clients to realize subscribe on primitive topic used in the rules. This subscription are sent on
    Event Cloud Node corresponding to the topic.
  • ProcessDeployer: This component received the BPEL process sent by clients and analyze it to change the location of subscription towards the valid Event Cloud Node.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.