1 / 34

COMP-12: Building Apama Applications

COMP-12: Building Apama Applications. Picking the Right Tools. John Trigg. Principal Product Manager, Progress Apama. Agenda. Complex Event Processing & Apama Constituents in CEP Development Scenarios and Dashboards The Developer and MonitorScript

dudley
Télécharger la présentation

COMP-12: Building Apama Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COMP-12: Building Apama Applications Picking the Right Tools John Trigg Principal Product Manager, Progress Apama

  2. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • Scenarios and Dashboards • The Developer and MonitorScript • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  3. What makes CEP so Special? • New way of processing • Works in real time • Time is built in • Analyze by sequence / within time frames • Speed • Sophisticated tools: high speed, high volume • Flexibility • Adaptable across industries, data, communication modes COMP-12: Building Apama Applications

  4. A New Way of Processing Traditional (Static) Data Processing “How many invalid credit card authorizations were accepted yesterday?” 1 2 3 4 5 6 7 8 9 Time Event Stream Data Processing “When 3 authorizations for the same credit card occur in any 60 second period, deny the request and require manual approval. COMP-12: Building Apama Applications

  5. Apama’s Leadership Position • Scalable Event Processing Platform • Sub-millisecond latency • 000’s of scenarios • Sophisticated Development Tools • Business & technical users • Rich event processing language • Flexible Event Capture and Replay • Backtesting & digital forensics • Graphically-Rich Dashboards • Real-time event monitoring • Rich Integration Framework • Event sources, messaging, & applications • Access historical insight in real-time in RDBMS and BI COMP-12: Building Apama Applications

  6. Enterprise Management & Monitoring Environment Scenario 1 Scenario 2 Event Correlator(s) Scenario 3 Scenario 4 Event Store Progress Apama Architecture Dashboards Research Studio Developer Studio Block Builder Apama IDE Scenario Modeler Dashboard Studio Actions Events Actions Events Actions Events Integration Adapter Framework Capture for Simulation & Analysis COMP-12: Building Apama Applications

  7. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • Scenarios and Dashboards • The Developer and MonitorScript • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  8. End users of dashboards Wish to alter and set parameters To monitor executions and to receive alerts To intervene manually To monitor automated actions Likely provider of funds for BAM project Business Line BusinessAnalysts Translator of requirements from the business Definition and design of dashboards Definition and testing of business rules Use and define suitable business analytics Understanding of existing processes Key power user Responsible for integration of tools into the existing environment Will work with business analysts on supportingthe business applications Implementation of analytics Responsible for operational issues TechnicalArchitects andDevelopers Who Gets Involved in Apama Projects?Bringing IT, Business Analysts and Business Users Together COMP-12: Building Apama Applications

  9. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • Scenarios and Dashboards • The Developer and MonitorScript • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  10. Scenarios – Key Concepts • A Scenario is a high level term defining a business level application, process, query or model • E.g. Receiving Process • E.g. Fraud Detection Process • Built by business analysts • Construction of blocks, rules, states, variables • Converted to MonitorScript for execution COMP-12: Building Apama Applications

  11. Scenarios – How to Build • Demo • Blocks • Wiring • States • Rules (incl Global) • Variables • Test COMP-12: Building Apama Applications

  12. Apama Dashboards – Visualizing Event Processing • Real-time variables and analytics can be visualized using graphs, charts, tables etc. • Enables event-driven Apama logic to be visualized in real-time • Variety of deployment options (web, app, …) COMP-12: Building Apama Applications

  13. Client Client Install Webstart/Applet Managed thru launch No pre-install Browser Zero install Portal Integration JSR-168 compliance Dashboards developed ONCE Can be deployed any number of ways Dashboards – Options for Deployment COMP-12: Building Apama Applications

  14. Dashboards - Demonstration COMP-12: Building Apama Applications

  15. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • Scenarios and Dashboards • The Developer and MonitorScript • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  16. What is MonitorScript? • Apama’s Event Processing Language • Event Driven • Script Language • Optimized for • Streams of structured event messages • Seeking patterns of events based on • TIME • CONTENT COMP-12: Building Apama Applications

  17. MonitorScript Key ConceptsApama Event Processing Language event MachineState {string state; string host;} Event Definition: specify event members and their type. Other types include integer, float, boolean, sequence, dictionary, and event. MachineState (“fail”,”192.164.2.174”) Events Instance: specify member values MachineState (state=“fail”,host=“192.164.2.174”) Event Template: specify pattern for one event COMP-12: Building Apama Applications

  18. MonitorScript Key ConceptsApama Event Processing Language MachineState (state=“fail”, host=“192.164.2.174”) -> SlaViolation(qos=3) within(60.0) Event Expression: specify sequence of one or more event templates on all MachineState (state=“fail”, host=“192.164.2.174”):c1 -> SlaViolation(qos=3):c2 within(60.0) {emit SlaAlert (c1.host, c2.qos); route RebalanceLoad (c1.host);} Listener, Tags, and Action: commands to execute when an event expression is matched. Typical commands are: - emit an event (such as an alert) to an external system - route an event to another listener COMP-12: Building Apama Applications

  19. Plug-in Wrapper Dynamic Library C/C++ Routine Other Concepts for a Developer – Plug-Ins • Plug-ins • Plug-ins are used to integrate C or C++ functions directly into the Correlator • Plug-ins are dynamically loaded • The functions exposed by the plug-in are directly accessible through MonitorScript COMP-12: Building Apama Applications

  20. Apama Events Mapping Mapping Normalization Normalization Transport Integration Transport Integration API Other Concepts for a Developer - Adapters Event Correlator • Used to connect middleware, data feeds, database and so on to the Apama Platform • Convert inbound data sources to Apama Events and vice versa • Built around standardized framework – the IAF • Pre-built Transport handlers and Codecs • Custom Transport handlers and Codecs • Flexible Semantic Mapping capabilities Database Event Feed Native Messages COMP-12: Building Apama Applications

  21. Demo of MonitorScript/Dev Studio COMP-12: Building Apama Applications

  22. Agenda Subtitle Goes Here - Arial Italic 24 pt. • Complex Event Processing & Apama • Constituents in CEP Development • The Developer and MonitorScript • Scenarios and Dashboards • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  23. What is a SmartBlock? • A Block is an encapsulation of a specific function that can be reused within scenarios • Adheres to a specific design pattern with standardized access • Implementation details hidden • Typically encapsulation of external access or an analytic • Embedded within an Scenario • Written in XML & MonitorScript COMP-12: Building Apama Applications

  24. Example Blocks • Data Feed Access • RFID reader • JMS Feed • Analytic • Statistical Calculation • Re-usable Scenario • Built by another and converted into a block • E.g. Common monitoring rules COMP-12: Building Apama Applications

  25. How to Build a Block • Block Builder Tool • Describe the parameters • Describe inputs and outputs • Describe functions • Code functions in MonitorScript 2. Build a Scenario; Save it as a block COMP-12: Building Apama Applications

  26. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • The Developer and MonitorScript • Scenarios and Dashboards • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  27. The Business User • Interacts with pre-built scenarios thru • Apama Dashboards • Alerts, messaging • Legacy interfaces triggered by Apama updates • Scope limited to scenario design • Can create/remove particular monitors • Scenario instances • Can adjust parameters of in-process monitors • Scenario instance variables COMP-12: Building Apama Applications

  28. Research Studio • What is It? • Replay tool based on captured event data • Raw • Generated • Why Use? • Simulation • Select time slices from captured data • Evaluate new scenarios against similar real world data • Debug • Replay to specific points in time • Determine what event sequences caused particular updates/events COMP-12: Building Apama Applications

  29. Agenda • Complex Event Processing & Apama • Constituents in CEP Development • The Developer and MonitorScript • Scenarios and Dashboards • Building Blocks – Developers and Analysts Collaborate • The Business User • Summary COMP-12: Building Apama Applications

  30. In Summary • Multiple constituents in any application development – CEP is no different • One environment that offers tools for different user perspectives fosters collaboration and accelerated development • The same environment allows different users to directly apply their knowledge to a project COMP-12: Building Apama Applications

  31. Questions? COMP-12: Building Apama Applications

  32. For More Information, go to… • www.progress.com/apama • www.progress.com/apama/news/webinars for archived webinars on CEP and BAM • CEP Blog : apama.typepad.com • Contact • John Trigg, Principal Product Manager, Apama • jtrigg@progress.com COMP-12: Building Apama Applications

  33. Thank you foryour time COMP-12: Building Apama Applications

  34. COMP-12: Building Apama Applications

More Related