Difference between revisions of "Execution engine"
From AMTech WikiDocs
(→Security context) |
(→Execution errors) |
||
| Line 2: | Line 2: | ||
[[File:RuleEngineHowItWorks.jpg]] | [[File:RuleEngineHowItWorks.jpg]] | ||
| − | ==Execution errors== | + | ==Execution feedback and/or errors== |
| − | + | When an activity is being executed by the execution engine, some events are reported through the ''activity_lifecycle'' topic. Among this events: | |
| + | |||
| + | * Start of a reasoner | ||
| + | * End of a reasoner | ||
| + | * Execution errors | ||
| + | |||
| + | 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== | ==Security context== | ||
Revision as of 22:02, 25 April 2016
How it works
Execution feedback and/or errors
When an activity is being executed by the execution engine, some events are reported through the activity_lifecycle topic. Among this events:
- Start of a reasoner
- End of a reasoner
- Execution errors
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
