com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.
How WSO2 IoT Server Functions
In this section, we will look at two real world scenarios to understand how IoT Server functions.
Sensor data processing
To understand the concept clearly consider the scenario where your fire alarm is connected to WSO2 IoT Server.
- The fire alarm sensor detects the outbreak of a fire and notifies the Device API.
- The Device API calls for the respective operation needed to be carried out from the fire alarm device type plugin.
Example: Notify the fire brigade of the fire. - The device plugin sends the details of the fire outbreaks to WSO2 Data Analytics Server (DAS) where the data will be analyzed to derive useful information.
Example: Analyze the frequency of the fire outbreaks and based on it identify the reason and pattern of the outbreaks. - Next DAS sends the analyzed information to the database and the system. The information will be made available to the end user who will access it via their mobile devices using the respective app.
Device access via the apps
With technology connecting individuals to devices, you are now capable of getting your devices to perform various operations for you. Consider the scenario where your gate is connected to the IoT Server.
- A request is sent to open the gate at your arrival through the respective mobile application.
- The application sends the request to the configured device plugin using the Device API.
- Next, the plugin communicates with the gate via a transport protocol, which can be MQTT/CoAP/XMPP/DDS/Sigfox, in order to trigger the specific event of opening the gate.
Sequence Diagrams on the communication flow
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.