This section explains how to embed WSO2 Siddhi 3.0 in a Java project. Embedding Siddhi in a Java project allows you to use the Siddhi query language to carry out real time processing on complex events without running a WSO2 CEP/DAS server. This is useful when you need to carry out complex event processing in embedded devices in which WSO2 CEP/DAS cannot be deployed.
Follow the procedure below to use Siddhi 3.0 as a library.
Step 1: Creating a Java project
Create a Java project using Maven and include the following dependencies in its
Add the following repository configuration to the same file.
You can create the Java project using any method you prefer. The required dependencies can be downloaded from here.
- Create a new Java class in the Maven project.
Define a stream definition as follows. The stream definition defines the format of the incoming events.
Define a Siddhi query as follows.
This Siddhi query stores incoming events for 500 milliseconds, groups them by symbol and calculates the sum for price and volume. Then it inserts the results into a stream named
Step 2: Creating an execution plan runtime
An execution plan is a self contained, valid set of stream definitions and queries. This step involves creating a runtime representation of an execution plan by combining the stream definition and the Siddhi query you created in Step 1.
In the above example,
definition + query forms the execution plan. The Siddhi Manager parses the execution plan and provides you with an execution plan runtime. This execution plan runtime is used to add callbacks and input handlers to the execution plan.
Step 3: Registering a callback
You can register a callback to the execution plan runtime in order to receive the results once the events are processed. There are two types of callbacks.
- Query callback: This subscribes to a query.
- Stream callback: This subscribes to an event stream.
In this example, a query callback is added because the Maven project has only one query.
Here, a new query callback is added to a query named
query1. Once the results are generated, they are sent to the receive method of this callback. An event printer is added inside this callback to print the incoming events for demonstration purposes.
Step 4: Sending events
In order to send events from the event stream to the query, you need to obtain an input handler as follows.
Use the following code to start the execution plan runtime and send events.
When the events are sent, they are printed by the event printer.
For code examples, see quick start samples for Siddhi in Github.