This is Day #15 of a short series of brief tips, tricks, hints and reminders of information relating to the Apama Streaming Analytics platform, both from Software AG as well as from the community.

Previously, Day #6 of the Advent Calendar dealt with the fundamentals of Apama EPL (Event Processing Language) and Day #10 touched on Cumulocity IoT as one of several development environments. Today we deal with the Cumulocity IoT environment in more detail.

Regardless of how each Apama component is presented within the Cumulocity IoT UI, the underlying functionality will be written in EPL and run within an instance of the correlator. This is most obvious with the Streaming Analytics component “EPL Apps”, which provides a developer UI for direct code development.

The same is also true of the companion component “Analytics Builder” that was covered in Day #3. The UI for the Analytics Builder is graphical, composed of various functional blocks which can be wired together to compose complex analytics easily without needing any programming knowledge. However, under the hood, each block is written in EPL along with the framework which checks and wires the entire network together. Custom blocks can also be added, and these will be written using EPL. The details of this will be covered tomorrow.

Even more abstracted are the smart rules, available via the Cockpit application. These provide pro-forma rules via simple dialogs to carry out common, basic tasks. Nevertheless, the underlying execution of those rules is again EPL running in an Apama correlator instance.

Today we take a closer look at EPL Apps, the app that exposes you to EPL directly, so check out the original post in the Software Ag Tech Community.

Note that some posts may be published a day or two early or late (e.g. Mon-Fri) so you may find you have bonus days with more than one post!