Service Level Management
| Retired Content |
|---|
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The AmberPoint SMS Service Level Manager provides visibility into specific performance and availability issues within enterprise-level SOA-based systems. It instruments and tracks the metrics for each BizTalk receive location and send port. This provides real-time health and status indication, in addition to ongoing performance characterization of these components. Figure 1 shows the display of the metrics associated with a receive location.
.png "Ff648931.5c3ccc10-066e-4744-8c4a-52548720e044(en-us,PandP.10).png")
Figure 1
The metrics associated with a receive location
AmberPoint run-time analytics allow users to set thresholds and send alerts when a system crosses a critical event threshold, including compliance warnings events, compliance violations events, and a subsequent return to compliance. Figure 2 shows the display where users configure service level agreements and view alerts generated for this service level agreement.
.png "Ff648931.6ee98208-395a-4af7-9ac7-29972889c7e5(en-us,PandP.10).png")
Figure 2
The screens to configure a service level agreement and view alerts
You can establish performance targets within the Service Level Manager. The software then tracks individual messages, messages from a specific user, or messages from groups of users, to measure performance against these targets.
You can also configure logging policies that instruct AmberPoint SMS to dynamically collect and inspect message context and data passing through BizTalk Server, as shown in Figure 3. You can then use these logs for “on-the-fly” troubleshooting, for technical analysis of problems, and for archiving to comply with industry-specific regulations.
.png "Ff648931.c65c67f8-f362-47ea-9254-1b09461f55a9(en-us,PandP.10).png")
Figure 3
The log file for BizTalk service messages