Alert Configuration

Use

You use the alert configuration to have the system inform you of errors during message processing. You can receive the alert by e-mail, fax, or SMS. In each case. you would also find the alert in your alert inbox .

Prerequisites

You have fulfilled the prerequisites and performed the steps listed in Alert Notification Step-by-Step so that you can proceed with the alert configuration settings.

If you want to use the message-based alerting, make sure that you adapt the corresponding parameters (alerting.target as described below) in all involved runtime engines (Central Adapter Engine and Non-Central Adapter Engine or Integration Engines) as follows:

Use transaction SXMB_ADM to configure the Integration Engine.
To configure the Advanced Adapter Engine, choose SAP NetWeaver Administrator Configuration Infrastructure JAVA System Properties Services: XPI Service: AF Core.
Note that the alerting parameters of the XPI Service: AF Core service are not modifiable online. If you change their value, make sure you restart the system for the changes to take effect.

Installation Steps for the Integration Engine

The following configuration steps are only relevant, if you have ABAP proxy systems in your PI landscape.

Start the Integration Engine Administration transaction (transaction code SXMB_ADM).
Choose Integration Engine Configuration
Specify the runtime engine that you want to configure as the Alert Engine (in the field Corresponding Integ. Server)
Select the change mode.
Use the parameter ALERTING_IS_ACTIVE, to switch on alerting for this runtime engine.
Add the parameter alerting.target and set one of the following values:
- Set 0, if you want to use the "classic" message-based alerting.
- Set 1 to switch on component-based message alerting.

Installation Steps for the Advanced Adapter Engine

Start the SAP NetWeaver Administrator.
Specify the following information in your browser: http://[host]:[port]/nwa
Choose Configuration Infrastructure JAVA System Properties XPI Services: AF Core and choose the Services tab.
Set the value of the service property alerting.isActive (value true).
Set one of the following values of the alerting.target service property:
- Set 1 to switch on component-based message alerting.
- Set 0 to use the "classic" message-based alerting.
  Note that if you want to use this option for a new single-stack installation, you need to follow the steps described in the Message Alerting for SAP PI Advanced Adapter Engine Extended article: Message Alerting for SAP PI Advanced Adapter Engine Extended.
Restart the system for the changes to take effect.

Process

You can access the alert configuration tool in one of the following ways:

Open a browser and go to http://[host]:[port]/rwb to access Runtime Workbench. Then choose Alert Configuration .
Open a browser and go to http://[host]:[port]/pimon to access the Process Integration tools. Then choose Configuration and Administration Common Alert Rules.

Note that you can do this only when the system is configured to use the Alert Framework mechanism. In case the system is configured to use the new component-based message alerting mechanism you cannot use this approach to access the alert configuration tool.

To configure your alerts, proceed as follows:

Create the alert categories that you want to use in your alert rules.
Create the alert rules in which you want to use your alert categories.

The following options are also available:

Using various properties of the XPI Service: AF CORE , you can also control the connection of alerts from the Adapter Framework to the central monitoring server.
Alerts from the Integration Engine are sent using the RFC destination CentralMonitoringServer-XIAlerts to the central monitoring server.

This destination is created automatically as soon as the first alert is sent from the Integration Engine. The required technical settings and logon information are read from the exchange profile.

Caution

If you use Message Based Monitoring in the application system, the destination is not created automatically, as the exchange profile does not exist in the application system. In this case, you must create the destination CentralMonitoringServer-XIAlerts manually, using the transaction SM59 , destination type: 3, with the technical user PIRWBUSER .If you use Component Based Monitoring in the application system, you must create the destination CENTRALMONITORINGSERVER--XIAALERTS.

Only one of these destinations should be defined and active for alerting !

Note

If you keep the corresponding parameters in the exchange profile unchanged, then the destination is not updated automatically. You can then either adapt or delete the destination manually. If you delete the destination then it is automatically re-created by the Integration Engine with the next alert.
You can configure a connection to CCMS and schedule the periodic transfer of alerts to CCMS.

Once you have configured the connection to CCMS, choose Show CCMS Connection , select a period, and start the periodic transfer.

A background job is scheduled that collects all unprocessed alerts and forwards the data to CCMS. You can also stop this job.

The transferred data is displayed in a special CCMS Monitor .
You can use the report SXMSALERT_LOGREADER to display log information for alerts that were reported by PI components. The report also shows whether an alert rule was found or not.