Engineering a BPEL orchestration engine as a multi-agent system

The BPEL language is currently the primary candidate for standardising Web Services orchestration. BPEL specifications are meant to be run by BPEL orchestration engines, which are therefore crucial components of today’s business-to-business infrastructures, carrying the burden of dynamically composi...

Full description

Saved in:
Bibliographic Details
Published in:Science of computer programming Vol. 66; no. 3; pp. 226 - 245
Main Authors: Viroli, Mirko, Denti, Enrico, Ricci, Alessandro
Format: Journal Article
Language:English
Published: Elsevier B.V 15.05.2007
Subjects:
Coordination models
Languages process algebra
Multiagent systems
Orchestration languages
Coordination models
Multiagent systems
Orchestration languages
Languages process algebra
ISSN:0167-6423, 1872-7964
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The BPEL language is currently the primary candidate for standardising Web Services orchestration. BPEL specifications are meant to be run by BPEL orchestration engines, which are therefore crucial components of today’s business-to-business infrastructures, carrying the burden of dynamically composing existing services. In this paper, we present the design of a BPEL orchestration engine based on a multi-agent system: while the basic BPEL activities are autonomously executed by agents, workflow aspects are realised by the mediation of ReSpecT tuple centres, a coordination model extending Linda with the ability of declaratively programming the tuple space behaviour. Our architecture separates the interaction, correlation, and workflow concerns into clearly identified tiers. In particular, we identify the workflow tier as the one encapsulating the core and most critical behaviour of the engine: due to its intrinsic complexity, we tackle its design formally. We introduce a core algebraic language of BPEL dealing with its workflow-related aspects, and provide it with a semantics based on a mapping into a net specification, modelling the dependencies between the activities to be executed by the engine. This mapping plays the role of a formal design, since it directly leads to an implementation of the workflow tier in the orchestration engine.
ISSN:0167-6423
1872-7964
DOI:10.1016/j.scico.2007.01.008