Supporting the dynamic evolution of Web service protocols in service-oriented architectures

Seung Hwan Ryu, Fabio Casati, Halvard Skogsrud, Boualem Benatallah, Régis Saint-Paul

Research output: Contribution to journalArticle

84 Citations (Scopus)

Abstract

In service-oriented architectures, everything is a service and everyone is a service provider. Web services (or simply services) are loosely coupled software components that are published, discovered, and invoked across the Web. As the use of Web service grows, in order to correctly interact with them, it is important to understand the business protocols that provide clients with the information on how to interact with services. In dynamic Web service environments, service providers need to constantly adapt their business protocols for reflecting the restrictions and requirements proposed by new applications, new business strategies, and new laws, or for fixing problems found in the protocol definition. However, the effective management of such a protocol evolution raises critical problems: one of the most critical issues is how to handle instances running under the old protocol when it has been changed. Simple solutions, such as aborting them or allowing them to continue to run according to the old protocol, can be considered, but they are inapplicable for many reasons (for example, the loss of work already done and the critical nature of work). In this article, we present a framework that supports service managers in managing the business protocol evolution by providing several features, such as a variety of protocol change impact analyses automatically determining which ongoing instances can be migrated to the new version of protocol, and data mining techniques inferring interaction patterns used for classifying ongoing instances migrateable to the new protocol. To support the protocol evolution process, we have also developed database-backed GUI tools on top of our existing system. The proposed approach and tools can help service managers in managing the evolution of ongoing instances when the business protocols of services with which they are interacting have changed.

Original languageEnglish
Article number13
JournalACM Transactions on the Web
Volume2
Issue number2
DOIs
Publication statusPublished - 1 Apr 2008
Externally publishedYes

Fingerprint

Service oriented architecture (SOA)
Web services
Network protocols
Industry
Managers
Graphical user interfaces
World Wide Web
Data mining

Keywords

  • Business protocols
  • Change impact analysis
  • Decision trees
  • Dynamic evolution
  • Ongoing instances
  • Web services

ASJC Scopus subject areas

  • Computer Networks and Communications

Cite this

Supporting the dynamic evolution of Web service protocols in service-oriented architectures. / Ryu, Seung Hwan; Casati, Fabio; Skogsrud, Halvard; Benatallah, Boualem; Saint-Paul, Régis.

In: ACM Transactions on the Web, Vol. 2, No. 2, 13, 01.04.2008.

Research output: Contribution to journalArticle

Ryu, Seung Hwan ; Casati, Fabio ; Skogsrud, Halvard ; Benatallah, Boualem ; Saint-Paul, Régis. / Supporting the dynamic evolution of Web service protocols in service-oriented architectures. In: ACM Transactions on the Web. 2008 ; Vol. 2, No. 2.
@article{672a1c6fa246436f9be8b23cfe162546,
title = "Supporting the dynamic evolution of Web service protocols in service-oriented architectures",
abstract = "In service-oriented architectures, everything is a service and everyone is a service provider. Web services (or simply services) are loosely coupled software components that are published, discovered, and invoked across the Web. As the use of Web service grows, in order to correctly interact with them, it is important to understand the business protocols that provide clients with the information on how to interact with services. In dynamic Web service environments, service providers need to constantly adapt their business protocols for reflecting the restrictions and requirements proposed by new applications, new business strategies, and new laws, or for fixing problems found in the protocol definition. However, the effective management of such a protocol evolution raises critical problems: one of the most critical issues is how to handle instances running under the old protocol when it has been changed. Simple solutions, such as aborting them or allowing them to continue to run according to the old protocol, can be considered, but they are inapplicable for many reasons (for example, the loss of work already done and the critical nature of work). In this article, we present a framework that supports service managers in managing the business protocol evolution by providing several features, such as a variety of protocol change impact analyses automatically determining which ongoing instances can be migrated to the new version of protocol, and data mining techniques inferring interaction patterns used for classifying ongoing instances migrateable to the new protocol. To support the protocol evolution process, we have also developed database-backed GUI tools on top of our existing system. The proposed approach and tools can help service managers in managing the evolution of ongoing instances when the business protocols of services with which they are interacting have changed.",
keywords = "Business protocols, Change impact analysis, Decision trees, Dynamic evolution, Ongoing instances, Web services",
author = "Ryu, {Seung Hwan} and Fabio Casati and Halvard Skogsrud and Boualem Benatallah and R{\'e}gis Saint-Paul",
year = "2008",
month = "4",
day = "1",
doi = "10.1145/1346237.1346241",
language = "English",
volume = "2",
journal = "ACM Transactions on the Web",
issn = "1559-1131",
publisher = "Association for Computing Machinery (ACM)",
number = "2",

}

