EasierCos Overview

Version 4 by Julien Lesbegueries
on Aug 31, 2011 17:52.

<< Changes from 3 to 4

compared with

Version 5 by Julien Lesbegueries
on Aug 31, 2011 17:55.

Changes from 5 to 6 >>

Key

This line was removed.

This word was removed. This word was added.

This line was added.

Changes (4)

View Page History

EasierCos is an implementation of a choreography engine. It aims at interpreting choreography processes and executing them in a SOA middleware. As for [EasyBPEL|easybpel:EasyBPEL Overview] that manages the WS-BPEL 2.0 layer, EasierCos manages the BPMN 2.0 layer (Choreography Modeling Conformance).
Both of us are based on the generic SOA process engine [EasyVIPER|easyviper:EasyViper Overview].

...

h1. How does it work?

The main job is done by EasyVIPER. It executes the choreography as an execution graph (with exclusive and inclusive gateways), into which nodes correspond to choreography tasks.

The main job is done by EasyVIPER. It executes the choreography as an execution graph (exclusive and inclusive gateways have been intepreted as corresponding EasyVIPER behaviours at compilation time), into which nodes correspond to choreography tasks.

Indeed, EasyVIPER provides main behaviours related to SOA process execution, such as Receiver, Sender, Loop, If,...
Furthermore, we can benefit from the fact it's an extensible library, for which new behaviours can be implemented. A new behaviour dedicated to the choreography is then implemented. This behaviour, called MEMB (for Message Exchange Monitoring Behaviour), is a WS-Notification consumer that previously subscribed on specific topics related to partners and that is able to check notifications validity.

If you want know how to use {report-info:page:space > space:name} library, please consult the list of [How-tos|How-tos].
If you have any questions, please use the \[{report-info:page:space > space:name} contact form\|Contact\].