Switching parties in a collaboration at run-time

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

5 Citations (Scopus)

Abstract

During the execution of a service collaboration, a party may drop out for technical reasons or business reasons. In that case, that party must be replaced in the collaboration, at run-time, by a new party. Ideally, the new party can pick up where the old party left. Currently, algorithms exist that can help with the selection and adaptation of the new party to incorporate it in the collaboration. Also, algorithms exist that can help to pick up a business process where it left off. However, to the best of our knowledge, no algorithms exist that can help a new party in a collaboration to pick up where the old party left off. This paper fills that gap, by providing an overview of the components and operations that are necessary to enable a party in a collaboration to be replaced by another party at run-time. In addition the paper presents two strategies, and the corresponding algorithms, that realize the architecture. As a proof-of-concept, a tool was developed that implements both strategies.
Original languageEnglish
Title of host publicationProceedings of the 2014 IEEE 18th International Enterprise Distributed Object Computing Conference (EDOC '14, Ulm, Germany, September 1-5, 2014)
EditorsManfred Reichert, Stefanie Rinderle-Ma, Georg Grossmann
Place of PublicationPiscataway
PublisherInstitute of Electrical and Electronics Engineers
Pages136-141
ISBN (Print)9781479954704
DOIs
Publication statusPublished - 2014
Event18th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2014) - Ulm, Germany
Duration: 1 Sept 20145 Sept 2014
Conference number: 18

Conference

Conference18th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2014)
Abbreviated titleEDOC 2014
Country/TerritoryGermany
CityUlm
Period1/09/145/09/14

Fingerprint

Dive into the research topics of 'Switching parties in a collaboration at run-time'. Together they form a unique fingerprint.

Cite this