|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (2)
View Page History
...
Web Site: [https://salty.unice.fr/|https://salty.unice.fr/] The aim of EBM in this project is to face adaptation issues in the context of ESBs and services orchestration. By using the Salty adaptation framework, we expect to manage long and versatile workflows by enhancing features of [EasyBPEL|easybpel:EasyBPEL Overview] and [EasyVIPER|easyviper:EasyViper Overview].
In particular sensors and effectors are expected to be developed according to the Salty framework:
* Sensors consist in SCA intents put upon workflows nodes. These intents can send notifications about functional and non-functional information to a controller.
* Sensors consist in SCA intents put upon workflows nodes. These intents can send notifications about functional and non-functional information to a controller.
In particular sensors and effectors are expected to be developed according to the Salty framework. They are implemented within an administration interface of the workflow engine, exposed as Web Service. The administration is composed of three parts:
# The Notification part, based on WS-Notification and subscribe/notify mechanism. This part allows to subscribe on particular events related to a workflow, and to retrieve functional and non functional information (service latency, which branch of the workflow is executed, service invokation failure, ...)
# The Observation part allows to get some informations about deployed workflows, their status, status of their nodes.
# The Command part allows to (un-)store, start, stop a workflow, to update it by replacing the behavior of a node, ...
Sensors consist then in either SCA intents put upon workflows nodes, either getter operations upon workflows. These intents can send notifications about functional and non-functional information to a controller. For more information about SCA intents
* Effectors consist in a administration interface exposed as Web Service in order for the controller to store/start/stop a workflow, replacing nodes behviors and adapt thus it according to the situation.
Let us notice that this administration exposes also getters and subscription operations that are used at sensors level.
# The Notification part, based on WS-Notification and subscribe/notify mechanism. This part allows to subscribe on particular events related to a workflow, and to retrieve functional and non functional information (service latency, which branch of the workflow is executed, service invokation failure, ...)
# The Observation part allows to get some informations about deployed workflows, their status, status of their nodes.
# The Command part allows to (un-)store, start, stop a workflow, to update it by replacing the behavior of a node, ...
Sensors consist then in either SCA intents put upon workflows nodes, either getter operations upon workflows. These intents can send notifications about functional and non-functional information to a controller. For more information about SCA intents
* Effectors consist in a administration interface exposed as Web Service in order for the controller to store/start/stop a workflow, replacing nodes behviors and adapt thus it according to the situation.
Let us notice that this administration exposes also getters and subscription operations that are used at sensors level.