TY - JOUR

T1 - Supporting the dynamic evolution of Web service protocols in service-oriented architectures

AU - Ryu, Seung Hwan

AU - Casati, Fabio

AU - Skogsrud, Halvard

AU - Benatallah, Boualem

AU - Saint-Paul, Régis

PY - 2008/4/1

Y1 - 2008/4/1

N2 - In service-oriented architectures, everything is a service and everyone is a service provider. Web services (or simply services) are loosely coupled software components that are published, discovered, and invoked across the Web. As the use of Web service grows, in order to correctly interact with them, it is important to understand the business protocols that provide clients with the information on how to interact with services. In dynamic Web service environments, service providers need to constantly adapt their business protocols for reflecting the restrictions and requirements proposed by new applications, new business strategies, and new laws, or for fixing problems found in the protocol definition. However, the effective management of such a protocol evolution raises critical problems: one of the most critical issues is how to handle instances running under the old protocol when it has been changed. Simple solutions, such as aborting them or allowing them to continue to run according to the old protocol, can be considered, but they are inapplicable for many reasons (for example, the loss of work already done and the critical nature of work). In this article, we present a framework that supports service managers in managing the business protocol evolution by providing several features, such as a variety of protocol change impact analyses automatically determining which ongoing instances can be migrated to the new version of protocol, and data mining techniques inferring interaction patterns used for classifying ongoing instances migrateable to the new protocol. To support the protocol evolution process, we have also developed database-backed GUI tools on top of our existing system. The proposed approach and tools can help service managers in managing the evolution of ongoing instances when the business protocols of services with which they are interacting have changed.

AB - In service-oriented architectures, everything is a service and everyone is a service provider. Web services (or simply services) are loosely coupled software components that are published, discovered, and invoked across the Web. As the use of Web service grows, in order to correctly interact with them, it is important to understand the business protocols that provide clients with the information on how to interact with services. In dynamic Web service environments, service providers need to constantly adapt their business protocols for reflecting the restrictions and requirements proposed by new applications, new business strategies, and new laws, or for fixing problems found in the protocol definition. However, the effective management of such a protocol evolution raises critical problems: one of the most critical issues is how to handle instances running under the old protocol when it has been changed. Simple solutions, such as aborting them or allowing them to continue to run according to the old protocol, can be considered, but they are inapplicable for many reasons (for example, the loss of work already done and the critical nature of work). In this article, we present a framework that supports service managers in managing the business protocol evolution by providing several features, such as a variety of protocol change impact analyses automatically determining which ongoing instances can be migrated to the new version of protocol, and data mining techniques inferring interaction patterns used for classifying ongoing instances migrateable to the new protocol. To support the protocol evolution process, we have also developed database-backed GUI tools on top of our existing system. The proposed approach and tools can help service managers in managing the evolution of ongoing instances when the business protocols of services with which they are interacting have changed.

KW - Business protocols

KW - Change impact analysis

KW - Decision trees

KW - Dynamic evolution

KW - Ongoing instances

KW - Web services

UR - http://www.scopus.com/inward/record.url?scp=43749124807&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=43749124807&partnerID=8YFLogxK

U2 - 10.1145/1346237.1346241

DO - 10.1145/1346237.1346241

M3 - Article

AN - SCOPUS:43749124807

VL - 2

JO - ACM Transactions on the Web

JF - ACM Transactions on the Web

SN - 1559-1131

IS - 2

M1 - 13

ER -