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 . ESB. ESB. Making business processes responsive to disengaged EVENT data . Transaction Choreography. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
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
EDA as coupling between deployed processes e.g. stock trading / compliance
Compliance process
TRADES event topic
Retained event history
Business process serverESB
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 )
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
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