Database Reference
In-Depth Information
This block diagram is strictly functional, and its only purpose is to summarize the actions
that RE and EDN agents have to perform in order to initiate the predefined orchestrated
process (upper part) or deliver the event notification to the ultimate receiver(s) (lower
part). For further reference, please be aware that the receiver could be anything, for in-
stance, Nagios, as mentioned earlier, or Oracle BAM, as we will demonstrate later. Actu-
ally, we are missing one crucial design rule here and will return to it: formalizing the EDN
requirements.
You will have certainly noticed some references to the DB operations in the figures and
drawings. This is normal for Oracle with its immense DB legacy, and consequently, with
its own realization of the CEP query language in addition to the already mentioned SRL
and EPL: the CQL. This is a continuous version of the traditional SQL with constructs for
supporting the streaming of data, and it is an essential part of Oracle's. Event Processing
Thus, take a look at the figure in the
Realization of business cases using event processing
(Rule Engine
) section that describes the 3D nature of complex events as a parallel flow of
events (or basic event-indicating tuples, from left to right), combined with the required
processing sequence (see the lower part of the previous figure; it is just one of the possible
processing routines around TP recognition).
Search WWH ::
Custom Search