|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (5)
View Page Historyh1. Features
The Observation module provides some information about deployed workflows, their status, status of their nodes. This is implemented by an administration upon EasyVIPER main components.
Observation operations are
# *getProcessDefinitionsNames*: lists workflows QNames installed in EasyVIPER.
# *getProcessDefinitionEndpoints*: lists endpoints exposed by a particular workflow (defined by its QName).
# *getProcessInstancesNames*: lists instances names of a particular workflow (defined by its QName).
# *getProcessInstanceState*: gives the state of a workflow instance (INACTIVE, ACTIVE, ENDED, UNSTABLE).
# *getActivityState*: gives the state of an activity for a particular workflow. An activity is an EasyVIPER behaviour located on a node of the workflow.
# *getProcessDefinitionsNames*: lists workflows QNames installed in EasyVIPER.
# *getProcessDefinitionEndpoints*: lists endpoints exposed by a particular workflow (defined by its QName).
# *getProcessInstancesNames*: lists instances names of a particular workflow (defined by its QName).
# *getProcessInstanceState*: gives the state of a workflow instance (INACTIVE, ACTIVE, ENDED, UNSTABLE).
# *getActivityState*: gives the state of an activity for a particular workflow. An activity is an EasyVIPER behaviour located on a node of the workflow.
The input of the observation service is the *getProcessDefinitions* operation that does not need any input. It gives the list of process definitions, i.e. the QNames of deployed workflows. This allows to access to workflow instances thanks to another operation. Then we can access to the state of instances and more precisely on node states.
The first operation does not need any input. It gives the list of process definitions, i.e. the QNames of deployed workflows. This allows to access to workflow instances thanks to the 3rd operation. Then we can access to the state of instances and more precisely on node states.
These features intend to help a self-adaptive framework to know enough information for adaptation controlling.
h1. EasyVIPER auto-generated documentation from WSDL
{wsdl:url=http://resources.petalslink.org/research/dev/experimental/easyviper/services/extended-service-observation/src/main/resources/description/EasyVIPERObservationService.wsdl}
h1. EasyVIPER auto-generated documentation from WSDL
{wsdl:url=http://resources.petalslink.org/research/dev/experimental/easyviper/services/extended-service-observation/src/main/resources/description/EasyVIPERObservationService.wsdl}