Transactional Composite Service
by
Dragan Ivanovic
—
last modified
Apr 25, 2012 20:29
—
filed under:
KnowledgeModel
Definitions
| Term: Transactional Composite Service |
Domain: Cross-cutting issues | ||||
|---|---|---|---|---|---|
| Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
| D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
| Service Composition and
Coordination (KM-SC) |
To create a Transaction Composite Service, one must be able to define orchestration among the component services using dependencies to specify how services are coupled and how the behaviour of the given services influences the behaviour of some others. These dependencies are used to express the relationships (sequence, alternative, compensation,. . .etc ) between component services. [Bhiri05] |
Transactional Composite Service is a service composed
of individual transactional
services. |
|||
| Service Infrastructure (KM-SI) |
The underlying assumption in creating transactional composite services is that the service infrastructure consists of services that employ transactional properties. [Bhiri05] | ||||
| Generic (domain independent) |
|||||
Competencies
- UCBL: Transactional Web Service; http://liris.cnrs.fr/bd/; Mohsen
Rouached, Salima Benbernou
Scenarios
References
- [Bhiri05] Sami Bhiri, Olivier Perrin, Claude Godart, and Khaled
Gaaloul: Transactional Patterns: Combining Workflow Flexibility
and Transactional Reliability for Composite Web Services. 3rd International Conference on Business Process Management - BPM'05 3649 (2005) 440-445
