You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by ma...@apache.org on 2011/09/09 19:04:18 UTC
svn commit: r1167297 - in /oodt/trunk: CHANGES.txt
workflow/src/site/xdoc/development/developer.xml
Author: mattmann
Date: Fri Sep 9 17:04:17 2011
New Revision: 1167297
URL: http://svn.apache.org/viewvc?rev=1167297&view=rev
Log:
- fix for OODT-316 Add the WorkflowManager Use Case Diagram back into the User Guide
Modified:
oodt/trunk/CHANGES.txt
oodt/trunk/workflow/src/site/xdoc/development/developer.xml
Modified: oodt/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/oodt/trunk/CHANGES.txt?rev=1167297&r1=1167296&r2=1167297&view=diff
==============================================================================
--- oodt/trunk/CHANGES.txt (original)
+++ oodt/trunk/CHANGES.txt Fri Sep 9 17:04:17 2011
@@ -4,6 +4,9 @@ Apache OODT Change Log
Release 0.4: Current Development
--------------------------------------------
+* OODT-316 Add the WorkflowManager Use Case Diagram back into
+ the User Guide (mattmann)
+
* OODT-43 Add the FileManager Use Case Diagram back into the
User Guide (mattmann, cgoodale)
Modified: oodt/trunk/workflow/src/site/xdoc/development/developer.xml
URL: http://svn.apache.org/viewvc/oodt/trunk/workflow/src/site/xdoc/development/developer.xml?rev=1167297&r1=1167296&r2=1167297&view=diff
==============================================================================
--- oodt/trunk/workflow/src/site/xdoc/development/developer.xml (original)
+++ oodt/trunk/workflow/src/site/xdoc/development/developer.xml Fri Sep 9 17:04:17 2011
@@ -287,6 +287,33 @@ the License.
</subsection>
</section>
+ <section name="Use Cases">
+ <p>
+ The Workflow Manager was built to support several of the above capabilities. In particular there
+ were several use cases that we wanted to support, some
+ of which are described below.
+ </p>
+
+ <img src="../images/wm_use_case1.jpg" alt="Workflow Manager Event-based Execution Use Case"/>
+
+ <p>The black numbers in the above Figure correspond to a sequence of steps that occurs and a
+ series of interactions between the different Workflow Manager extension points in order to
+ perform the workflow execution activity. In Step 1, an event is provided to the Workflow
+ Manager event listenter (the System extension point), along with required Metadata. The
+ Workflow Manager, in step 2, looks up if ther are any associated Workflow Repository models
+ associated with the provided Event. If so, in steps 3 and 4, the returned Workflow models
+ are sent to the WorkflowEngine, to be turned into executable Workflow Instances.Each
+ WorkflowInstance is handed off to a WorkflowProcessorThread, taken from the ThreadPoolWorkflowEngine,
+ in steps 5 and 6. The WorkflowProcessorThread, in step 7, steps through each executable WorkflowTask,
+ checking to make sure that all necessary Workflow Conditions (if any) are satisfied. If all Workflow
+ Conditions are satisfied, then the Workflow Task is executed, either locally, or if an Resource Manager
+ is defined, then the task is sent (in step 7) to the Resource Manager (labeled <code>Process Manager</code>
+ in the figure). In steps 8-13, the WorkflowTask is executed on remote resources using the Resource Manager,
+ and eventually completed, with the final notification being sent back to the corresponding Workflow Processor
+ Thread, which is stepping through the Workflow Instance, controlling its exectuion. </p>
+
+ </section>
+
<section name="Conclusion">
<p>The aim of this document is to provide information relevant to developers
about the CAS Worklfow Manager. Specifically, this document has described the Workflow