This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
WebSphere Business Monitor(analyst, architect, administrator)
Model
Services
Events
Objective: Exploit SLAs in BPM life cycle
Modelling
Development
Execution
Monitoring
Adapt to changing conditions to achieve the goals with minimal development and administrative effort
SimplicityAn analyst can specify goals without detailed knowledge of the implementation technologies
FlexibilityThe requirements and implementation technologies can be independently updated
End-to-end specificationRequirements captured in the tools can be enforced and monitored throughout the development cycle
Adaptive efficiencyThe system can allocate resources to meet changing requirements
Layer SLA Metric Example
Business process
Cost Cost of search service < $0.02 per use
Fidelity/quality/utility Map resolution > 300x300
Trust/reputation Only use trusted payment service
Deployment/ Operations
Service time Execution time < 3s
Throughput Throughput > 100/min
Availability Uptime > 99.9%
Load balance Server utilization delta < 10%
Network Latency Service RTT < 100ms
Bandwidth Max bandwidth < 3Mbps
Jitter Delay jitter < 10ms
Service Level AgreementsSLAs are a contract between service consumers and providers that specifies the expected behaviour of each party and the penalties of
violating the contract
SLAs specify business goals declaratively
SLA
Optim.criteria
Runtime Uses of SLAs
A B C D
p
q
Web service Task agent
2
1b service time < 1s
ESB
A,B
D
1a
C
service time < 2s
Dynamic service selectionDiscover services with capabilities that satisfy goals.
Distributed MonitoringOnly monitor the business events related to goals.Treat monitoring as a process.Feed back measurements to support runtime adaptations.
Distributed executionFine-grained allocation of process to available resources.Move portions of process to strategic locations.
ESB adaptationReconfigure the ESB topology to satisfy goals.
M
M
M
Process Execution ArchitecturesCentralized One execution engine May not scale Central point of failure