|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (2)
View Page History
|| Example || Description ||
| {center}{flash:file=^connexionManagerEasierGOV.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. |
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. |
| {center}{flash:file=^connexionManagerEasierGOV.swf|width=600px|height=560px}{show-to}{center} | |
| {center}{flash:file=^connexionManagerEasierGOV_2.swf|width=600px|height=560px}{show-to}{center} | |
| {center}{flash:file=^connexionManagerEasierGOV_2.swf|width=600px|height=560px}{show-to}{center} | |