Specification of Transactional Requirements for Web Services using Recoverability

Specification of Transactional Requirements for Web Services using Recoverability

Kanchana Rajaram (SSN College of Engineering, Anna University, Chennai, Tamil Nadu, India), Chitra Babu (SSN College of Engineering, Anna University, Chennai, Tamil Nadu, India) and Arun Adiththan (City University of New York (CUNY), New York, USA)
DOI: 10.4018/jitwe.2013010104
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

In Service-Oriented Computing (SOC), a business transaction comprises of several web services provided by multiple enterprises. The transactional behaviour of individual web services must be considered for service selection so that the composition of web services results in a reliable execution. It is difficult for a business analyst to envisage the desired business policies of a process in terms of transactional properties of the corresponding service. Hence, an abstract mechanism that enables the business analyst to specify the transactional properties in a simple manner must be introduced. Towards this objective, it is proposed to express the transactional properties in terms of the recoverability of services. The transactional web services are grouped into different levels of recoverability based on their recovery cost. The estimated recovery costs are empirically verified and validated.
Article Preview

Existing Work

The Web Service Conversation Language (WSCL) (Banerji, 2002) and the Web service Choreography Interface (WSCI) (WSCI, 2002) offer conversational meta-models that describe the external behaviour of a service in terms of the acceptable sequence of web service invocations. In addition, WSCI supports message correlation, message choreography, and service operation compensation. Web service transaction protocols such as Web Service Coordination (WS-C) (Carera, 2005), Web Service Transaction (WS-T) (WST, 2005) and Business Transfer Protocol (BTP) (Ceponkus, 2002) propose specific conversations that can be used to coordinate interacting parties and provide transactional properties. However, they do not provide a set of relevant abstractions to model service behaviors.

Web Services Transaction Language (WSTL) (Pires, 2003), a language extension over BPEL (Jordan, 2009) that provides transactional description support. WSTL defines its root element, transactionDefinitions, as a direct child of the wsdl:definitions element. The transactionDefinitions element has two child transactionBehavior elements each containing transaction semantics information on the operations supported by that Web service. The transactionBehaviour element has a type attribute whose values can be compensable, virtualcompensable, retriable, and pivot. These values are not much meaningful to the business analyst and the pros and cons of a service with a specific type of behaviour are not visible. The transactional behaviour type or property does not provide any abstraction for the business analyst to choose a service with an appropriate behaviour.

Jiuxin et al. (2010) defined conception-constrained rules for expressing the business logic of a transaction. In the absence of a suitable abstraction, it is a tough task for the business analyst to express the business requirements in the form of constraint rules.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 13: 4 Issues (2018): 1 Released, 3 Forthcoming
Volume 12: 4 Issues (2017)
Volume 11: 4 Issues (2016)
Volume 10: 4 Issues (2015)
Volume 9: 4 Issues (2014)
Volume 8: 4 Issues (2013)
Volume 7: 4 Issues (2012)
Volume 6: 4 Issues (2011)
Volume 5: 4 Issues (2010)
Volume 4: 4 Issues (2009)
Volume 3: 4 Issues (2008)
Volume 2: 4 Issues (2007)
Volume 1: 4 Issues (2006)
View Complete Journal Contents Listing