General Prerequisites

The following prerequisites apply for central monitoring (see also SAP Note 768456):

?     The central monitoring server must be defined in the exchange profile

The instance parameter icm/host_name_full needs to be specified with a fully-qualified host name (see also SAP Note 654982).

The following properties need to be set in the exchange profile. They define the SAP NetWeaver AS that provides the required CCMS monitor, PMI server, and Alert server.


Specify the same fully-qualified host name as for instance parameter icm/host_name_full.




Specify the port of the ABAP Web server, not the J2EE port.

?     The technical user for the Runtime Workbench must be defined on all PI components

The technical user for the Runtime Workbench (PIRWBUSER) as defined in the exchange profile needs to be available on all PI components that are to be monitored centrally. This service user is defined by the following properties, which are initially set during installation:




?     The ITS plug-in must run on the Integration Server and the central monitoring server

To allow navigation from the Runtime Workbench to ABAP monitoring transactions, for example to RZ20, the ITS plug-in needs to run on the Integration Server and on the central monitoring server.

Use transaction SICF to check whether the ITS service is activated. You may also have to set profile parameter em/global_area_mb to 128 to allow proper ITS operation.

?     The required SICF services must be activated

In addition to ITS, additional SICF services have to be activated on the central monitoring server in order to allow proper operation of end-to-end monitoring and alerting. You activate the required services by executing the report RSXMB_ACTIVATE_ICF_SERVICES (see also SAP Note 517484).

Alternatively, you can manually activate the services listed below by using transaction SICF.

SICF services to be activated


Path to SICF service

ITS plugin


End-to-end monitoring




















?     The content of the System Landscape Directory (SLD) must be consistent

The Runtime Workbench and other services, for example the directory cache refresh, read component and addressing information from the SLD. There are two complementary ways to provide the SLD with PI-specific content:

0     Manually

You define business systems by using the Business Landscape UI of the SLD. Before you do this, the technical systems need to be described in the SLD.

If SLD bridges are configured, the technical systems register themselves automatically with the SLD.

0     Automatically

PI components register themselves with the SLD as soon as they are started up. This type of self-registration does not require SLD bridges.