Difference between revisions of "Data Engine Task"
Jump to navigation
Jump to search
Jimhogenson (talk | contribs) (Created page with "File:Task manager config data engine.jpg") |
Jimhogenson (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:Task manager config data engine.jpg]] | [[File:Task manager config data engine.jpg]] | ||
| + | |||
| + | There is really not much to configure for the Data Engine, but if you have exported a collection of data objects from another IoTServer and wish to replicate that collection, here is where you can import a file containing the configuration of those objects. | ||
| + | |||
| + | Activity timeout is a form of watchdog. If the task manager does not see the Data Engine update its activity indicator within this amount of time, the task manager will restart the Data Engine. If set to zero, the watchdog is disabled. The task manager itself is restarted by the Linux cron if it stops responding. | ||
Latest revision as of 17:00, 3 May 2019
There is really not much to configure for the Data Engine, but if you have exported a collection of data objects from another IoTServer and wish to replicate that collection, here is where you can import a file containing the configuration of those objects.
Activity timeout is a form of watchdog. If the task manager does not see the Data Engine update its activity indicator within this amount of time, the task manager will restart the Data Engine. If set to zero, the watchdog is disabled. The task manager itself is restarted by the Linux cron if it stops responding.
