|
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). h1. EasierCos functionality
{center}
!airport{center}UseCase.png|border=1!
BPMN choreography: airport use case involving 5 partners.
{center}
EasierCos takes as input a BPMN (Choreography) process. It compiles it in order to generate an EasyVIPER process instance, that consists in an executable graph composed of behaviours dedicated to the choreography. Once started, a process instance subscribes to partners involved in the choreography relationships.
...h1. How does it work?
The main job is done by EasyVIPER. It Once compiled by EasierCos, EasyVIPER 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.
{center}
!EasyBPMNModel.png|border=1!
EasierCos layer architecture: compilation and process definition registry.
{center}
!EasyBPMNModel.png|border=1!
EasierCos layer architecture: compilation and process definition registry.
{center}
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.
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.
...