IBM Research Thomas J Watson Research Center

IBM Research – Thomas J Watson Research Center 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 | March 2006 © 2006 IBM Corporation

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

IBM T J Watson Research Center 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 Events and Workflow | © 2006 IBM Corporation

IBM T J Watson Research Center 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 Application integration triggers Event integration Sense state Event driven choreography Events and Workflow | © 2006 IBM Corporation

IBM T J Watson Research Center EDA – levels of Event capability 1. Pure Publish Subscribe ( as in JMS today) 2. Events are persisted in the middleware for historical retrieval 3. 4. 5. Ø • • push sources alert and retrieve consumers On demand event retrieval with multiple QOS, QOI • Two-way event propagation with Push-Pull sources and consumers Event information processing - event brokers • • Includes CEP, correlation, aggregation Targeted at both business and IT events 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 Events and Workflow | © 2006 IBM Corporation

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

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

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

IBM T J Watson Research Center EDA as coupling between deployed processes e. g. stock trading / compliance business process -> events -> business process ( invocation, request, emit ) ESB Business process server Retained event history Trade event emit • Placed • executed A TRADES event topic Trading process Select based trigger • >$1 M buy + >$1 Msell • 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 • B: Compliance process on trade anomalies as before Events and Workflow | © 2006 IBM Corporation

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

IBM T J Watson Research Center 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 Events and Workflow | © 2006 IBM Corporation

IBM T J Watson Research Center Local and distributed scopes for event interactions business process -> events -> dynamic modify of business process ESB Business Process server 1 Business Process server 2 A Event specification Retained event history AUDITS event topic TRADES event topic Other event sources and event consuming environments Event specification A Event specification • 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 Events and Workflow | © 2006 IBM Corporation

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

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

IBM T J Watson Research Center 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 Events and Workflow | © 2006 IBM Corporation