SAP Solution Manager 7.2 · User Experience Monitoring

What happens at each of the four activation steps (Steps 3–6) for UX monitoring?

  • Step 3 — Script Management — upload + assign to a remote robot/diagnostics agent (leave Hostname blank when installing the agent so you can rename by location; the host must have the apps the script uses, e.g. GUI/IE).
  • Step 4 — Monitoring — edit deployed scripts, set execution frequency.
  • Step 5 — Alerting — performance + availability thresholds + notification.
  • Step 6 — Reporting — SLA thresholds for a management history view.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in User Experience Monitoring

Which applications can the EEM HTTP script recorder record steps in?
Why should you record a SAP GUI script before recording an HTTP script in SAP Solution Manager?
What are the rules for recording a SAP GUI script for UX monitoring, and what profile parameter must be set?
What is User Experience Monitoring best at, and how does it end the finger-pointing between teams?
What five views does the UX monitoring dashboard offer, and what does enabling tracing add?
How do you set up a UX monitoring scenario, and why must the chosen business process be read-only?