|| WSDM example || Description ||
| {center}{flash:file=^WSDM.swf|width=600px|height=560px}{show-to}{center} | The video shows an exchange between a client and a service provider, monitored by the EasierBSM bus. In a first time, a service endpoint is deployed into the bus. A corresponding non-functional endpoint is automatically generated in EasierBSM thanks to BSM interceptors. \\
In a second time, a monitoring client (a governance tool for instance, such as [EasierGOV|easiergov:EasierGov - SOA Governance Tool]) subscribes on this endpoint. \\
Then at runtime:
# The client sends its request. It is intercepted when coming in the bus: it corresponds to T1 timestamp and a first report is created. Then the message goes out of the bus (T2 timestamp) and a second report is created. At this moment, a first notification message containing these 2 reports is sent to the EasierBSM, and more precisely in its Data-collector component. This data-collector is in charge to forward the message to the corresponding non functional endpoint.
# In a same way, when the service answers to the client, 2 new reports are created at timestamps T3 (when the response enters into the bus) and T4 (when it goes out of the bus). These 2 last reports are sent to the EasierBSM _via_ another notification message, and current Quality of Service values are updated and sent to the monitoring consumer(s). |
| {center}{flash:file=^WSDM.swf|width=600px|height=560px}{show-to}{center} | The video shows an exchange between a client and a service provider, monitored by the EasierBSM bus. In a first time, a service endpoint is deployed into the bus. A corresponding non-functional endpoint is automatically generated in EasierBSM thanks to BSM interceptors. \\
In a second time, a monitoring client (a governance tool for instance, such as [EasierGOV|easiergov:EasierGov - SOA Governance Tool]) subscribes on this endpoint. \\
Then at runtime:
# The client sends its request. It is intercepted when coming in the bus: it corresponds to T1 timestamp and a first report is created. Then the message goes out of the bus (T2 timestamp) and a second report is created. At this moment, a first notification message containing these 2 reports is sent to the EasierBSM, and more precisely in its Data-collector component. This data-collector is in charge to forward the message to the corresponding non functional endpoint.
# In a same way, when the service answers to the client, 2 new reports are created at timestamps T3 (when the response enters into the bus) and T4 (when it goes out of the bus). These 2 last reports are sent to the EasierBSM _via_ another notification message, and current Quality of Service values are updated and sent to the monitoring consumer(s). |