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 4 Next »

HTTP event receiver is an internal event receiver that comes with WSO2 products which is used to receive events in XML, JSON or Text formats via HTTP, HTTPS, and local transports. By default it uses the following URLs to retrieve events.

  • For super tenants: 

http://localhost:9763/endpoints/<EVENT_RECEIVER_NAME> or 

  https://localhost:9443/endpoints/<EVENT_RECEIVER_NAME>

  • For other tenants:

http://localhost:9763/endpoints/t/<TENANT_DOMAIN>/<EVENT_RECEIVER_NAMEor 

https://localhost:9443/endpoints/t/<TENANT_DOMAIN>/<EVENT_RECEIVER_NAME>

Creating a HTTP event receiver

For instructions on creating a HTTP event receiver, see Receiving Events.  

Configuring adapter properties

Specify the Adapter Properties, when creating a HTTP event receiver using the management console as shown below.

HTTP input event adapter properties

After entering the transport type in adapter properties, select the Event Stream to which you want to map the incoming events, and the Message Format which you want to apply on the receiving events . Also, click Advanced to define custom input mappings based on the Message Format you selected. For more information on custom input mapping types, see Input Mapping Types.

You can also d efine the respective adapter properties of the event receiver based on the transport type within the  <from>  element of the event receiver configuration in the <PRODUCT_HOME>/repository/deployment/server/eventreceivers/ directory as follows.

<eventReceiver name="HTTPInputEventAdapter" statistics="disable" trace="disable" xmlns="http://wso2.org/carbon/eventreceiver">
    <from eventAdapterType="http">
        <property name="transports">https</property>
    </from>
   ............................
</eventReceiver>

The above adapter properties are described below.

Adapter propertyDescriptionConfiguration file propertyExample

Transport(s)

Transport type via which the events are received.
transports
https
  • No labels