Achieving survivability in business process execution language for Web services (BPEL) with exception-flows

Survivability is defined as the capability of a service to fulfill its mission in a timely manner, even in the presence of attacks, failures, or accidents. Because of the severe consequences of failure, organizations are focusing on service survivability as a key risk management strategy for business processes. There are three key survivability properties: resistance, recognition, and recovery. Recovery, a hallmark of survivability, is the capability to maintain critical components and resource during attack, limit the extent of damage, and restore full services following attack. Exception handling is a way to deals with the recovery aspect of survivability. Business process execution language for Web services (BPEL) has been proposed for formal specification of business processes and interaction protocols. BPEL defines an interoperable integration model that facilitates expansion of automated process integration in both intra- and intercorporate environments. A business process description requires the specification of both the normal flow and the possible variations due to exceptional situations that can be anticipate and monitored. This paper bridges the analysis of business process survivability and its recovery aspect in terms of exception handling in the context of BPEL. The feasibility of the proposed model is demonstrated using an illustrative travel reservation example.

[1]  Jennifer Widom,et al.  Behavior of database production rules: termination, confluence, and observable determinism , 1992, SIGMOD '92.

[2]  Fabio Casati,et al.  Modeling exceptional behaviors in commercial workflow management systems , 1999, Proceedings Fourth IFCIS International Conference on Cooperative Information Systems. CoopIS 99 (Cat. No.PR00384).

[3]  Gregor Hohpe,et al.  Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions , 2003 .

[4]  Jan Mendling Business Process Execution Language for Web Service (BPEL) , 2006 .

[5]  Dickson K. W. Chiu,et al.  Web Interface-Driven Cooperative Exception Handling in Adome Workflow Management System , 2001, Inf. Syst..

[6]  John McHugh,et al.  Survivable Network Analysis Method , 2000 .

[7]  Alexander Borgida,et al.  Tolerating exceptions in workflows: a unified framework for data and processes , 1999 .

[8]  Alexander Borgida,et al.  Tolerating exceptions in workflows: a unified framework for data and processes , 1999, WACC '99.

[9]  Guijun Wang,et al.  Evolution of composition framework in a distributed system toolkit , 2004, Proceedings. IEEE International Conference on Web Services, 2004..

[10]  Jian Tang,et al.  Mining exception instances to facilitate workflow exception handling , 1999, Proceedings. 6th International Conference on Advanced Systems for Advanced Applications.

[11]  Andrew P. Moore,et al.  Attack Modeling for Information Security and Survivability , 2001 .

[12]  Guijun Wang,et al.  Architecture paradigms and their influences and impacts on component-based software systems , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[13]  Matjaz B. Juric,et al.  Business process execution language for web services , 2004 .

[14]  Dickson K. W. Chiu,et al.  A Meta Modeling Approach to Workflow Management Systems Supporting Exception Handling , 1999, Inf. Syst..

[15]  Anthony J. Bonner,et al.  Workflow, transactions and datalog , 1999, PODS.