This is the project documentation for BPEL Monitoring with Esper. Information about the components can be found in the respective subsections.

For information about the monitoring client, please take a look at the according website.


Architectural Overview

The BPEL monitoring system

The BPEL monitoring system consists of several components, that interact with each other to transmit, process and publish the BPEL events, generated by Apache ODE.

  • The ode-listener component is registered at the BPEL server and is responsible for receiving the generated BPEL events from ODE. It then forwards the events to a JMS destination, where the events can be picked up by the monitoring-engine.
  • The monitoring-engine receives the events from the JMS destination and transforms them to XML. These XML events are then inserted into the Esper event engine. A subscription manager listens on a JMS destination for subscription requests of clients. When a new subscription is created, the subscription manager creates a new EPL statement according to the client's request and sends notifications in form of JMS messages to a callback topic, when the statement returns a result.
  • Clients can register at the engine by providing a statement to which they want to subscribe and a callback topic where notifications of events are sent.


Ode BPEL Listener

The Ode BPEL Listener receives BPEL Events from Apache Ode and forwards them to a JMS topic.

Monitoring Engine

The Monitoring Engine receives the BPEL Events from a JMS topic, transforms them to XML and inserts them into Esper's event stream. It also handles subscription requests of clients and sends event notification to the specified callback topics.