ACM Home Page
Please provide us with feedback. Feedback
Workflow history management
Full text PdfPdf (239 KB)
Source ACM SIGMOD Record archive
Volume 27 ,  Issue 1  (March 1998) table of contents
Pages: 67 - 75  
Year of Publication: 1998
ISSN:0163-5808
Authors
Pinar Koksal  Software Research and Development Center, Department of Computer Engineering, Middle East Technical University (METU), 06531 Ankara Turkiye
Sena Nural Arpinar  Software Research and Development Center, Department of Computer Engineering, Middle East Technical University (METU), 06531 Ankara Turkiye
Asuman Dogac  Software Research and Development Center, Department of Computer Engineering, Middle East Technical University (METU), 06531 Ankara Turkiye
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 29,   Citation Count: 6
Additional Information:

abstract   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/273244.273265
What is a DOI?

ABSTRACT

A workflow history manager maintains the information essential for workflow monitoring and data mining as well as for recovery and authorization purposes.Certain characteristics of workflow systems like the necessity to run these systems on heterogeneous, autonomous and distributed environments and the nature of data, prevent history management in workflows to be handled by the classical data management techniques like distributed DBMSs. We further demonstrate that multi-database query processing techniques are also not appropriate for the problem at hand.In this paper, we describe history management, i.e., the structure of the history and querying of the history, in a fully distributed workflow architecture realized in conformance with Object Management Architecture (OMA) of OMG. By fully distributed architecture we mean that the scheduler of the workflow system is distributed and in accordance with this, the history objects related with activities are stored on data repositories (like DBMSs, files) available at the sites involved. We describe the structure of the history objects determined according to the nature of the data and the processing needs, and the possible query processing strategies on these objects using the Object Query Service of OMG. We then present the comparison of these strategies according to a cost model developed.



Collaborative Colleagues:
Pinar Koksal: colleagues
Sena Nural Arpinar: colleagues
Asuman Dogac: colleagues