Kepler Run Engine
-------------------------------------

Contributor: Matt Jones (jones@nceas.ucsb.edu)
             Jianwu Wang (jianwu@sdsc.edu)
             Jing Tao (tao@nceas.ucsb.edu)
             Michael Daigle (daigle@nceas.ucsb.edu) 
 
This product, Kepler Run Engine (KRE), consists of four components: the Workflow Scheduler, the Workflow Scheduler Client,  
the Workflow Run Engine, and the Workflow Run Engine client.            

The Workflow Scheduler (WFS) and client were originally implemented as part of the Threshold for Potential Concern (TPC) project. 
It is one piece in an architecture that currently includes Kepler, Metacat and the Workflow Run Engine. The WFS is a 
stand alone Java servlet web application. It handles requests to schedule, unschedule, reschedule, delete, and serve up 
workflows. It manages the schedules by wrapping the Quartz Scheduler utility. The WFS client provides a Java library to access the WFS
in Java applications. For more details, please see: https://kepler-project.org/developers/interest-groups/distributed/technical-documentation/overview-of-workflow-scheduler
The source code of the Workflow Scheduler and client is at: https://code.ecoinformatics.org/code/wfscheduler/

The Workflow Run Engine (WFRE) is to able to execute workflows remotely. It supports SOAP-based and RESTful invocation. The 
WFRE receives commands from the Workflow Scheduler and executes workflows. The WFRE client provides a Java library
to access the WFRE in Java applications. For more details, please see:
https://kepler-project.org/developers/interest-groups/distributed/technical-documentation/the-overview-of-the-workflow-run-engine-component