{children:excerpt=true}
Main results of Genesis concern works on Petals ESB and the BPEL engine.
* Petals ESB as an Event Driven Architecture (EDA):
** [WS-Notification|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn] library implemented (TODO link to source)
** [Broker component|wsnotification:How to use libraries - Samples] according to the Brokered Notification (TODO link to source),
** These results allow to build a distributed system of alerts sent by several environmental sensors and brokered to several alerts processing services. Final reports summarizing alerts are sent to the GENESIS portal. The following figure represents an example of architecture available with Petals ESB.
{center}
!ESB-EDA.png|border=1,width=600!
Petals ESB as an Event Driven Architecture.
{center}
Partners 1, 2, 3 or 4 can either be consumers or producers of notifications. The se-notification is a broker managing and aggregating subscriptions and registrations.
* Petals ESB enhanced for Geo-processing workflow compliance:
** Service extension of geo-processing workflow (WPS) administration (see the how-to for Services extensibility of Petals ESB (DSB?))
** Enhancement of EasyBPEL in order for the engine to be able to invoke asynchronous Web Service using WS-Addressing (see the [how-to on EasyBPEL extended activity|easybpel:How to implement an extended activity in EasyBPEL?]).
* [GEasyBPMN|geasybpmndesigner:GEasyBPMNEditor Overview] editor enhanced to provide BPMN 2.0 to BPEL 2.0 transformation.(TODO see doc on GeasyBPMN). This Web-based GUI allows to design geo-processing workflows with high-level representation. The transformation tools tries to automate this hidh-level description to an executable one.
!Sans bpmnEditor.JPG|border=1!
Main results of Genesis concern works on Petals ESB and the BPEL engine.
* Petals ESB as an Event Driven Architecture (EDA):
** [WS-Notification|http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn] library implemented (TODO link to source)
** [Broker component|wsnotification:How to use libraries - Samples] according to the Brokered Notification (TODO link to source),
** These results allow to build a distributed system of alerts sent by several environmental sensors and brokered to several alerts processing services. Final reports summarizing alerts are sent to the GENESIS portal. The following figure represents an example of architecture available with Petals ESB.
{center}
!ESB-EDA.png|border=1,width=600!
Petals ESB as an Event Driven Architecture.
{center}
Partners 1, 2, 3 or 4 can either be consumers or producers of notifications. The se-notification is a broker managing and aggregating subscriptions and registrations.
* Petals ESB enhanced for Geo-processing workflow compliance:
** Service extension of geo-processing workflow (WPS) administration (see the how-to for Services extensibility of Petals ESB (DSB?))
** Enhancement of EasyBPEL in order for the engine to be able to invoke asynchronous Web Service using WS-Addressing (see the [how-to on EasyBPEL extended activity|easybpel:How to implement an extended activity in EasyBPEL?]).
* [GEasyBPMN|geasybpmndesigner:GEasyBPMNEditor Overview] editor enhanced to provide BPMN 2.0 to BPEL 2.0 transformation.(TODO see doc on GeasyBPMN). This Web-based GUI allows to design geo-processing workflows with high-level representation. The transformation tools tries to automate this hidh-level description to an executable one.
!Sans bpmnEditor.JPG|border=1!