Difference between revisions of "Execution engine"
From AMTech WikiDocs
(→Execution feedback and/or errors) |
(→Execution feedback and/or errors) |
||
| Line 4: | Line 4: | ||
==Execution feedback and/or errors== | ==Execution feedback and/or errors== | ||
| − | When an activity is being executed by the execution engine, | + | When an activity is being executed by the execution engine, an observationlifecycle type is sent to the ''activity_lifecycle'' topic. Some events are reported through the property '''event''' among this events: |
| − | * Start of a reasoner | + | * Start of a reasoner (start) |
| − | * End of a reasoner | + | * End of a reasoner (end) |
| − | * Execution errors | + | * Execution errors (error) |
This is a strong mechanism you can use to trace the execution of your activities if, at a given moment, you think they are not function as intended. | This is a strong mechanism you can use to trace the execution of your activities if, at a given moment, you think they are not function as intended. | ||
Revision as of 17:59, 26 April 2016
How it works
Execution feedback and/or errors
When an activity is being executed by the execution engine, an observationlifecycle type is sent to the activity_lifecycle topic. Some events are reported through the property event among this events:
- Start of a reasoner (start)
- End of a reasoner (end)
- Execution errors (error)
This is a strong mechanism you can use to trace the execution of your activities if, at a given moment, you think they are not function as intended.
Security context
- The reasoners get executed in the access control selected at reasoner's creation time
- Observation access control
- Entities access control
