Show TOC

Procedure documentationConfiguring Alert Notifications Locate this document in the navigation structure


You specify who is to be notified when alerts are raised.


  • You have specified meaningful threshold values for raising alerts, and the system is running normally. For more information, see Specify Alert Thresholds.

  • You have administrator authorization.

  • You are currently performing the Alerting step of the guided procedure for setting up End User Experience Monitoring in the SAP Solution Manager: Configuration work center.


  1. To configure the settings globally or for individual EEMon scripts, choose the Global tab, or choose the Scripts tab and select the relevant EEMon script.

  2. Choose Edit. You have the following options:

    • On the Incidents tab, specify whether support messages are to be created:

      1. Set the Auto-Incidents flag to specify that a support message is automatically created if a script fails and an alert is raised.

      2. In the Assigned Support Component field, specify the component to which support messages are to be assigned.

      3. In the CRM Transaction Type field, specify the support process for which support messages are to be created.

      4. The field Incident Confirmation Closes Alert specifies that when a support message is confirmed, the relevant alert is closed and removed from the list in the alert inbox.

    • On the Notifications tab, specify who is to be informed by e-mail or SMS about alerts.

      1. The field Auto-Notifications specifies whether automatic e-Mail or SMS notifications are to be sent when an alert is raised.

      2. Choose Add to add a recipient list to specify who is to be notified.

      3. Optional: Choose Maintain Recipients to create or change a recipient list.

      For more information, see Alert Inbox.

    • On the Event Rule tab, you specify globally for all locations, how and under what conditions availability and performance alerts are to be generated:

      • Worst Case: An EEMon script raises an alert if any step in an EEMon script fails.

      • Best Case: An EEMon script does not raise an alert as long as at least one step can be performed in an EEMon script.

        Example Example

        You check the availability of an internet portal. As long as you can call at least one instance, the portal is considered technically available.

        End of the example.

      For more information about the propagation rules you can use, see the expandable help for the tab.