A language-based approach to addressing reliability in composite-Web services

Onyeka Ezenwoye, S. Masoud Sadjadi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

6 Scopus citations

Abstract

With Web services, distributed applications can be encapsulated as self-contained, discoverable software components that can be integrated to create other applications. BPEL allows for the composition of existing Web services to create new higher-function Web services. We identified that the techniques currently applied at development time are not sufficient for ensuring the reliability of composite Web services In this paper, we present a language-based approach to transparently adapting BPEL processes to improve reliability. This approach addresses reliability at the Business process layer (i.e the language layer) using a code generator, which weaves fault-tolerant code to the original code and an external proxy. The generated code uses standard BPEL constructs, and therefore, does not require any changes to the BPEL engine.

Original languageEnglish (US)
Title of host publication20th International Conference on Software Engineering and Knowledge Engineering, SEKE 2008
Pages649-654
Number of pages6
StatePublished - Dec 1 2008
Externally publishedYes
Event20th International Conference on Software Engineering and Knowledge Engineering, SEKE 2008 - San Francisco Bay, CA, United States
Duration: Jul 1 2008Jul 3 2008

Publication series

Name20th International Conference on Software Engineering and Knowledge Engineering, SEKE 2008

Other

Other20th International Conference on Software Engineering and Knowledge Engineering, SEKE 2008
Country/TerritoryUnited States
CitySan Francisco Bay, CA
Period7/1/087/3/08

Keywords

  • Adaptability
  • Business process
  • Reliability
  • Web service composition

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'A language-based approach to addressing reliability in composite-Web services'. Together they form a unique fingerprint.

Cite this