WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


This sample demonstrates the usage of the UI publisher using a client app. This sample does not have Siddhi queries because it does not not use any execution plans. 


 Set up the prerequisites required for all samples.

Building the sample 

Start the WSO2 CEP server with the sample configuration numbered 0071. For instructions, see Starting sample CEP configurations. This sample configuration does the following.

  • Creates an event stream named

  • Creates an event publisher named uiPublisher.

  • Loads the events stored in the <CEP_HOME>/samples/cep/artifacts/0071/eventsimulatorfiles/events.csv file to the event simulator.

  • Deploys a Jaggery application named outputuitest. This application functions as the client that consumes the events published by the UI publisher.

Executing the sample

Follow the steps below to execute the sample.

  1. Log in to the management console.
  2. Click Tools, and then click Event Simulator.
  3. Access the Web app which you deployed in Prerequisites via your Web browser using the following URL:  http://localhost:9763/outputuitest/
  4. Enter  the following details in the Web app as shown below.

    enter details in the Web app

      • Stream Name:

      • Version: 1.0.0

      • CEP Host: localhost

      • CEP Port: 9763

      • Polling Interval: 30

      • Domain: carbon.super

      • Mode: WEBSOCKET

      • Secure level: UNSECURED

  5. Click Connect.

  6. Click Play on the corresponding event stream as shown below, to send the events in the <CEP_HOME>/samples/cep/artifacts/0071/eventsimulatorfiles/events.csv file to the publisher.

    You view the output events published from the CEP which are received by the Web app as shown below.

    published events received by the Web app


  • No labels