Child pages
  • Input WSO2Event Event Adapter

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

Skip to end of metadata
Go to start of metadata

The input WSO2Event event adapter handles WSO2 events. It receives WSO2 events over Thrift using TCP, SSL/ TCP, HTTP, HTTPS. You can also send events via HTTP and HTTPS in a predefined JSON format, using the REST API data receiver.

Configuring input WSO2Event event adapter

By default, WSO2 products come with a configured WSO2Event event adapter by the name DefaultWSO2EventInputAdaptor to receive fired events.

Have only one input WSO2Event event adapter in the product to receive incoming events. However, to send WSO2 events out, you can use several o utput WSO2Event event adapters.

By default, the input WSO2Event event adapter starts up with the product, and its default ports are as follows:

  • tcp port: 7611 

  • ssl port: 7711 

  • http port: 9763 

  • https port: 9443

You can configure the input WSO2Event event adapter either using the management console or using a configuration file as explained below.

Configure using the management console 

Follow the instructions below to configure input WSO2Event event adapter using the management console. This deploys the event adapter in the <PRODUCT_HOME>/

repository/deployment/server/inputeventadaptors/ directory.

  1. Log in to product's management console, and click Configure.
  2. Click Input Event Adaptors in the Event Processor Configs menu, and then click Add Input Event Adaptor.
  3. Enter LocalWSO2EventReceiver for Event Adaptor Name, and select wso2event for Event Adaptor Type as shown below.
    create input WSO2Event event adapter

  4. Click  Add Event Adaptor.

Configure using a configuration file

Follow the instructions below to configure input WSO2Event event adapter using a configuration file.

  1. Create an XML file with the following input WSO2Event event adapter configurations. Input event adapter implementation must start with  <inputEventAdaptor>  as the root element.

    <inputEventAdaptor name="LocalWSO2EventReceiver" type="wso2event" xmlns=""></inputEventAdaptor>
  2. Add the XML file to the <PRODUCT_HOME>/repository/deployment/server/inputeventadaptors/ directorySince hot deployment is supported in the product, you can simply add/remove input event adapter configuration files to deploy/undeploy input event adapters to/from the server.

After an adapter is successfully added, it gets added to the list of adapters displayed under Event Processor Configs in the Configure menu of the product's management console. Click Edit to change its configuration and redeploy it. This opens an XML-based editor allowing you to edit the event adapter configurations from the UI.  Do your modifications and click Update. You can also delete it, enable/disable statistics or enable/disable tracing on it using the provided options in the UI.

Configuring input WSO2Event event adapter message properties

The configured input event adapters are used in event builders. With input event adapter message properties, event builders are able to extract data from the incoming events to build the event streams. Message properties specific to input event adapters of the wso2event type can be configured as follows. 
  1. Log into the CEP Management Console. For detailed instructions, see Running the Product.
  2. Click the Configure tab and then click Event Builders to open the Available Event Builders page.
  3. Click the name of the event builder to which the relevant input event adapter is connected. This opens the Event Builder Details page.

    The input WSO2Event event adapter message properties The message properties of a wso2event input event adapter are described below.  Change the property values as required.

    Input Event Adaptor NameThe name of the input event adapter.
    Stream NameThe name of the incoming WSO2 event stream.
    Stream VersionThe version of the incoming WSO2 event stream.
    Input Mapping TypeThe incoming event type to be mapped. The Input WSO2Event event adapter supports only WSO2Event mapping type.
  • No labels