This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Configuring Eventing

There are two key concepts of eventing in ESB: Event Source and Event Broker.

  • Configuring an Event Source in WSO2 ESB
  • Configuring an Event Broker in WSO2 ESB

Note

These components can be configured using XML. You can see some examples of the XML eventing configuration here. To configure eventing using XML, click on "Source View" in the "Manage" menu.

Configuring an Event Source in UI

Event source implementation within the WSO2 ESB 2.0 provides a service, where subscribers can send WS-Eventing complaint subscriptions and subscription related operation requests to the WSO2 ESB.

Follow the instructions below to configure an event source in WSO2 ESB.

1. Sign in. Enter your user name and password to log on to the ESB Management Console.

2. From the left navigation menu, select "Event Sources."

3. The "Event Sources" page appears. Click on the "Add Event Source" link to load the "New Event Source" configuration page.

4. Select the subscription manager type from the drop-down menu in "New Event Source."

Available options are:

RemoteRegistry

If you selected "Topic Based Remote Registry subscription manager", the data entry screen will look like the following:

Topic based remote registry subscription manager uses the following properties:

  • Name -The unique name of the subscription manager.
  • Topic Header Name -The value inside a topic header name is subscriptions and events used by the topic based event filter to identify valid subscriptions and dispatch the events.
  • Topic Header Namespace
  • Registry URL - The URL to the remote registry.
  • User Name
  • Password

DefaultInMemory or EmbeddedRegistry

If you selected "Topic Based In-Memory subscription manager", the data entry screen will look like the following:

In-Memory subscription manager requires the following properties:

  • Name - The unique name of the subscription manager.
  • Topic Header Name - The value inside a topic header name is subscriptions and events used by the topic based event filter to identify valid subscriptions and dispatch the events.
  • Topic Header Namespace

5. Click on the "Add" button to save an event source.

Configuring an Event Broker in UI

The WSO2 ESB acts as an event broker dispatching events coming into the ESB. To dispatch an event, the event should fulfill requirements of the particular event source and match subscriptions using active event filter.

Follow the instructions below to configure an event broker in WSO2 ESB.

1. Sign in. Enter your user name and password to log on to the ESB Management Console.

2. Create a sequence and add a child to it by selecting "Core" from the menu and "Event" from the context menu.

3. Select an event source for "eventPublisher" from the drop-down menu. Learn more information about the Event Mediator here.

5. Add a sequence. Click on the "Save" button.

6. Assign sequence to the Proxy Service in the message flow. See Adding a Proxy Service.