Show TOC

 Example Configuration: Forwarding Alerts to the ALMLocate this document in the navigation structure


This procedure shows as an example the configuration steps that you must perform to forward alerts to Alert Management. In this example, you want to assign different alert categories to two monitoring areas:

  • An alert category CCMS CPU is to be created in the ALM for alerts in nodes that belong to the monitoring object CPU.
  • An alert category CCMS DIALOG is to be created in the ALM for alerts of the MTE class R3DialogResponseTime (average response time of the dialog service).

Since the alert category is transferred as a parameter of the method definition for the auto-reaction method CCMS_Send_Alert_to_ALM, you must therefore create two different method definitions from the template, which you can then assign to the relevant nodes.


For a general description of this process and important prerequisites, see Forwarding Alerts to Alert Management (ALM).


Proceed as follows to display CCMS alerts using ALM. CEN stands for the central monitoring system.

Creating an RFC Connection Between the CCMS and the ALM

  1. You require a user for the RFC connection between client 0 of the central monitoring system (CEN) and the work client of the ALM system. To provide this, start user maintenance in the work client of the ALM system by calling transaction SU01.
  2. Create the communication user ALERT, and enter the following parameters:
    Tab Page Entry


    Enter any last name.

    E-Mail/ Other communication

    Specify an e-mail address. This is to be the sender's address of the e-mails with which you are informed of inbound alerts by the ALM.

    You can also use Other Communication to specify the addresses of other types of communication (fax, SMS).

    Logon Data

    Enter any initial password, and repeat your entry.


    Assign the role SAP_BC_ALM_ALERT_USER to the user.

    You can also create the corresponding role. The authorization objects for sending alerts are S_OC_SEND and S_RFC.

  3. Save your entries.
  4. In client 0 of the central monitoring system (CEN), create an RFC connection to the work client of the ALM system. To do this, start Display and Maintain RFC Destinations by calling transaction SM59.
  5. Choose the Create button and then enter the following parameters:
    Input Field Entry

    RFC Destination

    Enter any name for the RFC destination.

    Connection Type

    Enter 3 for Connection to ABAP System.


    Enter any description for the RFC destination; confirm your entries up to now by choosing Enter ().

    Technical Settings

    Specify the desired server or the desired logon group of the ALM system.


    Specify the logon data of the ALERT user created above. Ensure that you specify the client in which you created the user.

  6. Save your entries.
  7. Make this RFC destination known as the RFC destination of the Alert Management Systems in client 0 of CEN. To do this, start transaction SALRT1, and enter the destination created above in the input field RFC Dest.of Alert Server.

Configuring Alert Management

You want to forward alerts from the areas Dialog and CPU to the ALM in the context of monitoring. Since each area is overseen by different employees, you require two different alert categories in the ALM. You want to specify a fixed user as the recipient for both categories. In addition, an escalation user is to be informed after 120 minutes.

  1. Change the alert categories, by calling transaction ALRTCATDEF in the work client of the ALM system.
  2. Switch to change mode by choosing the Display/Change button .
  3. You are on the Change Alert Categories screen. Since all alerts from the monitoring infrastructure have the alert classification CCMS ALERTS in the ALM, choose the classification by double-clicking it.
  4. To create a new alert category, select the existing category CCMS TEMPLATE as a template in the table in the upper right, and choose Copy Alert Category (). Enter CCMS CPU as the name of the new category. Create the category CCMS DIALOG in the same way.
  5. Both new alert categories are now displayed in the list of existing categories. To start the method, choose the node by double-clicking it. Activate the indicator Escalation Active in the Properties group box and enter any Escalation Recipient and a Tolerance Time in Minutes.

    The report RSALERTPROC must be scheduled as a job for the relevant classifications and categories so that escalation can be performed. The Escalate option must be selected in the report for this. If the report is not executed as an escalation job, the escalation option is available for selection on the Properties tab page in the configuration transaction ALRTCATDEF, but the alert is not escalated.

    The report is also used for the reorganization and multiple sending of unconfirmed alerts. It may, therefore, be useful to schedule multiple jobs with different variants of the report RSALERTPROC, depending on their function. For example, you could schedule a job for the escalation every five minutes, and another for the reorganization every weekend.

  6. To set fixed recipients for the selected category, choose the Fixed Recipients () button, and then choose New Entries on the screen that appears after this, Change "Fixed Alert Recipients": Overview. Specify fixed recipients for both new categories.

    Note that if you are using the external communication methods e-mail, SMS, and fax, all recipients and the RFC user must have a valid communication method, which is maintained in SAPconnect, in user maintenance (transaction SU01).

  7. Ensure that the Dynamic Text indicator is activated in the Properties of the alert categories, since the text for the alert is determined not in the ALM, but rather in the CCMS.
  8. If alerts are to be confirmed using the external communication methods e-mail and SMS, you must set the sender for the alert information. To do this, choose Settings → Configuration in the menu of the transaction ALRTCATDEF. The View: Change "Alerts Configuration": Detail screen appears. Enter the user ALERTin the Inbound Processing group box. This means that ALERT is the sender of the alert information.
  9. Save your entries.
  10. In Alert Management, you can determine the times at which you want to be informed about an alert, and whether external communication methods (mail, SMS, fax) are also to be used. This is done in a BSP application, which you can call using transaction ALRTINBOX → Personalization or with the following URL:

    <Prot>://<host name>:<Port>/sap/bc/bsp/sap/alertinbox

    The protocol Prot is either http or https. The host name is the name of the application server on which the BSP application is to be executed, including the domain and extension.


  11. A screen on which you can specify the desired delivery method depending on the time appears. By default, alerts that occur are sent to the recipient, irrespective of time, in the UWL, application, or Alert Inbox and are also sent by e-mail, if this external communication method is configured. You also have the following options:
    • Choose the time-independent delivery radio button and, if applicable, the additional external delivery types (Mail, SMS, Fax).

      External communication methods must be configured in SAPconnect. The communication data, such as e-mail addresses, must also be maintained in the user settings for the recipient and the RFC user in transaction SU01.

    • Choose the time-dependent delivery radio button and, if applicable, the additional external delivery types (Mail, SMS, Fax). You can specify a factory calendar and the type of delivery with the corresponding time periods.
  12. You can also specify a substitute.
  13. Save your entries.

