Difference between revisions of "Workflow Engine"
| Line 2: | Line 2: | ||
The Workflow Engine operates on top of the [[ExecutionEngine]]. Its purpose is to abstract over the low level details that are needed by the [[ExecutionEngine]] and the [[ExecutionPlan]] it is provided with. | The Workflow Engine operates on top of the [[ExecutionEngine]]. Its purpose is to abstract over the low level details that are needed by the [[ExecutionEngine]] and the [[ExecutionPlan]] it is provided with. | ||
=Adaptors= | =Adaptors= | ||
| + | One of the functionalities offered by the WorkflowEngine is the possibility to bridge between existing well known job description and workflow definition languages and the internally used [[WorkflowLanguage]] which is subsequently transformed in the an [[ExecutionPlan]]. This bridging is performed by means of 'Adaptors' | ||
| + | |||
| + | Adaptors are implemented to operate on a specific third party language which they can understand, parse, and translate into internally used constructs. This way the WorkflowEngine opens up its usability level since existing workflows already defined in third party languages can be easily incorporated. Additionally, the learning curve for anyone wishing to use the execution and workflow capabilities of the system is greatly reduced as depending on ones needs one can simply focus on one of the existing supported languages which will best match the job at hand. | ||
| + | |||
| + | Currently | ||
Revision as of 15:14, 29 January 2010
Overview
The Workflow Engine operates on top of the ExecutionEngine. Its purpose is to abstract over the low level details that are needed by the ExecutionEngine and the ExecutionPlan it is provided with.
Adaptors
One of the functionalities offered by the WorkflowEngine is the possibility to bridge between existing well known job description and workflow definition languages and the internally used WorkflowLanguage which is subsequently transformed in the an ExecutionPlan. This bridging is performed by means of 'Adaptors'
Adaptors are implemented to operate on a specific third party language which they can understand, parse, and translate into internally used constructs. This way the WorkflowEngine opens up its usability level since existing workflows already defined in third party languages can be easily incorporated. Additionally, the learning curve for anyone wishing to use the execution and workflow capabilities of the system is greatly reduced as depending on ones needs one can simply focus on one of the existing supported languages which will best match the job at hand.
Currently
