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:
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
Tab Page | Entry |
---|---|
Address |
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. |
Roles/Profiles |
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. |
Input Field | Entry |
---|---|
RFC Destination |
Enter any name for the RFC destination. |
Connection Type |
Enter 3 for Connection to ABAP System. |
Description |
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. |
Logon/Security |
Specify the logon data of the ALERT user created above. Ensure that you specify the client in which you created the user. |
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.
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.
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).
<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.
Example:
http://myServer.sap-ag.de:1080/sap/bc/bsp/sap/alertinbox
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.
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.
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).
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.