This documentation is for WSO2 CEP 3.1.0. View the home page of the latest release.

Unknown macro: {next_previous_links}
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 7 Current »

Introduction

This sample demonstrates how to process the api request stream statistics. Here we have used soap server as both input and output 

The query used in this sample is as follows:

from apiRequestStream[meta_api=="API-1"]
select *
insert into filteredAPIRequestStream;

Prerequisites

  1. See Prerequisites in CEP Samples Setup page.

Building the sample

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

  • Creates <CEP_HOME>/repository/conf/data-bridge/stream-definitions.xml file, which is used to create the stream definitions for the sample.

Executing the sample

  1. Run the Axis2LogService since it is the consumer of the events which emitted by CEP. Go to the <CEP_HOME>/samples/consumers/axis2-log-service and run ant -DsampleNo=0111. Then it will deploy the logging service.

  2. Open the CEP terminal to view the event logged by LogService which was deployed on step 1.

  3. Go to the management console and select the Try this service option . (Main --> Services )

  4. Then you will redirected to a UI shown below, then change the endpoint and body as shown below and click on send.

     

    Endpoint - http://10.100.0.44:9763/services/soapInputEventAdaptor/apiRequestStream
    Body - 

    <body>
    <events>
        <event>
            <metaData>
                <api>API-1</api>
                <api_version>version</api_version>
            </metaData>
            <payloadData>
                <requestTime>56783</requestTime>
                <apiPublisher>publisher1</apiPublisher>
                <hostName>localhost</hostName>
            </payloadData>
        </event>
    </events>
    </body>
  5. From the terminal opened in step 2, you can see the processed events which emitted by CEP.

    For example, given below is part of the console output of the consumer when sending events through Try-it service. 

  • No labels