h2. 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.
h2. 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]
h2. Components Architecture:
!SeaCloud.png|align=center!
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.
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.
h2. 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]
h2. Components Architecture:
!SeaCloud.png|align=center!
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.