Difference between revisions of "Execution Engine"
From Gcube Wiki
(→Execution Plan) |
|||
| Line 1: | Line 1: | ||
| + | =Invokable Profile= | ||
=Execution Plan= | =Execution Plan= | ||
For a client of the [[ExecutionEngine]] to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars. | For a client of the [[ExecutionEngine]] to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars. | ||
Revision as of 20:09, 9 February 2010
Invokable Profile
Execution Plan
For a client of the ExecutionEngine to be able to formally describe the plan that he wants to execute, the constructs offered by the Execution Plan are used. These constructs have the following main pillars.
- Execution Plan Configuration
- Every plan is potentially one execution unit for the execution engine. Each plan while executing can request different parametrization.
- Execution Plan Variables
- Tha variables defined in a plan are the common data placeholders through which the elements of the plan exchange data.
- Execution Engine Data Types
- Each variable is typed and this type describes the different characteristics of the data exchanged.
- Execution Engine Parameters
- Each variable is accessed through defined parameters. Parameters are distinguished by their direction and processing.
- Plan Execution Tree
- The plan hierarchy is composed of a number of elements that control the flow and the actions of the plan
