Compensability of Business Processes
When a business process executed in a SOA environment cannot fully achieve its goal, it should perform a compensation of its already completed activities. This method is widely used by the standards related to the executing of business processes in SOA environments. Many of the specifications relative to the types of process coordination, execution languages and notations which are used to design business processes are based on this approach. Unfortunately, there is no specification which provides mechanisms that guarantee the possibility of compensation. The lack of such mechanisms may lead to the situations which in the BPMN standard are defined as "hazardous". They occur when an execution of a process can neither be completed nor fully compensated. The result of this process is undetermined, inconsistent with intentions of a designer of a process and can lead to the loss of consistency. These cases often enforce manual engagement in resolving the situation and are a serious problem if we deal with numerous instances of processes.
This article focuses on this issue, presents its analysis as well as a solution to it.
KeywordsBusiness Process Coordination Mechanism Business Process Model Compensation Activity Business Process Execution Language
- 1.Business process model and notation (bpmn) version 2.0 (January 2011)Google Scholar
- 3.Alrifai, M., Dolog, P., Vej, F.B., Dk-Aalborg, Nejdl, W.: Transactions concurrency control in web service environment. In: ECOWS 2006: Proceedings of the European Conference on Web Services, pp. 109–118. IEEE (December 2006)Google Scholar
- 4.Alves, A., Arkin, A., Askary, S., Barreto, C., Bloch, B., Curbera, F., Ford, M., Goland, Y., Guízar, A., Kartha, N., Liu, C.K., Khalaf, R., König, D., Marin, M., Mehta, V., Thatte, S., van der Rijn, D., Yendluri, P., Yiu, A.: Web services business process execution language (April 2009)Google Scholar
- 5.Ambroszkiewicz, S., Brzeziński, J., Cellary, W., Grzech, A., Zieliński, K. (eds.): SOA Infrastructure Tools - Concepts and Methods. Poznan University of Economics Press (2010)Google Scholar
- 6.Bhiri, S., Perrin, O., Godart, C.: Ensuring required failure atomicity of composite web services. In: WWW, pp. 138–147 (2005)Google Scholar
- 7.Choi, S., Jang, H., Kim, H., Kim, J.-S., Kim, S.M., Song, J., Lee, Y.-J.: Maintaining Consistency Under Isolation Relaxation of Web Services Transactions. In: Ngu, A.H.H., Kitsuregawa, M., Neuhold, E.J., Chung, J.-Y., Sheng, Q.Z. (eds.) WISE 2005. LNCS, vol. 3806, pp. 245–257. Springer, Heidelberg (2005)CrossRefGoogle Scholar
- 8.Erven, H., Hicker, G., Huemer, C., Zaptletal, M.: The web services-businessactivity-initiator (ws-ba-i) protocol: an extension to the web services-businessactivity specification. In: IEEE International Conference on Web Services, ICWS 2007, pp. 216–224 (July 2007)Google Scholar
- 9.Freund, T., Little, M.: Oasis web services business activity version 1.2 (February 2009)Google Scholar
- 10.Jankiewicz, K., Morzy, T., Kujawiñski, K., Mor, M.: Transaction mechanisms in complex business processes. Control and Cybernetics (2011) (special issue) (in preparation)Google Scholar
- 11.Krafzig, D., Banke, K., Slama, D.: Enterprise SOA: Service-Oriented Architecture Best Practices. The Coad Series. Prentice Hall, Upper Saddle River (2004)Google Scholar
- 12.McGovern, J., Sims, O., Jain, A., Little, M.: Enterprise Service Oriented Architectures: Concepts, Challenges, Recommendations. Springer-Verlag New York, Inc., Secaucus (2006)Google Scholar