1106 soc eda-nice-dicep

427 views

Published on

Complex Event Processing Distributed Complex Event Processing Engine

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
427
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

1106 soc eda-nice-dicep

  1. 1. DistributedComplex Event ProcessingFernand Paraiso, Lionel Seinturier, Romain Rouvoy INRIA Lille – Nord Europe Project-team ADAM
  2. 2. Use case: The MuseumArchitecture Configuration: 4 zones  3 guardians  3 visitors Alert: Whenever a visitor enters a zone not covered by a guardianObjective Propagating events across several CEP engines  Running on separated JVMs  Connected through SCA bindings (JMS, REST…) DiCEPE: Distributed Complex Event Processing Engine
  3. 3. Museum: Architecture Overview Binding REST Guardian composite Alert-system composite Visitor composite Binding JMSDiCEPE: Distributed Complex Event Processing Engine
  4. 4. Museum: Architecture Details frascati binding.rest or binding.jms guardian stmt engineWire guardian-stmt guarded gui enginerun logview stat-guardian Guardian composite Esper-engine alert-stmt alert stmt engineWire visitor-stmt visitor logview stat-visitor gui enginerun visited stmt group-stmt Visitor composite DiCEPE: Distributed Complex Event Processing Engine
  5. 5. Museum: Visitor Composite "{ GuardedLocation: { zone:1,count:1}}" <guardedLocation> <count>1</count> <zone>1</zone> </guardedLocation> stmt engineWire visitor-stmt Client logview stat-visitor frascati run visitor engine binding.rest stmt or group-stmt binding.jms Visitor compositeDiCEPE: Distributed Complex Event Processing Engine
  6. 6. DiCEPE: Supported BindingsREST (HTTP) Events pushed into CEP via HTTP POST Support for multiple representations: XML, JSON… WADL interface description available Based on existing SCA binding: <binding.rest uri=“…“/> Implemented with CXF communication stackJMS Events pushed into JMS channels CEP engine subscribe to and publish into the channels Based on existing SCA binding: <binding.jms jndiURL=“…“/> Implemented with JORAM middleware DiCEPE: Distributed Complex Event Processing Engine
  7. 7. DiCEPE: Dynamic ReconfigurationSupport for reconfiguring CEP engines Dynamic reconfiguration at runtime Manageable from FraSCAti ExplorerCRUD reconfigurations currently supported EPL statements Statement listeners Remote bindings DiCEPE: Distributed Complex Event Processing Engine
  8. 8. DiCEPE open support for CEP EnginesA simple «push» interface public interface Notification<T> { void notify(T event); }Associated to an SCA constraining type <constrainingType name=“cep-engine”> <service name=“notification”> <interface.java interface=“soceda.cep.Notification”/> </service> <!-- … --> </constrainingtype>One component implementation by CEP library Esper (EPL) available Etalis (Prolog) under tests DiCEPE: Distributed Complex Event Processing Engine
  9. 9. Demonstration Questions?DiCEPE: Distributed Complex Event Processing Engine
  10. 10. PerspectivesIncluding support for the WS-Notification standard REST and JMS protocols are already supported Using <sca:binding.ws uri=“…”/>Including more semantics into events POJO and XML documents are already supported Reflecting events as RDF triples

×