Event Processing Overview


Published on

Overview of event processing

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

  • This illustrates a conceptual view of the event processing flow. There are 3 basic elements – events, the event processing system and actions. Again, events are any electronic message or signal emitted or published by any process executing in the extended information infrastructure, including sensors, databases, 3rd party application suites, legacy applications, business process workflows, activity monitors, content from external sources, transactions, for example, from CICS. Although events can be sent directly to the event processing system, most often events are published to an enterprise message transport service such as JMS, IBM’s MQ, Message Broker or Enterprise Service Bus. Our use of the cloud illustrates events published to the enterprise message service. Any process can subscribe or consume events from the cloud. In this illustration, we show the WBE system (running on any network server) subscribing to certain events of interest, as defined by the user. When events are consumed, the WBE system immediately attempts to execute the user defined logic . This logic is used by WBE to understand which events are of interest, how to evaluate and correlate events for detecting event patterns and what actions or responses to create and emit when actionable events or patterns are detected. Actions, like events are electronic messages emitted by the WBE system. Action messages are used to inform people or other systems when an actionable situation has been detected. Presumably, when informed, people will react and systems will execute.. An action might be an email alert, an update to a dashboard or a database, a message to a transaction processing system or a message that might initiate the processing of an application or invoke a business process or service. Actions can be communicated directly to a system, published to the message transport service for consumption by any process or transmitted directly back into the WBE system for recursive event processing. In summary, events are emitted, communicated, and then processed by WBE, where, when actionable situations are discovered, action messages are published by WBE informing people or systems of the situation resulting in a response. This intelligent sense and respond processing is often a continuous recursive flow of events and actions among systems driven by the processing of events. This flow mimics how businesses operated before automation – when certain actives occurred in one department, it would trigger a response from another department, which when completed would initiate activities in yet another group and so on and so on until the process came to a logical conclusion. For example; if there are 3 product inquires from the same perspective client within a 5 day period, respond by initiating sales activities, resulting in a purchase, which drives a product order, requiring shipment, billing and accounts receivable activities. The right-time processing of these disparate systems was coordinated based on a preceding event or an event pattern.
  • Filters, or conditions, come in two flavors – “data” filters and “stream” filters. Data filters operate against the Intermediate Object (in-memory data) layer which can be populated by the event or other methods (DB, Web Service, etc. – as defined by the IT person when the objects were created). Stream filters allow correlation of the event triggering the rule with any other event or action (or combination) in the application. The context in which to relate the events and actions is called a “Stream ID” or “Context ID” which can be any Intermediate Object field. In this example, the Stream ID is the Customer ID which tells the rule to look for any PIN changes for that customer. If a different Stream ID were used in this example (such as “ATM ID”), then the rule would look for a PIN change from the same ATM in the past 24 hours (in that case the customer id would be irrelevant).

    In addition, any number of actions may result in a rule evaluating to true. In this case, if the conditions are true (the withdrawal amount was above $1,000 and the customer changed his/her PIN in the last 24 hours), then the transaction would be denied and would be sent to Investigations.
  • WBE is comprise of 3 seamlessly integrated elements – Design Environment, Run-time Environment and a Asset Repository.

  • Key Take Away: Show combination of Business Activity Monitoring (BAM), Business Event Processing (BEP), and Business Intelligence (BI) in the same closed loop system with the ability to act or intervene based on that information.

    The result is a comprehensive systems of capturing, aggregating and analyzing information. Combining best of both value propositions for BAM, BI and BEP.
    Aggregating across events, processes, applications and historical data for a complete business picture
    Unparalleled ability to act or intervene based on that information: automated response, human decision support, or ongoing process optimization

  • Event Processing Overview

    1. 1. Clifford Foster CTO and Distinguished Engineer March 2010 Event Processing for a Smarter Planet © 2009 IBM Corporation
    2. 2. Every natural and man-made system is becoming instrumented, interconnected and intelligent. Instrumented: We now have the ability to measure, sense and monitor the condition of almost everything. Interconnected: People, systems and objects can communicate and interact with each other in entirely new ways. Intelligent: We can now respond to changes quickly and get better results by predicting and optimising for future events. 2 © 2009 IBM Corporation
    3. 3. Today, more than ever, organisations are under pressure to leverage a wealth of information to make more intelligent choices. Volume of data Velocity of decision-making Data volumes are expected to The market demands that grow tenfold in the next three businesses optimise decisions, years. This is driven by the take action based on good proliferation of end-user devices, information and utilise advanced real-world sensors, lower-cost predictive capabilities - all with technologies and population speed and efficiency. growth. Variety of information Shift in what we analyse With the expansion of Enterprises need a broader, information comes large systems-based approach to the variances in the complexion of information they examine and available data - very noisy with optimise. Stream computing and lots of errors and no opportunity event processing capabilities are to cleanse it in a world of real- enabling the analysis of massive time decision-making. volumes. 3 © 2009 IBM Corporation
    4. 4. Event processing concepts. An Event Simple Event Processing (SEP) Any signal indicating that a change Simple event processing is not a of state (of the business, real- new concept. SEP provides world or other domain) has functions to detect and respond occurred or contemplated as reactively to a single source, or having occurred. homogeneous event type. Business Event Processing Complex Event Processing (BEP) (CEP) Extends CEP and provides a Detect and respond reactively to graphical, non-programmatic user patterns among like or related interface that allows business events, missing events and users to manage event processing aggregate events. CEP supports logic themselves. Supports high high volumes of homogenous volumes of heterogenous business events within a predictable time events and complex patterns that and order. occur in no particular time or order. 4 © 2009 IBM Corporation
    5. 5. Event Processing turns insight into action Action Initiate loyalty program Event Pattern before customer 2nd purchase in a week and leaves the store Event total purchases this year > POS $1000 Purchase Action Trigger automated troubleshooting Event Pattern process Third consecutive period Event without signal No meter signal Action Initiate customer notification / approval process Event and alert fraud Unusual department. withdraw or Event Pattern transfer of Address and PIN changed in last 7 days funds © 2009 IBM Corporation
    6. 6. Detect events & event patterns and alerts the infrastructure when an Business Event Processing follow-on processing actionable situation has occurred – initiating Event Event Event Event Event Turbulent, disparate, non- Event deterministic, unsequenced events Event Event Event Event Text IT Developer Detect Event Sources BEP Events and Patterns External Event Sources/Sinks Internal Event Sources/Sinks ! Generate Actions Business User Sensors Cognos 8 BAM Actions Applications Business Databases Processes © 2009 IBM Corporation
    7. 7. Typical event flow. Business Event Runtime Engine Automated Do any patterns Format actions Receive event Yes? enrichment meet the and and any Then trigger from any currently auto-enrich included associated source specified again if information actions (DB, WSDL, API, etc.) criteria? necessary Event Action - another event Event Cloud 7 © 2009 IBM Corporation
    8. 8. Design and runtime environments should integrate via a shared repository. Design Environment Object Repository Runtime Environment A graphical design environment Provides a means of maintaining When defined event interactions/ provides for defining BEP. IT the defines assets, as well as patterns are detected, the defines the building blocks: supporting incremental life-cycle engine coordinates follow- on information describing events, development and deployment. processing by creating and actions, certain conditions Definitions of events, actions and communicating actions. The (filters), and user console forms data, connectivity, interactions, actions are events themselves that will be made available for and conditions (filters) are all and can trigger services, processing. Furthermore, decoupled at design time - this processes, applications and business users are able to define supports reuse and incremental alerts to business users. and manage the processing logic deployment. and dashboard graphs and charts themselves. 8 © 2009 IBM Corporation
    9. 9. How does event processing fit into SOA?  SOA is an approach to modelling your business, SOA Request/Response and hence IT, as a set of reusable activities or Service services. B Service  Services are then orchestrated or composed into A coarser services, processes or application. Service  SOA communication is typically implemented as C request/response pattern.  Event processing adds an asynchronous pattern to SOA components and services. These patterns are BEP/SOA Pattern Service complementary. BEP Runtime Environment B  Services can emit events and consume events.  The event processing itself is performed as an Service Service extended capability of an ESB. A C  Another name for BEP is Event Driven Architecture (EDA). Dash-  SOA and BEP form together SOA 2.0 (Gartner, board 2006) or Event-based SOA. 9 © 2009 IBM Corporation
    10. 10. Synergy with BPM and BAM BPM BPM deals with the definition, modelling, simulation and execution of business processes. What to Do BAM is used to monitor KPIs, discover exceptions Front Office Back Office Partners and provide visibility through a management interface. BEP BAM When to What’s Act Happening Know When to Act, What To Do, and What’s Happening 10 © 2009 IBM Corporation
    11. 11. The first Forrester CEP Wave - summary  Key Highlights –Focus on Business Event Processing confirmed: “IBM WebSphere Business Events [had the] top score for business end- user tools…” –WBE outranked key competitors like Coral8 and Oracle. –Excellent beginning for a new IBM offering as both Progress Apama and Aleri are pure plays that have been in market since 1999. –This Wave was focused on Complex Event Processing whereas IBM goes to market with Business Event Processing (BEP). BEP is a superset of CEP –IBM’s offering integrates into the rest of the Websphere platform, including the ESB. 11 © 2009 IBM Corporation