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.


  • Points the default Axis2 repo to <CEP_HOME>/sample/artifacts/0107 (by default, the Axis2 repo is <CEP_HOME>/repository/deployment/server).

Executing the sample

  1. Log into in to the CEP management console which is located at using the following URL and admin/admin credentials:  https://localhost:9443/carbon.


  2. Go to Tools -> Click Tools, and then click Event Simulator. Under the 'Multiple Events' section, you can see 4 files listed there You view four files listed under the Send multiple Events section, which contains some sample data as follows.
     files containing sample dataImage Modified
  3. Simulate the above streams in the following order
    • userEvents.csv
    • blackListUserEvents.csv
    • purchaseEvents.csv
    • deleteUserEvents.csv (in order to clean up the table)
  4. The Click the corresponding Play button of the userEvents.csv file which contains sample data that is used to fill the in-memory CardUserTable. Click play start This starts sending events to fill the table.

  5. The Click the corresponding Play button of the blackListUserEvents.csv file which contains sample data that is used to mark user entries in the CardUserTable as blacklisted. Click play to start This starts sending blacklisted events and mark marks some table entries as blacklisted.
  6. The Click the corresponding Play button of the purchaseEvents.csv file which contains credit card transactions data. Play it and send This sends the transaction data. 
  7. After sending sample events from purchaseEvents.csv, you will be able to see the outputs as follows.

    Image RemovedClick the corresponding Play button of the deleteUserEvents.csv file to clean up the tables.
    You view the output logs in the CLI in which you run the product s as shown below.

    output logs in the CLIImage Added