Page Comparison

...

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Streams to open the Available Event Streams page. 
2. Click Add Event Stream to open the Define New Event Stream page. 

3. Enter information as follows to create a new event stream named org.wso2.event.sensor.stream.
   
   Event Stream Details

   Parameter Name	Value
   Event Stream Name	org.wso2.event.sensor.stream
   Event Stream Version	1.0.0

   Stream Attributes

   Click Add to add the attribute after entering the attribute name and attribute type.

   Attribute Category	Attribute	Attribute Type
   Meta Data	timestamp	long

    

   	isPowerSaverEnabled	bool

    

   sensorId

   int

    

   	sensorName	string
   Correlation Data	longitude	double

    

   	latitude	double
   Payload Data	humidity	float

    

   sensorValue

   double

4. Click Add Event Stream to save the information.

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Receivers to open the Available Receivers page.
2. Click Add Event Receiver to open the Create a New Event Receiver page.

3. Enter information as follows to create the new event receiver named httpReceiver.
   

   Parameter Name	Value
   Event Receiver Name	httpReceiver
   Input Event Adapter Type	http
   Transports	all
   Event Stream	org.wso2.event.sensor.stream
   Message Format	json

4. Click Add Event Receiver to save the information.

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Publishers to open the Available Publishers page.
2. Click Add Event Publisher to open the Create a New Event Publisher page.

3. Enter information as follows to create the new event publisher named  loggerPublisher.
   
   

   Parameter Name	Description
   Event Publisher Name	loggerPublisher
   Event Source	org.wso2.event.sensor.stream
   Output Event Adapter Type	logger
   Message Format	text

   
   

4. Click Add Event Publisher to save the information.

...

This builds the HTTP client and sends the events in the <DAS_HOME>/samples/cep/artifacts/0001/httpReceiver.txt file to the httpReceiver endpoint. You can view the details of the events that are sent as shown in the log below. These logs are published by the publisher created in Step 3.

The logs of the JSON events received by the DAS server will be displayed in the CLI as shown in the example below.

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Streams to open the Available Event Streams page. 
2. Click Add Event Stream to open the Define New Event Stream page. 
3. Enter information as follows to create the event stream named org.wso2.event.sensor.filtered.stream.
   

   Event Stream Details

   Paramater Name	Value
   Event Stream Name	org.wso2.event.sensor.filtered.stream
   Event Stream Version	1.0.0

   Stream Attributes
   

   Attribute Category	Attribute	Attribute Type
   Meta Date	timestamp	long

    

   	sensorName	string
   Correlation Data	longitude	double

    

   	latitude	double
   Payload Data	sensorValue	double

4. Click Add Event Stream to save the information.

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Execution Plans to open the Available Execution Plans page. 
2. Click Add Execution Plan to open the Create a New Execution Plan page.

3. Enter information as follows to create the new execution plan
   

   Parameter Name	Value
   Import Stream	org.wso2.event.sensor.stream:1.0.0
   As	sensorStream
   Value Of	filteredStream
   StreamId	org.wso2.event.sensor.filtered.stream:1.0.0

4. Click Import and then click Export. The section for query expressions will be updated as shown below.
   

5. Add the following query expression.

   Anchor
   filter filter

   

   Code Block
   from sensorStream [sensorValue > 100] select meta_timestamp, meta_sensorName, correlation_longitude, correlation_latitude, sensorValue insert into filteredStream

   This query includes the value sensorValue > 100. Therefore, when the execution plan forwards events from org.wso2.event.sensor.stream:1.0.0  to org.wso2.event.sensor.filtered.stream:1.0.0, events in which the value for the sensorValue attribute is less than 100 will be dropped.

6. Click Validate  Query Expressions. Once you get a message to confirm that the queries are valid, click Add Execution Plan.

...

1. Log into the DAS Management Console and click on the Main tab. Under Manage, click Publishers to open the Available Publishers page.
2. Click Add Event Publisher to open the Create a New Event Publisher page.

3. Enter information as follows to create the new event publisher named UIPublisher.
   

   Parameter Name	Description
   Event Publisher Name	uiPublisher
   Event Source	org.wso2.event.sensor.filtered.stream:1.0.0
   Output Event Adapter Type	ui
   Message Format	wso2event

4. Click Add Event Publisher to save the information.

Step 9: Create a dashboard and a gadget

