This documentation is for WSO2 Stream Processor 4.3.0. View documentation for the latest release.

All docs This doc
||
Skip to end of metadata
Go to start of metadata

This section provides an overview of the samples shipped with WSO2 SP to help you understand the capabilities of WSO2 SP and well as WSO2 Siddhi. These samples can be accessed and run via the WSO2 Stream Processor Studio.

Sample list

To view the complete list of WSO2 samples, click here.

Running a sample

To access and run a sample from the WSO2 Stream Processor Studio, follow the steps below.

  1. Navigate to the <SP_HOME>/bin directory and issue the following command to start the WSO2  Stream Processor Studio.
    • For Windows: editor.bat
    • For Linux: sh editor.sh
  2. Access the Stream Processor Studio via the  http://localhost:<EDITOR_PORT>/editor  URL. The Stream Processor Studio opens as shown below.

    The default URL is  http://localhost:9390/editor .

    All the available samples can be accessed from the welcome-page. 

  3. Click on the required sample to open its Siddhi application.

    If the sample you want to try out is not visible in the default view, click More Samples. This opens the Import Sample dialog box where the complete list of available samples are displayed. Click on the required sample to expand it, and then click on its Siddhi file as shown below. As a result, the Siddhi application is entered in the Sample Name field. Click Open to open the sample and proceed to execute it.

  4. To save the Siddhi application in your workspace so that you can run it, click File => Save. This opens the Save to Workspace dialog box. Click Save.
  5. To run the Siddhi application, click Run => Run. If the application has successfully started, a message similar to the following example is displayed in the output console.
     
  6. The testing steps differ from one sample to another. Therefore, to test the Siddhi application of the required sample, follow the instructions provided at the top of the relevant Siddhi file as comments. The following is an example.

Once test a sample following the given instructions, you can view the results in the output console.
 

  • No labels