This documentation is for WSO2 Complex Event Processor 4.0.0. View documentation for the latest release.
WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Events can be processed on Realtime using The Siddhi CEP engine . Sequence processes events in real time. A sequence of events having of the same event type are is defined as a stream, and processing processed by Siddhi using via the SQL-like Siddhi Query Language (SiddhiQL), . Siddhi works as an upside down database by storing all the queries in memory, matching incoming events against the stored queries at runtime, and producing matched events as streams.

In-order to process events, the execution logic should must be written as a script using SiddhiQL, and these scripts must be deployed in the server . This Execution Plan will act as execution plans. An execution plan acts as an isolated execution environment and there will be an , and a separate instance of  Siddhi Execution Runtime execution runtime is created for each Execution Plan. An Execution Plan execution plan. An execution plan can import one or more streams from the server for processing and push zero or more output streams back to the server.  In-In order to import and export streams the script will also contain streams, the script contains import and export annotations bindings that bind the streams on the server with the streams defined in the Execution Planexecution plan