Work ow History Management

A workkow history manager maintains the information essential for workkow monitoring and data mining as well as for recovery and authorization purposes. Certain characteristics of workkow systems like the necessity to run these systems on heterogeneous, autonomous and distributed environments and the nature of data, prevent history management in workkows 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 workkow architecture realized in conformance with Object Management Architecture (OMA) of OMG. By fully distributed architecture we mean that the scheduler of the workkow system is distributed and in accordance with this, the history objects related with activities are stored on data repositories (like DBMSs, les) 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.

[1]  Andreas Reuter,et al.  The ConTract Model , 1991, Database Transaction Models for Advanced Applications.

[2]  R. G. G. Cattell,et al.  The Object Database Standard: ODMG-93 , 1993 .

[3]  Asuman Dogac,et al.  Dynamic query optimization on a distributed object management platform , 1996, CIKM '96.