The organization of SCI-Flex can be broken down into a several parts, based on the way it is being implemented. As discussed before, they are:

The JMS Map Message support is not implicit in this diagram as it being embedded into the unified event representation logic.

External events are sources of messages that flow in to Synapse and destinations of messages to which Synapse forwards messages to. These are necessarily a part of an external cloud that is decoupled from the ESB implementation boundaries. The unification process maps between various external events and the internal unified representation of events which we implement as a substitution to the existing logic of diverse independent event representations which is now considered outdated and unmanageable. Unified Events are the one that roam within the periphery of Synapse.

For mediation to take place the Synapse-Esper mediator will either use a static configuration or a dynamic representation of Event Processing Language (EPL), and Endpoint References (EPR). The static versions are embedded in the Synapse configuration information, whereas the dynamic versions are fetched from a compatible backend Registry implementation.

The Synapse-Esper Mediator Administration User Interface is the administrators’ entry point to the dynamic system in action. This gives an administrator to monitor, manage, control, and configure various aspects related to SCI-Flex’s interaction with Synapse and Esper.

The Synapse-Esper mediators execute queries on events that flow in at the mediation stage which are processed by the Esper CEP system. The associated listeners capture events generated by Esper which are the result of patterns being identified based on the input event stream composition and query definition. These events are forwarded to Synapse who decides on further processing and routing operations.