-162-
v7.3
Cloud Connectors
Meshlium
X
treme
12.3.23.3. Running the connector
After the entire configuration is complete, the user can start the connector using the “Start” button of the GUI. The
Connector will be started and run seamlessly in background.
Figure: Simfony start button
The Status box will show the Connector’s state whenever the page is viewed by the user.
To stop the Connector, the user can press the “Kill” button that will stop the connector from running.
Warning: The “Kill” operation will terminate the Connector process and all it procedures abruptly independently
of the stage they are in, i.e. extracting, transmitting, etc.
Figure: Simfony stop/kill button
To stop gracefully the connector the “Stop” button can be used. This will not interrupt any ongoing operations but
rather wait for the connector to finish any ongoing activities. The Connector will look for this graceful stop signal
each time it is starting or finishing the sleep cycle.
12.3.23.4. Integration with Simfony’s IoT platform
The Simfony Cloud Connector is intended to work with any type of connectivity provided by the Meshlium device
it is deployed on. The Connector has two standard protocols available for communicating with the Simfony Cloud:
MQTT and HTTP. Both of them are available in the encrypted version also, i.e. MQTT+SSL and HTTPS. The customer
it is able to choose the most appropriate protocol for his application.
Each Cloud Connector/Meshlium device must be individually authenticated and authorized before it can send data
to the Simfony Cloud Service. The IoT platform will perform protocol specific authentication and authorization
procedures and will allow the connectors to send data only if these are successful. The Connector configuration
data must contain these credentials before the Connector can run properly.
Before data can be sent from the Connector to the Cloud Platform, a Cloud IoT Application must be deployed in
order to listen for data. Customers can easily create, test and deploy their own applications via the Application
Designer GUI. Each application can have a specific entry point for the data coming from the sensor and connectors.
This entry point is defined by the used Protocol (MQTT or HTTP) and a custom target (MQTT-topic; HTTP-path). This
entry point must be also configured in the Connector via the “Connection Type” and “Connection Path” parameters.
Once the application is deployed, the connectors can start sending data into it and the custom business logic will
be triggered.
Find out more about running the connector in the “
Simfony Meshlium Connector- User Guide
”.