IoT-Ignite Rule Management
The Rule Engine makes it possible to build IoT applications that gather, process, analyze and act on data generated by connected devices at global scale without having to manage any infrastructure. Complex event processing (CEP) can be done in IoT-Ignite platform thanks to IoT-Ignite Rule Management. This is the place where you visually design your CEP rules. These rules can run on IoT-Ignite cloud as well as at the edge gateways. We call them “cloud rules” or “edge rules” respectively.
You visually design your rules by drag and dropping your data source, condition and action components. You configure them by double clicking on a component, and link them to each other to create a rule flow.
There are no restrictions on the number of rules to be defined. It is also possible to enable or disable any rule at any time you want.
The Rule Engine evaluates inbound messages published into IoT-Ignite and transforms and delivers them to another device or a cloud service, based on business rules you define. A rule can be applied to data streams from one or many devices, and it can take one or many actions in parallel.
Edge devices are the key components as a main data source of IoT services. Processing data at the edge is the way of real time analysis and real time response for IoT services. We call this ‘running services at the gateways’. Smartness at the edge also prevents all–time cloud connectivity and enables real time event processing. Rule-definition in the edge device provides flexible and cost effective services.
It is also possible to emit ‘realized’ rules (events) at the gateway to IoT-Ignite. Using these events as conditions in your cloud rules reduces data traffic, and lets you handle them at the cloud level.
IoT-Ignite architecture also provides a “Device Rules Creation” feature that enables the edge device to run by itself when the cloud connection is lost.