Difference between revisions of "Debug & check a reasoner"

From AMTech WikiDocs
Jump to: navigation, search
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
==Run==
 
[[File:Rd1.png|thumbnail|left|execute]]
 
[[File:Rd1.png|thumbnail|left|execute]]
Allows to check the execution of a reasoner without the need to be published and deployed.
+
Allows you to check the execution of a reasoner without the need to deploy it.
*The reasoners executes in a sandbox with the security context of the activity-creator checking the reasoners
+
* The reasoners executes in a sandbox with the security context of the creator.
*The checking executes the same logic is executed when the reasoner is deploy.
+
* For those reasoners that execute actions for each thing returned by the observer (foreach reasoners), the execution in this mode only runs for the first thing returned by the observer.
**The only difference is that the user selects an instance of the observation type configured.
+
* It executes the same logic that would execute the engine for deployed reasoner.
**The creator can request for more detail information by using the function '''debug''' this option is only available for javascript options
+
* The creator initiates the execution by selecting an instance of the observation type configured. (See [[Simulator|Simulator]])
***The results appears in a segment like the following
+
[[File:Rd2.png|650px|thumbnail|center|Select observation instance]]
INFO: action helloWorld Doing single binding for property: producer
+
 
INFO: action helloWorld BEGIN: JS evaluation debug
+
==Debug==
INFO: action helloWorld DEBUGGING *** helloWorldProducer
+
The creator can request for more detail information by using the function '''debug''' this option is only available for javascript options
INFO: action helloWorld END: JS evaluation debug
+
[[File:Rd3.png|1050px|thumbnail|center|Select observation instance]]
**After the reasoner has been execute and the result are the expected please check it valid and save it.
+
*The results appears in a segment like the following
***If this operation is omitted the publication process will abort with an error
+
    INFO: action helloWorld BEGIN: JS evaluation debug
 +
    INFO: action helloWorld DEBUGGING *** helloWorldProducer
 +
    INFO: action helloWorld END: JS evaluation debug
 +
[[File:Rd4.png|1050px|thumbnail|center|Select observation instance]]
 +
 
 +
==Check==
 +
After the reasoner has been execute and the result are the expected please check Ready to be published.
 +
[[File:Rd5.png|thumbnail|left|Ready]]
 +
*If this operation is omitted the publication process will abort with an error

Latest revision as of 10:45, 16 May 2016

Run

execute

Allows you to check the execution of a reasoner without the need to deploy it.

  • The reasoners executes in a sandbox with the security context of the creator.
  • For those reasoners that execute actions for each thing returned by the observer (foreach reasoners), the execution in this mode only runs for the first thing returned by the observer.
  • It executes the same logic that would execute the engine for deployed reasoner.
  • The creator initiates the execution by selecting an instance of the observation type configured. (See Simulator)
Select observation instance

Debug

The creator can request for more detail information by using the function debug this option is only available for javascript options

Select observation instance
  • The results appears in a segment like the following
   INFO: action helloWorld BEGIN: JS evaluation debug
   INFO: action helloWorld DEBUGGING *** helloWorldProducer
   INFO: action helloWorld END: JS evaluation debug
Select observation instance

Check

After the reasoner has been execute and the result are the expected please check Ready to be published.

Ready
  • If this operation is omitted the publication process will abort with an error