Versions Compared

Old Version 13

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

WSO2 CEP/DAS has the capability of receiving events from event receivers via various transport protocols. Following are the event receivers that come with WSO2 CEP/DAS by default. You can write extensions to support other transport.

Child pages (Children Display)

Info

In addition to the above, the SQS extension allows you to receive events via SQS.

For instructions to download and install an extension, see Downloading and Installing Extensions from the Store.


Event receiver configuration

...

The above sections of an event receiver configuration are described below.

Section
Description
FromAn input event adapter (transport) configuration via which the event receiver receives events.
Adapter propertiesSpecific properties of the selected input event adapter. For information on configuring adapter properties of various transport types, see Event Receiver Types.
ToThe event stream from which the event receiver will fetch the events for processing.
Mapping configurationThe format of the message that is received. You can configure custom mappings on the selected format via advanced settings. For information on configuring custom mappings, see Input Mapping Types.

Creating event receivers

You can create event receivers either using the management console or using a configuration file as explained below.

...

  1. Create an XML file with the following event receiver configurations. An event receiver implementation must start with  <eventReceiver> as the root element.

    Note

    In the following configuration, specify the respective adapter properties based on the transport type of the receiver within the <from> element. For the respective adapter properties of the event receiver configuration based on the transport type, see Event Receiver Types .

    Code Block
    languagexml
    <eventReceiver name="EVENT-RECEIVER-NAME" statistics="disable" trace="disable" xmlns="http://wso2.org/carbon/eventreceiver">
    <from eventAdapterType="EVENT-ADAPTER-TYPE">
       .................................
    </from>
    <mapping customMapping="disable" type="xml"/>
    <to streamName="Test Stream" version="1.0.0"/>
</eventReceiver>

    The properties of the above configuration are described below.

    Adapter propertyDescription
    name
    		Name of the event receiver
    statistics
    		Whether monitoring event statistics is enabled for the receiver
    trace
    		Whether tracing events is enabled for the receiver
    xmlns
    		XML namespace for event receivers
    eventAdapterType
    		Type of the event adapter.
    customMapping
    		Whether a custom mapping is enabled on the receiver.
    type
    		Type of the enabled custom mapping.
    streamName
    		Name of the event stream to which the receiver is mapped.

  2.   Add the XML file to the <PRODUCT_HOME>/repository/deployment/server/eventreceivers/directory directory. Since hot deployment is supported in the product, you can simply add/remove event receiver configuration files to deploy/undeploy event receivers to/from the server.

...

After a receiver is successfully added, it gets added to the list of receivers displayed under under Event in the  in the  Main   menu of the product's management console. Click Edit  Edit to change its configuration and redeploy it. This opens an XML-based editor allowing you to edit the event receiverr configurations event receiver 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 as described below.

...