WSO2 Analytics Dashboard will be used as the tool to analyse the output of the event flow you created in this guide. This step creates a dashboard and a gadget which analyses events from the  org.wso2.event.sensor.filtered.stream stream published by the uiPublisher publisher.

1. Log into the DAS Management Console. In the Main tab, click Analytics Dashboard.
2. Log into the Analytics Dashboard with your username and password.
3. Click the menu icon and then click Gadgets to open the Gadgets page as demonstrated below.
   Image Modified
4. Click GENERATE GADGET, and enter values in the Generate a Gadget wizard as follow. 
   Image Modified
   
   1. In the  Select Provider  field, select  Realtime Data Source . Then click  Next .
   2. In the Event Stream field, select org.wso2.event.sensor.filtered.stream:1.0.0 . Then click Next.

   3. Configure a chart as follows.

      Parameter Name	Value
      Gadget Name	Sensor Value VS Timestamp
      Select Chart Type	Line Chart
      X-Axis	TIMESTAMP
      X type	time
      Y-Axis	sensorValue
      Y type	default
      Color domain	sensorName
      Max length	30

   4. Click Add to Store, and then click Go to Portal. the Dashboards page appears again.
5. Click CREATE DASHBOARD to open the Create a Dashboard page. Configure a new dashboard as follows.Image Modified

   1. Enter a name and a description for the new dashboard as follows, and click Next.
      

      Parameter Name	Value
      Name of your Dashboard	Sensor Statistics
      Description	This dashboard indicates the sensor value at different times in a particular location.

   2. Select the Single Column layout. A message appears to indicate that the dashboard is successfully created.
   3. Click the  icon for gadgets. Then select and drag Sensor Value VS Timestamp gadget to the first column as demonstrated above.

Step 10: Send Events to the HTTP Receiver via Curl Command

...

1. Issue the following curl command.

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439468145264 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 96.5 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   The following log will appear in the DAS CLI.
   

   Note that the Sensor the Sensor Statistics dashboard you created does not get updated. This is because the value for the sensorValue attribute is less than 100 in this event. Therefore, it gets dropped by the filter you created in the execution plan, and as a result, it is not forwarded to the org.wso2.event.sensor.filtered. stream:1.0.0 stream.

2. Issue another command with a value greater than 100 for the sensorValue attribute as follows.
   

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp":1439467524120 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 156 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

    The following log will appear in he DAS CLI.
   
   

   The event is forwarded to the  org.wso2.event.sensor.filtered. stream:1.0.0 stream since the value for the sensorValue attribute is greater than 100. Therefore, the Sensor Statistics dashboard will be updated as shown below.
    

3. Issue more curl commands as follows with several timestamps and sensor values. 

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439467524120 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 156 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439467890957 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 170 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439467951518 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 131 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439467992936 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 126 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   Code Block
   curl -X POST -d "{ "event": { "metaData": { "timestamp": 1439468050928 , "isPowerSaverEnabled": false, "sensorId": 701, "sensorName": temperature }, "correlationData": { "longitude": 4.504343, "latitude": 20.44345 }, "payloadData": { "humidity": 2.3, "sensorValue": 145 } } }" http://localhost:9763/endpoints/httpReceiver --header "Content-Type:application/json"

   Since the value for the sensorValue attribute is greater than 100 in all these events, the dashboard will be updated as shown below. These events will also be logged in the DAS CLI.

   Send sensor events with several timestamps and sensorValues, The dashboard will now get effected with the sent event since sensorValue is over 100 and the event gets sent to the dashboard. These events will get logged in the DAS CLI as well.
   
   

...

This step involves adding execution plan and stream configurations using the template you created and added in the previous step.

1. If the DAS server was running when you created and deployed the template, restart the DAS server. 
2. Log into the DAS Management Console. Click the Main tab and then click Template Manager. Create a new scenario as demonstrated below.
   
   1. Click on SensorStatistics to open the Deployed Scenarios page. Then click Create New Scenario to open the Edit Scenario page.

   2. Enter information as shown in the table below and click Add scenario .
      

      Parameter Name	Value
      Scenario Type	AnalyzeSensorStatistics
      Scenario Name	FilterSensorValues
      Description	Filter events with a sensor value greater than 120
      Sensor Value	120

       A message appears to inform you that the scenario is successfully created. Close the message. The scenario you configured is displayed in the Deployed Scenarios page

...

The following is a summary of this guide which describes each element in the event flow.

...