Introduction
This sample demonstrates how to filter incoming event attributes and add them to another stream using simple pass-through with WSO2Event adaptor. Because we do not use any execution plan here, there is no Siddhi query.
Prerequisites
See Prerequisites in CEP Samples Setup page.
Building the sample
Start the WSO2 CEP server with the sample configuration numbered 0001. For instructions, see Starting sample CEP configurations. This sample configuration does the following:
- Creates
<CEP_HOME>/repository/conf/stream-manager-config.xml
file, which is used to create the stream definitions for the sample. - Points the default Axis2 repo to
<CEP_HOME>/sample/artifacts/0001
(by default, the Axis2 repo is<CEP_HOME>/repository/deployment/server
).
Executing the sample
Open another terminal, go to
<CEP_HOME>/samples/consumers/wso2-event
and run ant from there.
It builds the sample wso2event consumer and executes it.Do not close this terminal. It is required to keep the server running and receive events.
Open another terminal, go to
<CEP_HOME>/samples/producers/service-stats
and run ant from there.
It builds and runs the wso2event producer, which sends sample service stats to the CEP server.To configure host, port, username, password and No. of events, use -Dhost=xxxx -Dport=xxxx -Dusername=xxxx -Dpassword=xxxx -Devents=xx.
For example : ant -Devents=10
See the output events received from the CEP via the terminal opened in step 2. For example, given below is the console output of the consumer when sending 5 events from the producer.