Route
Definition
Routes identify how a Message is processed when received by a Deployment Instance and consist of Pipeline Modules. Routes can also send Messages back to the Device, to other systems, and/or write data to a Data Stream. Within Routes, it is sometime necessary to provide Mapping of the data between Pipeline Modules. Mapping identifies how the output produced from one module is passed on as input to other modules.
Example
The Plymouth IoT Conveyor Belt sent a Message to its Deployment Instance that the bearings reached a temperature of 425°. Following is an example of a Route that is identified by the Planner:
The PEM was sent to the appropriate Route which used the Sentinel Module to ensure the Message came from PICBelt001. When this was confirmed, the PEM was Queued to a Parser Module.
The Parser Module extracted the temperature of 425° and sent it to the
temperatureWorkflow.The
temperatureWorkflow determined that the belt was overheating and a Message should be sent to the belt to make it stop.The Route also sent a Notification to the owner of Plymouth Manufacturing warning of the issue.
Finally, the Route recorded all of this information in a Data Stream.