MR Introduction

Message Routing service provides the capability of rule-based filtering, transformation, enrichment and routing of sensor data streams in real time. It allows users to define rules with one or more conditions. Rule’s condition is checked on every sensor observation data on real time basis and if the rule condition is satisfied the data is sent to the selected destination or sink. Rules allow different sensor outputs to be cleaned, grouped and filtered for the other applications/services to consume. Routing can be done based on identity of sensors, the real-world object being observed, the property being observed, value of the measurement and location coordinates of the sensor. Further, any business rule can be written using expression evaluation which is in line with the concept of zero coding.

Message router rules can receive messages from the input points mentioned below:

  • Direct type exchange

  • Topic type exchange

  • Queue

Queue and topic exchange support are provided from TCUP 11.

Purpose of the Document

After going through this document a user will able to create different type of rules, do the basic operations on the rule such as start, stop etc. They will be able to publish observation data to the input of the rule and view the output. This document also helps the user to view the statistics of the rule, download and upload any rule from/in TCUP.

This document explains the MR service both from the portal as well as from the swagger.

Reference Document

Please refer to the following documents to get more details on MR service:

  • To understand the basic concepts of MR Service please refer to the Concept guide.

  • For API details please refer to the API guide.