Sender

Module summary

Sender module is used to read data from receiver and conditionally execute automated actions, usually to route the processed messages to the other systems.

Module lifecycle

Each sender module connected over the Service bus to exactly one Receiver module and follows this process:

1. Periodically checks new data on Receiver
2. Read normalized data from Receiver
3. Evaluate action rules
4. Trigger one or more automated actions
5. Delete processed data from Receiver

Action rules

Automated actions are executed, only if action rules are met or no rules are defined.

Currently, there is just one type of action rule - filter rule. Filter rule defines set of filter conditions, which are evaluated in a row. Filter rule consist of referrenced field name, operation type (e.g. EQ, GT, NOT_NULL, etc) and values.

Automated actions

There are following automated action types available out of the box:

• BellaDati REST - Send data to the BellaDati backend over REST API, single or bulk mode for huge data loads
• BellaDati Data set - Send data directly to BellaDati data sets
• HTTP based - Send data to 3rd party systems using HTTP protocol with wide range of authentication options support
• SMTP - Use SMTP action to execute send email actions
• Filesystem - store data to filesystems
• MQTT publish - Publish MQTT messages to the MQTT broker
• Modbus publish - Publish messages using Modbus protocol
• PLC4X publish - extendable module supporting variety of protocols such as AB-Ethernet, ADS /AMS, BACnet/IP, CANopen, DeltaV, DF1, EtherNet/IP, Firmata, KNXnet/IP, OPC-UA, S7 and transports, e.g. TCP, UDP, Raw Socket, Serial Port, CAN bus, SocketCAN, PCAP replay
• Custom action - Custom action implemented using IoT Controller SDK

Roles

 This module supports following roles:

Module states

This module can have one of following statuses:

API endpoints

This module provides following HTTP endpoints: