This documentation is for WSO2 Enterprise Service Bus version 4.7.0 . View documentation for the latest release.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

The Event Mediator (New in version 4.0) redirects the incoming events to the Event topics.

The Qpid Server can be used as as an event broker with the Event Mediator. 


Table of Contents
maxLevel3
minLevel3
styleborder:1
locationtop
typeflat
separatorpipe


Syntax

Code Block
XML
XML
<event xmlns="http://ws.apache.org/ns/synapse" topic="" [expression=""] />

UI Configuration

The configuration options for Event Mediator are:

  • Topic Type
    • Static
    • Dynamic
  • Topic - Topic to which the events are dispatched. This can be a static topic, or can be specified using an XPath as a dynamic topic.
  • Expression - Xpath to extract the message to be submitted.
Info
titleNote

You can configure the Mediator using XML. Click on "switch to source view" in the "Mediator" window.


Example

Code Block
XML
XML
<!-- Simple Eventing configuration -->
 <definitions xmlns="http://ws.apache.org/ns/synapse">

     <sequence name="PublicEventSource" >
            <log level="full"/>
            <event topic="SampleEventSource"/>
     </sequence>

     <proxy name="EventingProxy">
         <target inSequence="PublicEventSource" />
     </proxy>
 </definitions>

In this scenario, the user has defined a Top source called SampleEventSource. When an event notification comes to the EventingProxy Proxy Service, the messages will be logged and sent to the event source.

Also refer to Topics and Eventing.

Excerpt
hiddentrue

Description of the Event Mediator in WSO2 ESB.