{maturity:experimental}
{section}
{column}
[!download.png!|Binaries]
EasierBSM (for Business Service Monitoring) is a framework able to monitor services deployed on a insfractucture of services such as [EasyESB |easyesb:EASYESB - Open source Lightweight Services Bus] or [PEtALS-DSB|petalsdsb:PetalsDSB Overview].
It is also able to manage the agreements negociated between clients and providers.
EasierBSM is composed of three main components:
- The *{_}Data Collector{_}* is in charge of collect all reports sent by the service infrastructure such as [EasyESB |easyesb:EASYESB - Open source Lightweight Services Bus] or [PEtALS-DSB|petalsdsb:PetalsDSB Overview].
- The *{_}WSDM Monitoring{_}* create a WSDM non functional endpoint when a functional endpoint is created on the service infrastructure. It is possible to subscribe on each WSDM endpoints to get non functional current properties like the latency for example.
- The *{_}SLA Manager{_}* is able to send alert when a business exchange in the ESB is in violation with the agreement loaded.
{column}
{column:width=300px}
{panel}
\*Related Thematics\* {related-to:thematics}
\*Related Projects\* {related-to:projects}
\*Related Results\* {related-to:results}
{panel}
{column}
{section}
h3. WSDM Monitoring
|| 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). |
h3. SLA Enforcement
|| SLA Example || Description ||
| {center}{flash:file=^SLA.swf|width=600px|height=560px}{show-to}{center} | The video shows the mechanism of EasierBSM when the SLA manager component is activated and configured. It means a BSM client loaded an agreement with SLAs dedicated to the service the provider endpoint provides. \\
In this case, reports sent (while a business exchange occurs) are dispatched by the data-collector to the SLA manager that checks potential SLA violations. \\
In this example, the latency violation is checked, by computing the difference between the timestamp values of T1T2 report and T3T4 report. \\
The result is bigger than expected in the SLA, and an alert is then sent to the governance tool. |
EasierBSM is composed of several modules and under modules:
* *{+}Services{+}*:
** *{_}ws-binding-rawreport{_}*: proposes a WSDL description providing the basic operation to get a raw report.
** *{_}ws-binding-wsdm{_}*: proposes a WSDL description providing the basic operation exposed by a monitoring WSDM endpoint.
** *{_}ws-binding-wsdmadmin{_}*: proposes a WSDL description providing the basic operation to administrate wsdm-monitoring framework.
** *{_}ws-binding-wsdmadmin-client{_}*: provide a client able to invoke administration operation of wsdm-monitoring framework.
** *{_}ws-binding-slamanager{_}*: proposes a WSDL description providing the basic operation to administrate sla-manager framework.
* *{+}Interceptors{+}*:
** *{_}wsdm-interceptor{_}*: interceptor to add to EasyESB. It allows EasyESB to send raw report to EasierBSM when functional endpoint is created or requested.
* *{+}Frameworks{+}*:
** *_[wsdm-monitoring|easierbsm:WSDM-Monitoring]_*: WSDM Monitoring framework. Allow to create and manage WSDM enpdoints
** *_[sla-manager|easierbsm:SLA-Manager]_*: SLA Manager framework. Allow to load and verify WS-Agreement.
** *_[data-collector|easierbsm:Data-Collector]_*: Data Collector framework. Allow to dispatch raw report received fron functionnal bus to corresponding WSDM endpoint and SLA manager service.
* *{+}Distribution{+}*:
** *{_}bsm-distribution{_}*: distribution containing data-collector, sla-manager and wsdm-monitoring framework.
If you want know how to use {report-info:page:space > space:name} library, please consult the list of [How-tos|How-tos].
If you have any questions, please use the \[{report-info:page:space > space:name} contact form\|Contact\].
[Here|^EasierBSM_cookbook.pdf], you can download a cookbook written by Mohamed Zouari (LAAS-CNRS). Thanks for this contribution.
{section}
{column}
[!download.png!|Binaries]
EasierBSM (for Business Service Monitoring) is a framework able to monitor services deployed on a insfractucture of services such as [EasyESB |easyesb:EASYESB - Open source Lightweight Services Bus] or [PEtALS-DSB|petalsdsb:PetalsDSB Overview].
It is also able to manage the agreements negociated between clients and providers.
EasierBSM is composed of three main components:
- The *{_}Data Collector{_}* is in charge of collect all reports sent by the service infrastructure such as [EasyESB |easyesb:EASYESB - Open source Lightweight Services Bus] or [PEtALS-DSB|petalsdsb:PetalsDSB Overview].
- The *{_}WSDM Monitoring{_}* create a WSDM non functional endpoint when a functional endpoint is created on the service infrastructure. It is possible to subscribe on each WSDM endpoints to get non functional current properties like the latency for example.
- The *{_}SLA Manager{_}* is able to send alert when a business exchange in the ESB is in violation with the agreement loaded.
{column}
{column:width=300px}
{panel}
\*Related Thematics\* {related-to:thematics}
\*Related Projects\* {related-to:projects}
\*Related Results\* {related-to:results}
{panel}
{column}
{section}
h3. WSDM Monitoring
|| 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). |
h3. SLA Enforcement
|| SLA Example || Description ||
| {center}{flash:file=^SLA.swf|width=600px|height=560px}{show-to}{center} | The video shows the mechanism of EasierBSM when the SLA manager component is activated and configured. It means a BSM client loaded an agreement with SLAs dedicated to the service the provider endpoint provides. \\
In this case, reports sent (while a business exchange occurs) are dispatched by the data-collector to the SLA manager that checks potential SLA violations. \\
In this example, the latency violation is checked, by computing the difference between the timestamp values of T1T2 report and T3T4 report. \\
The result is bigger than expected in the SLA, and an alert is then sent to the governance tool. |
EasierBSM is composed of several modules and under modules:
* *{+}Services{+}*:
** *{_}ws-binding-rawreport{_}*: proposes a WSDL description providing the basic operation to get a raw report.
** *{_}ws-binding-wsdm{_}*: proposes a WSDL description providing the basic operation exposed by a monitoring WSDM endpoint.
** *{_}ws-binding-wsdmadmin{_}*: proposes a WSDL description providing the basic operation to administrate wsdm-monitoring framework.
** *{_}ws-binding-wsdmadmin-client{_}*: provide a client able to invoke administration operation of wsdm-monitoring framework.
** *{_}ws-binding-slamanager{_}*: proposes a WSDL description providing the basic operation to administrate sla-manager framework.
* *{+}Interceptors{+}*:
** *{_}wsdm-interceptor{_}*: interceptor to add to EasyESB. It allows EasyESB to send raw report to EasierBSM when functional endpoint is created or requested.
* *{+}Frameworks{+}*:
** *_[wsdm-monitoring|easierbsm:WSDM-Monitoring]_*: WSDM Monitoring framework. Allow to create and manage WSDM enpdoints
** *_[sla-manager|easierbsm:SLA-Manager]_*: SLA Manager framework. Allow to load and verify WS-Agreement.
** *_[data-collector|easierbsm:Data-Collector]_*: Data Collector framework. Allow to dispatch raw report received fron functionnal bus to corresponding WSDM endpoint and SLA manager service.
* *{+}Distribution{+}*:
** *{_}bsm-distribution{_}*: distribution containing data-collector, sla-manager and wsdm-monitoring framework.
If you want know how to use {report-info:page:space > space:name} library, please consult the list of [How-tos|How-tos].
If you have any questions, please use the \[{report-info:page:space > space:name} contact form\|Contact\].
[Here|^EasierBSM_cookbook.pdf], you can download a cookbook written by Mohamed Zouari (LAAS-CNRS). Thanks for this contribution.