Configuring SAPconnect

If alerts are to be sent to users using the external communication methods e-mail, SMS, and fax, these must be configured in SAPconnect (transaction SCOT). The communication data, such as e-mail addresses, must also be maintained in the user settings for the recipient and the RFC user in transaction SU01.

This configuration is performed in the work client of the ALM system.

Tailoring the Auto-Reaction Method

Since you want to assign two different alert categories to different nodes, first copy the original method CCMS_Send_Alert_to_ALMtwice, so that you can then set the CATEGORY parameter of the two copies to the value CCMS CPU or CCMS DIALOG.

  1. In the work client of CEN, start the Customizing transaction for the monitoring architecture by starting transaction RZ21.
  2. In the Methods group box, select Method Definitions and choose Display Overview.
  3. Select the method CCMS_Send_Alert_to_ALM and choose Copy (). Specify ZCCMS_Send_Alert_to_ALM_CPU as the name. Create a second copy with the name ZCCMS_Send_Alert_to_ALM_DIALOG in the same way.
  4. In the list, select the new method definition ZCCMS_Send_Alert_to_ALM_CPU, and choose the Edit Data button (). Switch to change mode by choosing Display «Change ().
  5. Switch to the Execution tab page. Ensure that the Any Server radio button is activated in the Execute Method group box for nodes that are supplied with values by the host agent (more information: Infrastructure of the NetWeaver Management Agents).
  6. Switch to the Parameters tab page. Specify the parameter value CCMS CPU for the parameter CATEGORY.
  7. Switch to the Release tab page, and release the method as an auto-reaction method. Save your entries.
  8. Adjust the method definition ZCCMS_Send_Alert_to_ALM_DIALOG in the same way; choose the parameter value CCMS DIALOG for the CATEGORY parameter here. Save your entries.

Assigning the Method as a Local Auto-Reaction Method

In this example, you want to assign the created method definitions to the monitoring object CPU and the MTE class R3DialogResponseTime (see Assigning Methods to MTE Classes or Individual MTEs).

  1. In the work client of CEN, start the Alert Monitor by calling transaction RZ20.
  2. In the monitor list, expand the SAP CCMS Monitor Templates monitor set, and start the Entire System monitor by double-clicking it.
  3. Expand the subtree of any application server and select the subtree Operating System → CPU there. Choose Properties. In this way, you set properties for the monitoring object CPU, which are inherited by all monitoring attributes of this object that do not have their own method assignment.
  4. The Monitoring: Properties and Methods screen appears. Select the name of the MTE Class (CPU) in the header data of the screen by double-clicking it. In this way, you change the properties of the MTE class CPU, not just the properties of the subtree of the selected server.
  5. The Monitoring: Methods screen appears. Switch to change mode by choosing Display «Change ().
  6. In the Auto-Reaction Method group box, choose the Method Name radio button and enter ZCCMS_Send_Alert_to_ALM_CPU in the associated field. Save your entries.
  7. Set the method assignment for the MTE class R3DialogResponseTime, to which you assign the auto-reaction method ZCCMS_Send_Alert_to_ALM_DIALOG, in the same way. There are nodes of this MTE class in every subtree of an application server under R3Services → Dialog → Response Time.

You have set up the forwarding of selected alerts (CPU, dialog response time) to Alert Management. If an alert occurs in one of the assigned nodes of the alert monitor, the specified recipients are immediately informed in the Alert Inbox (transaction ALRTINBOX) using the ALM. If escalation is activated and the alerts are not confirmed within a defined period of time, the escalation users receive the alerts.