1. IBM Research – Thomas J Watson Research Center | March 2006 © 2006 IBM Corporation Events and workflow – BPM Systems Event Application symposium Parallel Session on Event processing in Workflows 13-15 th March 2006 Francis N Parr – IBM Research Hawthorne

2. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Making business processes responsive to disengaged EVENT data Internet with application and process servers 1995 - 2005 central transaction and database server 70’s - 80’s – early 90’s … to be augmented with events Information and business process management - transactional - request / rsp Information gather- ing and automation asynchronous disengaged data staged data filtering pruning ESB Sensors, RFID readers… Control nets,actuators Application history, data warehouse PDA data Process Choreography Transaction Choreography Events: Process & Data Choreography ESB

3. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Business Process Servers extended with Events coupled to ESB  Application and process servers harden business states into database and advance business process by updating this state in place  Events are disengaged, non updatable data, organized in streams, from many sources, not updatable ( reference data ), asynchronous  In Event Driven Architecture, application intelligence is organized into  Sense ( and emit ) of events and event patterns - from event middleware  Processing / business response – the middle steps of MAPE loop – supported by existing transactional, web, application servers  Event interfaces:  Event selection – by event consuming endpoint applications – specifying patterns of events to be detected by event middleware  Event mediations – Event Processing Networks – enrich events  Event emit  Role and value of Enterprise Systems Bus enhanced with events  Unifies reference data fetching with messaging, correlation, aggregation

4. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation SOA – includes EDA as a special case  SOA enables solution construction from loosely coupled components  Including application assembly from service and distributed object components  EDA for consumer directed assembly of useful information from lower level event messages from autonomous sources  Both using a common messaging substrate triggers Sense state Event driven choreography Application integration Event integration

5. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation EDA – levels of Event capability 1.Pure Publish Subscribe ( as in JMS today) 2.Events are persisted in the middleware for historical retrieval push sources alert and retrieve consumers 3.On demand event retrieval with multiple QOS,QOI Two-way event propagation with Push-Pull sources and consumers 4.Event information processing - event brokers Includes CEP, correlation, aggregation Targeted at both business and IT events 5.Integration/programming Model for EDA event consumer model/lifecycle complementing,SOA programming model Distributed deployment of event selection Event driven business application choreography Source lifecycle model for metadata and semantics  Each level requires additional metadata, management and tooling

6. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Event Consumer Y Event Consumer X Event Producer A Event Producer B Concept: two way propagation within an Event Bus Event mediations / Event Processing Services Event History Event Metadata publish Event Metadata subscribe retrieve Notify retrieve Provide metadata On demand Event History SCA SDO Event topics Event applications Notify

7. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Event Processing network EE Event endpoint ET Event topic EM event mediation EE EM ET Event mediations derive higher level event information

8. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Two application scenarios  Coupling Event driven business operations  Energy –control optimization – associated business process interactions

9. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation EDA as coupling between deployed processes e.g. stock trading / compliance Compliance process TRADES event topic Retained event history Business process server ESB Trading process Trade event emit Placed executed Select based trigger >$1M buy + >$1Msell same stock, 24 hrs Select based retrieve similar pattern historical pull A: Trading process handles execution of trades -- i.e. Broker – client – exchange interaction – emits TRADE events ( placed, executed ) B: Compliance process on trade anomalies as before A B business process -> events -> business process ( invocation, request, emit )

10. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation EDA for dynamic business process interactions eg stock trading / compliance Compliance process TRADES event topic Retained event history Business Process server ESB Trading process Trade event emit Placed executed Select trigger Select based retrieve similar pattern historical pull C cancellation of trading privileges on too many anomalies or bad compliance audit may affect new process instances, or call, or cancel etc B C Emit Audit event AUDITS event topic A Select threshhold process modify business process -> events -> dynamic modify of business process

11. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Specific motivating examples  Trading – compliance audit and response  Processing of Multiple RFQ in online marketplace  Modification of insurance claims processing in response to initial assessor reports

12. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Local and distributed scopes for event interactions TRADES event topic Retained event history ESB May be helpful to have event scopes local event interactions between processes of a single environment enterprise wide interaction involving other sources and sinks public internet wide ? Interaction between workflow based and other event sources and consumers may drive multi level event system design AUDITS event topic business process -> events -> dynamic modify of business process Business Process server 1 A Event specif- ication Business Process server 2 A Event specif- ication Other event sources and event consuming environments Event specif- ication

13. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Multilevel event coupled systems from workflow to sensors and actuators Business process server Enterprise business processes and workflows Sensor and actuator components Dispersed (on premise) application servers and controllers with event capabilities End-to-end Multi layer Event based Workflow design

14. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation

15. IBM T J Watson Research Center Events and Workflow | © 2006 IBM Corporation Summary – a point of view  Events – disengaged data-on-the move will be used to enrich workflow and application server environments  Allowing services to interact via events makes this a natural extension of the SOA paradigm  Declarative event emit and consume specifications on workflows with implementations pushed down into middleware will minimize loss of control through dispersed business process logic  Dynamic process interactions can be provided with workflow interfaces for exceptional and unexpected events  Scoping of events, and eventually multilevel end-to-end event based workflows can allow line of business workflows to reach down to sensor and actuator endpoints.  => Event technology can benefit both the process–to-process interactions in workflow systems AND the design of data flows feeding / responding to them