FAQs¶
Q: How to debug the input and output data of each node?¶
A: Each node has input and output messages that transfers data between nodes. Toggle on the Debug switch for flows in order to view the running logs of the individual nodes, which include the input and output message of the node. Note that node logs are stored for a maximum of 7 days.
Q: What are the supported syntax and library functions for the Script node? Does Script support the writing of multiple functions, and how can we use real data to debug the script?¶
A: The Script node supports JavaScript and its library function is the transform function which has two parameters, msg and metadata. Yes, the Script node supports the writing of multiple functions. Click the Test button where you can enter stimulated device data to test and debug the script.
Q: What is the maximum number of concurrent connections to the system?¶
A: Using a simple workflow as a reference, consisting of standard nodes such as HTTP Server, MQTT Sub, Lookup Asset, Update Device Status, OTA, Command, etc., processing continuously for 15-20 minutes under stable pressure where the resource usage does not exceed 80% with a resource configuration of 1 CU, the number of concurrent connections is 1000.
Q: How to reuse the created flow?¶
A: You can export the created flow and import to an environment/OU to reuse it. For more information, see Exporting and Importing Flows.
For the code designed for a specified features, you can package it into a custom node and import to an environment/OU to reuse it. For more information, see Creating and Uploading Customized Nodes.
Q: Is there any network specification limitation when uploading and downloading files via integration flows?¶
A: There is no network specification limit in Device Data Integration Service, only file size limit varying from node to node. For more information, see Nodes. The max storage space for downloaded files is 12GB and the max storage period is 30 days.
Q: How is the performance like for this service?¶
A: Please contact the EnOS project manager for the test report as a reference for the performance.