A. Cichocki. A prototype of a workflow execution controller Summer intern report and documentation, Databases and Formal Methods Research Group, Bellcore, 1994. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Managing Heterogeneous Multi-system Tasks to Support.. - Krishnakumar, Sheth (1995) (60 citations) (Correct)
....that for every such failure of an enabled controllable transition, the task makes a transition to a corresponding err state, e.g. start err. Since handling the errors of each transition might make the specification very tedious, another approach that has been explored in a Bellcore prototype [11] is to specify a default state such as failed or aborted that is reached when such an error happens. Observe that a task structure does not determine the means of execution nor the functionality of the task, but only a high level description of the (visible) state transitions. Two tasks might ....
....that fails and recovers must interact with the workflow controller to resynchronize with the controller (it is possible that another task manager has been started up in the 28 N. KRISHNAKUMAR AND A. SHETH meantime to handle the same task) The recovery mechanisms used are documented in [27] and [11]. Notice however that interactions between task managers and the interfaces to processing entities might not be reliable. It is therefore possible that the same tasks may be resubmitted to a processing entity (possibly if the task manager detects a communications failure) It is imperative that ....
A. Cichocki. A prototype of a workflow execution controller Summer intern report and documentation, Databases and Formal Methods Research Group, Bellcore, 1994.
Managing Heterogeneous Multi-system Tasks to Support.. - Narayanan Krishnakumar (1995) (3 citations) (Correct)
....that for every such failure of an enabled controllable transition, the task makes a transition to a corresponding err state, e.g. start err. Since handling the errors of each transition might make the specification very tedious, another approach that has been explored in a Bellcore prototype [10] is to specify a default state such as failed or aborted that is reached when such an error happens. Failures of the workflow controller or task managers executing the tasks are assumed to be handled by the recovery process. A user task or script could be characterized by the non transactional ....
....at the time of failure. Any task manager that fails and recovers must interact with the workflow controller to resynchronize with the controller (it is possible that another task manager has been started up in the meantime to handle the same task) The recovery mechanisms used are documented in [25, 10]. Notice however that interactions between processing entities and the workflow management system might not be reliable. It is therefore possible that the same tasks may be submitted again to the processing entity (possibly if the task manager detects a communications failure) It is imperative ....
A. Cichocki. A prototype of a workflow execution controller Summer intern report and documentation, Databases and Formal Methods Research Group, Bellcore, 1994.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC