Embed Size (px)
DESCRIPTION
This presentation demonstrates an approach to terminate (or influence) multiple BPEL instances as a result of a single Event on the Event Delivery Network. Based on a blog article - http://technology.amis.nl/2011/10/07/soa-suite-11g-event-delivery-network-how-to-correlate-one-event-into-multiple-instances-of-the-same-composite-bpel-or-bpm/ - I have used a Spring Component, Composite Sensors and the SOA Suite Java API to make this work. All order processes running for a single customer will be terminated when the TerminateCustomer event is published for that customer.
Citation preview
Correlate on Event into Multiple BPEL process instances
Fan Out Events using:Composite Sensors, Spring
Component, SOA Suite Java API
Customer Identifier Order Identifier
ABC 123A
123B
123C
XYZ 345X
346X
347X
348X
349X
PQR 567P
568P
569P
http://technology.amis.nl/2011/06/21/keeping-your-process-clean-hiding-technology-complexity-behind-a-service/
http://docs.oracle.com/cd/E15586_01/integration.1111/e10224/sca_spring.htm
https://blogs.oracle.com/soabpm/entry/using_the_new_11g_soa_suite_ap
http://sridhar-oraclefusion.blogspot.nl/2011/11/correlate-one-event-into-multiple.html
http://technology.amis.nl/2011/10/07/soa-suite-11g-event-delivery-network-how-to-correlate-one-event-into-multiple-instances-of-the-same-composite-bpel-or-bpm/
