Towards TransactionalWeb Services

Authors:
Benjamin A. Schmit;Schahram Dustdar
Affiliations:
Vienna University of Technology Information Systems Institute Distributed Systems Group Vienna, Austria, Europe;Vienna University of Technology Information Systems Institute Distributed Systems Group Vienna, Austria, Europe
Venue:
CECW '05 Proceedings of the Seventh IEEE International Conference on E-Commerce Technology Workshops
Year:
2005

Citing 0
Cited 7

A framework for ensuring consistency of Web Services Transactions

Information and Software Technology
Exploiting a database system in scheduling internet-based workflows

Proceedings of the 10th International Conference on Information Integration and Web-based Applications & Services
Ensuring recoverability in composing web services

Proceedings of the 11th International Conference on Information Integration and Web-based Applications & Services
The reliability of web services atomic commitment protocols

Proceedings of the 12th International Conference on Information Integration and Web-based Applications & Services
Systematic design of web service transactions

TES'05 Proceedings of the 6th international conference on Technologies for E-Services
Service Composition and Interaction in a SOC Middleware Supporting Separation of Concerns with Flows and Views

Journal of Database Management
Towards cost-aware service recovery

Proceedings of the 9th international ACM Sigsoft conference on Quality of software architectures

Quantified Score

Hi-index	0.00

Visualization

Abstract

When Web services are composed, transactions are needed to maintain the consistency of the distributed data in all but the most trivial cases. Today驴s Web service transaction speci?cations still leave some issues unresolved, e.g., the speci?cation of quality of service aspects. Therefore, we propose a modeling methodology that forces the software architect to address such issues at an early stage of development. The methodology is divided into four layers of UML diagrams which reference each other: structure, transactions, security, and work?ow. This separation of concerns can also be used to incorporate the knowledge of several experts into the design.