Your SlideShare is downloading. ×
Indusrty Experience with the IBM Active Middleware Technology (AMiT)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Indusrty Experience with the IBM Active Middleware Technology (AMiT)

897
views

Published on

Presented at DEBS2010.

Presented at DEBS2010.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
897
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Industry Experience with the IBM Active Middleware Technology (AMiT) Complex Event Processing Engine Ella Rabinovich (ellak@il.ibm.com) Joint work with Yonit Magid, Guy Sharon, Sarit Arcushin, Idan Ben-Harrush
  • 2.
    • Introduction
    • IBM Active Middleware Technology (AMiT) Overview
    • Industry Experience – 3 use cases
      • Location Awareness
      • Continuous Control Monitoring (CCM)
      • Observation
    • Lessons learned
    Agenda
  • 3. IBM Active Middleware Technology (AMiT) - History 1999 2005 2008
    • Establishment of the group
    • Integrated with:
    • WebSphere Message Broker v6.1
    • WebSphere Premises Server v6.1
    • Entity Analytic Solutions v4.2.1
    • DB2 Health Analyzer
    • Continuous Control Monitor
    • Integrated with:
    • WBI-Message Broker v5
    • WebSphere Server Express
    • AMiT v3
    • Customer engagements, POC, prototypes, solutions, services and show cases
    2006 2004
    • AMiT v2.1
    • Integrated with MQSI v2.1
    • Services Insurance Asset
    • Claim processing
    • Underwriting
    2001
    • AMiT v1
    • IBM Global Technology Services offering
    2003
    • Part of the IBM Autonomic Computing Toolkit alphaWorks
  • 4. From Single Events to Patterns Events Event Processing Rules Situation Detection Definitions Detected Situations event sources Run Time Build Time Authoring Tool Actions Runtime Engine
  • 5. AMiT Model – the Situation Concept Situation Conditions Lifespan initiator terminator Event Selection Actions Operation Keys Input events Operator Joining Counting Temporal Absence Aggregation Notifications Messages Definition updates User plug-ins e1 e2 e3 e5 e8
  • 6. IBM Active Middleware Technology (AMiT) – Engine Architecture and Building Blocks
  • 7. Flexible Design
    • Core can be adapted for
    • a new environment
    Implementation of each component can be changed without affecting the whole engine
  • 8.
    • Experience through use cases from different domains
      • Location Awareness Applications
      • Continuous Control Monitoring (CCM)
      • Observation with CEP
    Industry Experience Through Use Cases
  • 9. Location Awareness Applications
    • For each factory zone, a policy is defined regarding visitor presence:
      • Visitor is not allowed to enter this zone at all
      • Visitor in a zone should always be escorted
      • Visitor in a zone is allowed to stay unaccompanied
    • The event processing engine gets updates of a visitor’s location and detects unauthorized or dangerous situations, such as:
      • A visitor enters unauthorized zone alone
      • Visitor is apart from his escort in an unauthorized zone
    Zone 1 Zone 2 Zone 3 Zone 4 Zone 5
  • 10. Location Awareness Applications – cont. Event Bus RTLS Provider (low-level event source) Filtering Smoothing Persistence Zones Determination Container Checking Backend AMiT Input Adapter Output Listener Backend Interface
  • 11. Continuous Control Monitoring (CCM)
    • Continuous Control Monitoring (CCM) is about giving
    • auditors an automated way to continuously monitor high
    • risk transaction exceptions based on predefined criteria.
    Risk Pattern to Monitor Split transactions are processed in order to by-pass the required level of approvals Executable CEP Rule Alert when multiple transactions with write-off adjustments in aggregate are greater than 25K within a 90 days rolling window CCM Application Alert on exception
  • 12. Continuous Control Monitoring (CCM) – Solution
  • 13. Observation with CEP
    • A client of the bank has the option to purchase the service of being notified on bank related activities regarding their bank account
      • Cashing of bank checks of amount exceeding a specified threshold
      • Account balance exceeds or sinks below a specified threshold (notification once every crossing of the threshold)
      • Completion of an approval process of various types of transactions
    • A client may choose from several notification options and set some individual parameters for each type of notification through web interface
    • A client may preference the method by which to notify
      • Email or text message to a mobile phone
  • 14. Observation with CEP - Solution
    • The AMiT engine integrated with the ESB (used by the bank) as another processing node
    • Situations are detected asynchronously - not necessarily as a response to an incoming event
    • The broker node performs an observation task – the flow and content of the messages are not affected
  • 15. Observation with CEP - Solution WebSphere Message Broker Batch sources Retrieve customer registration data from DB Alert Publish DB2 Event Publisher Data source 2 Dash board Dash board Alert Detection Activate rule logic using MB plug-ins if transaction.type="cash_check“ and transaction.amount>=transaction.parameter_check_threshold AMiT Type “cash_check” Customer 111 Amount 500 customer 111 threshold 400 send by SMS
  • 16. Lessons Learned
    • Application build time
      • Raising the abstraction level – increases usability
      • Expressiveness – ability to detect complex patterns
      • Flexibility and change management (templates and hot-updates)
    • Application run time
      • Scalable (both in number of rules and in volume of events)
      • Supports transactions (is able to run as part of a global transaction)
      • Satisfies the various performance requirements (throughput, latency) encountered for different use cases
  • 17. Lessons Learned – cont.
    • Event processing logic often “leaks” out of the centralized CEP engine to other parts of the solution
    • Event Processing Network (EPN)
    • Raises the abstraction level for the whole event processing logic, not just the part handled by the engine
    Moxey C. et al: A Conceptual model for Event Processing Systems, an IBM Redguide TM publication.
  • 18.
      • Questions

×