0% found this document useful (0 votes)

45 views

Configuring The Monitoring Architecture

This document provides instructions for configuring the monitoring architecture in SAP systems. It describes setting up a central monitoring system (CEN) and configuring it to monitor ABAP instances, Java instances, and other SAP NetWeaver components. The steps include creating a CSMREG user, activating background dispatching and the Internet Communication Manager in the CEN, and preparing to register CCMS agents for monitoring remote systems.

Uploaded by

Charith Weerasekara

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

45 views

Configuring The Monitoring Architecture

Uploaded by

Charith Weerasekara

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 38

5/30/2022

Con guring the Monitoring Architecture

Generated on: 2022-05-30 17:58:43 GMT+0000

| 2021 FPS02

PUBLIC

Original content: https://help.sap.com/docs/ABAP_PLATFORM_NEW/cc3cb88824a44bd09e8743d64539419c?locale=en-

US&state=PRODUCTION&version=202110.002

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the oﬃcial SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
5/30/2022

Con guring the Monitoring Architecture

Purpose
The monitoring of a system landscape is a complex task of signi cant importance for every company that operates one or more
SAP systems. The complexity increases with every additional system, component, or extension.

With the monitoring architecture of the Computing Center Management System (CCMS), SAP provides a exible and
universally-usable infrastructure with which you can centrally monitor your entire IT landscape and which reports problems
quickly and reliably.

The monitoring architecture is delivered free of cost with every SAP Web Application Server. The architecture runs on every SAP
Web Application Server and can easily be extended to include additional SAP and non-SAP components.

The concept of the monitoring architecture is that all required information is available in a central monitoring system (CEN),
and therefore makes the work of the administrators easier. Problems are displayed as soon as they occur; all log les are also
accessible from a central location, which reduces the time for error identi cation and correction. In this way, the monitoring
architecture enables greater eﬃciency with lower costs.

Additional con guration steps allow advanced technologies such as noti cations, meaning that administrators no longer need
to actively investigate systems for alerts.

This guide outlines the con guration steps required to monitor a system landscape based on SAP NetWeaver 7.0. It is a
prerequisite for this that you have already completed the installation of the corresponding components.

To con gure the monitoring, perform the following processes in the speci ed order, if the relevant components are part of your
system landscape:

Con guring a Central Monitoring System (CEN)

Monitoring: Con guring ABAP Instances

Monitoring: Con guring Java Instances

Monitoring: Con guring Other SAP NetWeaver Components

Con guring Alert Triggering and Alert Reactions

 Note
As of SAP NetWeaver 7.0 EhP2, the Consistency Check of the CCMS Monitoring Infrastructure is available to you. The
associated transactions RZ50, RZ521, and RZ52 provide a variety of functions to check the con guration and runtime
of the CCMS monitoring infrastructure, to display errors, and to correct these automatically. The checks are called
from the central monitoring system (CEN) and include both the CEN itself and the monitored systems.

Con guring a Central Monitoring System (CEN)

Use
The concept of the monitoring architecture assumes that you declare a system in your system landscape to be the central
monitoring system (CEN). The monitoring information for your system landscape is collected in this system and displayed in the
Alert Monitor.

This system should be reserved only for monitoring and system management. In particular, do not use a production system for
this purpose, to avoid unnecessary load on the system. If you are using a separate SAP system, you can always maintain this
system at the most up-to-date status with regard to releases or Support Packages without any problems, meaning that you can

This is custom documentation. For more information, please visit the SAP Help Portal 2
5/30/2022
always pro t from the newest developments in the areas of monitoring and system management. The system does not require
any special and expensive hardware features, but should have at least a release status of SAP Web AS 6.20, or preferably SAP
Web AS 6.40.

This process outlines the steps that you must perform in the system that you want to use as CEN. For exact descriptions of the
steps, see the corresponding linked sections of the documentation.

Prerequisites
This process is part of Con guring the Monitoring Architecture. To completely con gure landscape-wide monitoring, you must
also perform the other processes.

Process
Perform the following steps in CEN:

Creating the CSMREG User

You require a communication user with particular, restricted authorizations in all ABAP systems in your system
landscape for communication between CEN, the monitored systems, and CCMS agents (see Creating the CSMREG
User).

To create the user, start transaction RZ21, choose Technical Infrastructure Con gure Central System Create CSMREG
User , and enter any password for this user.

Activate Background Dispatching

Some of the monitoring data of the monitoring architecture is collected using data collection methods, which are
periodically executed as jobs. So that these methods are started correctly, background dispatching must be activated in
all of the ABAP systems of your system landscape (see Activating and Deactivating Method Execution).

 Note
In each case, activate background dispatching in client 000.

To activate background dispatching, start transaction RZ21, and choose Technical Infrastructure Local Method
Execution Activate Background Dispatching .

Activate the Internet Communication Manager (ICM)

The monitoring architecture uses the Generic Request and Message Generator for availability monitoring of Web
components. This requires that ICM is con gured and activated in all ABAP systems of your system landscape (see
Administration of the ICM).

Activate Central System Dispatching

Auto-reaction methods are part of the monitoring architecture that are started automatically in the case of an alert. By
default, these methods are executed in the system in which the alert occurs. If these methods are to be started in CEN,
you must activate central system dispatching (see Activating and Deactivating Method Execution).

 Note
In each case, activate central system dispatching in client 000.

To activate central system dispatching, start transaction RZ21, and choose Technical Infrastructure Con gure
Central System Activate Central System Dispatching .

Monitor Remote ABAP Systems

This is custom documentation. For more information, please visit the SAP Help Portal 3
5/30/2022
By default, the monitoring architecture monitors only the local ABAP system. To monitor remote systems, follow the
procedure described in Registering SAP NetWeaver Components and Hosts in CEN.

The following steps are not directly part of con guring the CEN. However, since you only need to perform them once per
monitored system landscape, the steps are listed here:

Prepare the Registration of the CCMS Agents

When con guring monitored systems and components, you will register a CCMS agent with CEN in each case. First
perform the following procedure once, since you require the relevant les (executables for the agents and the CSMCONF
start le) for each agent registration.

To download the required executables for the CCMS agents, proceed as follows:

1. You require the le CCMAGENT.SAR. This archive contains all CCMS agents, including SAPCCMSR, SAPCCM4X,
and SAPCM3X.

2. Download the archive CCMAGENT.SAR. You can nd it in the SAP Software Distribution Center of the SAP
Service Marketplace (http://service.sap.com/swdc ). Log on using your SAP Service Marketplace ID.

3. In the navigation bar, choose: Download Support Packages and Patches Entry by Application Group SAP
NetWeaver SAP NETWEAVER SAP NETWEAVER 04 Entry by Component AS ABAP SAP KERNEL 6.40 32/64-
BIT <operating system> Database Independent .

4. Decompress the archive CCMAGENT.SAR using the SAPCAR tool, which you can nd under Additional
Components in the SAP Software Distribution Center. Use the following command to decompress the les:

sapcar -xvf CCMAGENT_<Version>.SAR

 Note
If you cannot nd the archive for your operating system there, proceed as described in Downloading CCMS
Agents.

During the registration of the agent, you require connection data from the agent to CEN. We recommend that you
generate this data in a CSMCONF le in CEN before the registration. To do this, follow the procedure below:

1. In CEN, call transaction RZ21, and choose Technical Infrastructure Con gure Central System Create
CSMCONF Start File for Agents .

2. Save the le at a location that is centrally available, since you require the le for all agent registrations.

Availability Monitoring with CCMSPING

You can use the availability agent CCMSPING to monitor, above all, the availability of ABAP instances and systems. To do
this, you need to install the agent once on any host of your monitored system landscape and register it with CEN (see
Availability Monitoring with CCMSPING).

For the following monitored SAP NetWeaver components, you also need to make settings in CEN, among other things, in the
context of the monitoring con guration:

SAP Exchange Infrastructure

You need to create a system group called ExchangeInfrastructure_Systems that contains all of your Exchange
Infrastructure systems.

SAP Mobile Infrastructure

In the context of monitoring the SAP Mobile Infrastructure with the CCMS, various jobs are monitored; the monitoring
architecture must be made aware of these jobs.

This is custom documentation. For more information, please visit the SAP Help Portal 4
5/30/2022
Start page Con guring the Monitoring Architecture

Registering SAP NetWeaver Components and Hosts in CEN

Use
To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in
CEN. There are two ways of doing so:

If you are using the SAP NetWeaver Administrator (NWA), we recommend that you con gure the monitored components
using the Con guration Wizard.

If you are using the Alert Monitor, register the desired component in the con guration transaction for the Alert Monitor
(transaction RZ21). This procedure is described here.

Prerequisites
There is a CSMREG user in CEN.

There is also a CSMREG user on the ABAP or double-stack system to be monitored.

If you want to register a host with no SAP NetWeaver components in CEN, install the host agent on that host.

The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0 EhP2.

 Note
You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 EhP1 with CEN using CCMS
agents.

 Note
If you want to centrally monitor any system with a central monitoring system with release SAP NetWeaver 7.0, this
procedure is not applicable. In this case, follow the procedure described in the newest Monitoring Setup Guide for
SAP NetWeaver 7.0 instead. You can obtain the Monitoring Setup Guide at the Internet address
service.sap.com/operationsnw70 in the Monitoring area.

Procedure
1. To monitor an additional system or host, call transaction RZ21.

2. Choose Technical Infrastructure Con gure Central System Create Remote Monitoring Entry .

3. Choose which component type you want to register in CEN.

4. In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.

5. Depending on the type of component to be monitored, enter the following system and connection data for the
component to be monitored:

Type Input Data More Information

ABAP The connection to the monitored system

System ID
is tested with user CSRMREG when you
Double-Stack
Message Server save (or if you choose the button in
the RFC Connections to Remote
Component) group box. The monitored
This is custom documentation. For more information, please visit the SAP Help Portal 5
5/30/2022
Logon Group; the SPACE, which component is only added and the RFC
always exists, is set as the destinations (see below) are only created
default if the test is performed successfully.

Password of CSMREG on the

monitored system

Java
System ID

Message Server

HTTP port of the message

server

TREX You require the user at operating system

System ID
level to execute a con guration script on
Server the TREX host (see TREX
documentation).
Instance number

Register only hosts without SAP

Host Host Name
NetWeaver components here. Ensure that
the host agent is installed on the host.

6. In the Operating System User on the Host of the Monitored System group box, enter the password of an administration
user at operating system level. For an SAP NetWeaver component, this is the user <SysID>adm., for a host, it is
sapadm.

 Note
You require this authentication since the Web service call for registering a component in CEN is protected.

7. Save your entries.

Technical Background

To monitor an ABAP or dual-stack system centrally, the system creates two RFC destinations in that system:

<SysID>_RZ20_COLLECT reads monitoring data for the monitored system; the connection uses the CSMREG
user.

<SysID>_RZ20_ANALYZE is the destination with which you as an administrator can execute an analysis method
in the monitored system. The destination is created without a user, meaning that you need to authenticate
yourself in the monitored system.

A Customizing destination between the CEN and the relevant Java Engine is required, so that you can change the
properties of the monitoring data of the Java Engine (such as threshold values) from the Alert Monitor. This is
automatically created under the name SAP.CCMS.J2EE.<SysID> when adding a Java system, where <SysID> is the
system ID of the Java system to be monitored.

Result
You can now monitor the corresponding with the Alert Monitor or with the NWA. If you are using rule-based monitors for
monitoring, the new system is automatically added to your monitors. Otherwise, add the new system to your monitors or create
a new monitor (see Creating and Changing Monitors).

 Note
This is custom documentation. For more information, please visit the SAP Help Portal 6
5/30/2022
To deregister a component again, call the topology display (see Technical Topology of the Monitoring Architecture).

More Information
Infrastructure of the SAP NetWeaver Management Agents Start Page

Host Agent

Best Procedure for Central Monitoring with CCMS

Use
This section describes the Customizing settings and procedures that have proved themselves in day-to-day operation of CCMS
monitoring, and ensure high performance and reliability.

Process
Planning the Instances of the Central Monitoring System (CEN)

For small to medium-sized landscapes that you want to monitor centrally, we basically recommend that you operate the central
monitoring systme (CEN) with a single instance. This recommendation applies for system landscapes of up to approximately
100 systems. In this case, you avoid potential problems that could arise from distributing the workload across diﬀerent
instances.

If you want to monitor larger system landscapes, design your CEN with multiple instances. We recommend that you assign each
instance one or both of the following tasks:

The instance acts as a communication partner for CCMS agents, that is, you x the registration of the CCMS agents to
this instance. You do this by specifying this instance during the registration and not activating load balancing using logon
groups (more information: Dialog-Free Registration of CCMS Agents).

On these agent instances, activate the central data cache (more information: Setting Up the Central Data Cache).

Fix the context CCMS_Selfmonitoring to one of these instances (refer to the command Fixing on in Monitoring Contexts
in the Topology Display).

The instance is used to monitor availability, that is, you x the corresponding contexts to one of the instances. This
aﬀects the Availability contexts and the contexts for availability monitoring with GRMG. You can obtain a list of GRMG
contexts in the corresponding table column if you call transaction GRMG in CEN.

Fix the speci ed contexts to one of these instances (refer to the command Fixing on in Monitoring Contexts in the
Topology Display).

Once you have assigned the tasks above to instances of CEN, you should also check the workload of the instances, and, if
necessary, move contexts between the two groups until you achieve an equal distribution of the workload.

Optimization of the Instances with which CCMS Agents Are Registered

The instances that are used for communication with CCMS agets, as described above, require a larger roll buﬀer so that the
required data can be read directly from working memory when communicating with the agents, and so that no read and write
operations on the disk are necessary.

To achieve this, increase the instance parameter rdisp/ROLL_SHM. The default value of the parameter is 32768, which
corresponds to a roll buﬀer size of 32768 * 8 KB = 262,144 KB. This value is not suﬃcient for the instances in question.

This is custom documentation. For more information, please visit the SAP Help Portal 7
5/30/2022
In a tuned system, the roll area hit rate should be over 95%; you can check this hit rate in transaction ST02 of the relevant
instance. There is no general speci cation for the value to which you need to increase the instance parameter
rdisp/ROLL_SHM. However, as an initial guideline, we recommend an increase by a factor of ve (163840).

Monitoring: Con guring ABAP Instances

Purpose
To allow the central monitoring system (CEN) to monitor other ABAP systems, you must make various settings in these
systems.

Prerequisites
This process is part of Con guring the Monitoring Architecture. To completely con gure landscape-wide monitoring, you must
also perform the other processes.

Process Flow
Perform the following steps in every monitored ABAP system:

Create the CSMREG User

To create the user, start transaction RZ21, choose Technical Infrastructure → Con gure Central System → Create
CSMREG User, and enter any password for this user.

Activate Background Dispatching

To activate background dispatching, start transaction RZ21, and choose Technical Infrastructure → Local Method
Execution → Activate Background Dispatching.

Activate the Internet Communication Manager (ICM)

Register with CEN

To monitor remote ABAP systems, you need to register the corresponding system in CEN (see Registering SAP
NetWeaver Components and Hosts in CEN).

Con guring the Monitoring Architecture start page

Registering SAP NetWeaver Components and Hosts in CEN

Use

This is custom documentation. For more information, please visit the SAP Help Portal 8
5/30/2022
To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in
CEN. There are two ways of doing so:

If you are using the SAP NetWeaver Administrator (NWA), we recommend that you con gure the monitored components
using the Con guration Wizard.

If you are using the Alert Monitor, register the desired component in the con guration transaction for the Alert Monitor
(transaction RZ21). This procedure is described here.

Prerequisites
There is a CSMREG user in CEN.

There is also a CSMREG user on the ABAP or double-stack system to be monitored.

If you want to register a host with no SAP NetWeaver components in CEN, install the host agent on that host.

The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0 EhP2.

 Note
You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 EhP1 with CEN using CCMS
agents.

Procedure
1. To monitor an additional system or host, call transaction RZ21.

2. Choose Technical Infrastructure Con gure Central System Create Remote Monitoring Entry .

3. Choose which component type you want to register in CEN.

4. In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.

5. Depending on the type of component to be monitored, enter the following system and connection data for the
component to be monitored:

Type Input Data More Information

ABAP The connection to the monitored system

System ID
is tested with user CSRMREG when you
Double-Stack
save (or if you choose the button in
Message Server
the RFC Connections to Remote
Logon Group; the SPACE, which Component) group box. The monitored
always exists, is set as the component is only added and the RFC
default destinations (see below) are only created
if the test is performed successfully.
Password of CSMREG on the
monitored system

Java
System ID

This is custom documentation. For more information, please visit the SAP Help Portal 9
5/30/2022
Message Server

HTTP port of the message

server

TREX You require the user at operating system

System ID
level to execute a con guration script on
the TREX host (see TREX
Server
documentation).
Instance number

Register only hosts without SAP

Host Host Name
NetWeaver components here. Ensure that
the host agent is installed on the host.

 Note
You require this authentication since the Web service call for registering a component in CEN is protected.

7. Save your entries.

Technical Background

To monitor an ABAP or dual-stack system centrally, the system creates two RFC destinations in that system:

<SysID>_RZ20_COLLECT reads monitoring data for the monitored system; the connection uses the CSMREG
user.

 Note
To deregister a component again, call the topology display (see Technical Topology of the Monitoring Architecture).

More Information
Infrastructure of the SAP NetWeaver Management Agents Start Page

Host Agent

This is custom documentation. For more information, please visit the SAP Help Portal 10
5/30/2022

Monitoring: Con guring Java Instances

Purpose
If you use Java instances with release SAP NetWeaver 7.x, you can monitor them centrally with the monitoring architecture. The
corresponding monitoring data is displayed in the Alert Monitor of the central monitoring system (CEN) in the monitor set SAP
J2EE Monitor Templates.

Prerequisites
This process is part of Con guring the Monitoring Architecture. To completely con gure landscape-wide monitoring, you must
also perform the other processes.

Process Flow
Perform the following steps:

Register the Java System in CEN

To do this, follow the procedure described in Registering SAP NetWeaver Components and Hosts in CEN. You only need to
perform this registration once for each monitored system.

Set Up GRMG monitoring of the Java instance

You can use the Generic Request and Message Generator (GRMG) to monitor the availability of technical components
and entire business processes. To do this, de ne the required con guration settings in a GRMG Customizing, which is
transferred to CEN by a CCMS agent. See GRMG Monitoring of SAP NetWeaver Components.

Con guring the Monitoring Architecture start page

Registering SAP NetWeaver Components and Hosts in CEN

Use
To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in
CEN. There are two ways of doing so:

If you are using the SAP NetWeaver Administrator (NWA), we recommend that you con gure the monitored components
using the Con guration Wizard.

If you are using the Alert Monitor, register the desired component in the con guration transaction for the Alert Monitor
(transaction RZ21). This procedure is described here.

Prerequisites
There is a CSMREG user in CEN.

There is also a CSMREG user on the ABAP or double-stack system to be monitored.

If you want to register a host with no SAP NetWeaver components in CEN, install the host agent on that host.

The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0 EhP2.

This is custom documentation. For more information, please visit the SAP Help Portal 11
5/30/2022

 Note
You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 EhP1 with CEN using CCMS
agents.

Procedure
1. To monitor an additional system or host, call transaction RZ21.

2. Choose Technical Infrastructure Con gure Central System Create Remote Monitoring Entry .

3. Choose which component type you want to register in CEN.

4. In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.

5. Depending on the type of component to be monitored, enter the following system and connection data for the
component to be monitored:

Type Input Data More Information

ABAP The connection to the monitored system

System ID is tested with user CSRMREG when you
Double-Stack save (or if you choose the button in
Message Server
the RFC Connections to Remote
Logon Group; the SPACE, which Component) group box. The monitored
always exists, is set as the component is only added and the RFC
default destinations (see below) are only created
if the test is performed successfully.
Password of CSMREG on the
monitored system

Java
System ID

Message Server

HTTP port of the message

server

TREX You require the user at operating system

System ID level to execute a con guration script on
the TREX host (see TREX
Server
documentation).
Instance number

Register only hosts without SAP

Host Host Name NetWeaver components here. Ensure that
the host agent is installed on the host.

This is custom documentation. For more information, please visit the SAP Help Portal 12
5/30/2022
sapadm.

 Note
You require this authentication since the Web service call for registering a component in CEN is protected.

7. Save your entries.

Technical Background

To monitor an ABAP or dual-stack system centrally, the system creates two RFC destinations in that system:

<SysID>_RZ20_COLLECT reads monitoring data for the monitored system; the connection uses the CSMREG
user.

 Note
To deregister a component again, call the topology display (see Technical Topology of the Monitoring Architecture).

More Information
Infrastructure of the SAP NetWeaver Management Agents Start Page

Host Agent

GRMG Monitoring of SAP NetWeaver Components

If the SAP NetWeaver components listed exist in your system landscape, you can use GRMG to monitor them. By following the
links below, you can view information about the associated con guration:

Setting Up GRMG Monitoring of the SAP Business Warehouse

Setting Up GRMG Monitoring of the Exchange Infrastructure

Setting Up GRMG Monitoring of the ICM

This section describes the con guration of the following functional units:

AS Java

Process Monitoring Infrastructure

Adobe Document Services

This is custom documentation. For more information, please visit the SAP Help Portal 13
5/30/2022
Business Communication Broker

Portal Infrastructure

Web Dynpro

To monitor the availability of the speci ed components with GRMG, you need to upload corresponding GRMG customizing les
to the central monitoring system (CEN), enter the required information (such as host and port) for the components there, and
start the scenarios:

1. Call the Internet address http://www.sdn.sap.com/irj/sdn/monitoring, and choose the link Enhancing your Monitoring
Possibilities. There is a section on this page called GRMG Customizing les. Templates for the GRMG customizing les for
the above components are available to you here.

2. Download the desired template by downloading the desired archive and decompressing it.

3. Use a suitable XML editor to edit the downloaded le. You need to change the values of diﬀerent tags, depending on the
monitored component. These tags are indicated in the template with square brackets ([]). These are usually:

<scenstarturl>, in which you usually need to enter the host and port of the monitored component

<scendesc>, in which you usually need to enter the system ID and host of the monitored component

4. In CEN, call transaction GRMG, choose the Upload button, and specify the le that you have just downloaded.

5. Select the scenario that you have just uploaded and choose Edit GRMG Customizing.

6. For the monitored component Portal Infrastructure, you still need to edit the scenario after you have uploaded the le.
Proceed as described in Setting Up GRMG Monitoring of the Portal Infrastructure.

7. To start the availability monitoring, select the corresponding row, and choose Start.

Checking the Entries (Optional)

1. After you have started the scenario, you can nd out from the Scenario Execution Status, whether the scenario was
correctly executed. After the scenario has been executed, there should be a green check mark ( ) here.

2. To view the availability data for the monitored components, call transaction RZ20 in CEN, and start the Availability and
Performance Overview monitor in the SAP CCMS Monitor Templates monitor set. Expand the GRMG-Tested Availability
(Web Components) subtree. The availability of your monitored components is displayed in this tree.

Monitoring: Con guring Other SAP NetWeaver Components

Purpose
SAP NetWeaver components can be monitored by the monitoring architecture. Both the con guration steps required for this
and information about the displayed monitoring data are part of the documentation for the relevant component.

As a basic principle, the operating system collector SAPOSCOL must be running on every host of the monitored system
landscape; for ABAP and Java instances, the installation and start of SAPOSCOL is part of the relevant installation and
start routine of the instance, meaning that you do not have to perform any manual con guration for this.

A SAP NetWeaver management agent must also be installed and registered with the central monitoring system (CEN)
for each monitored software component. To do this, follow the procedure described in Registering SAP NetWeaver
Components and Hosts in CEN.

For additional con guration steps, see the relevant monitored component

Prerequisites
This process is part of Con guring the Monitoring Architecture. To completely con gure landscape-wide monitoring, you must
also perform the other processes.

This is custom documentation. For more information, please visit the SAP Help Portal 14
5/30/2022

Process Flow
To con gure the monitoring of the following components, proceed as described in the respective linked documentation:

TREX

TREX uses the following technologies for monitoring the component:

Availability monitoring with the GRMG

Log le monitoring

Process monitoring

Activity tracing using Distributed Statistics Records

The required con guration steps are described in the TREX documentation.

Portal Infrastructure

The availability of the Portal Infrastructure is monitored using the GRMG. To do this, de ne the required con guration
settings in a GRMG Customizing, which is transferred to CEN by a CCMS agent (see GRMG Monitoring of SAP
NetWeaver Components).

SAP Exchange Infrastructure

The availability of the XI Java components is monitored using the GRMG. To perform the con guration, you must edit an
appropriate template for a GRMG Customizing le and upload it to the CEN. The required con guration steps are
described in the SAP Exchange Infrastructure documentation.

SAP Business Warehouse

The availability of the following BW components is monitored using the GRMG (see Setting Up GRMG Monitoring of the
SAP Business Warehouse and SAP Note 706290):

UDC Enterprise Beans

SAP BI Java connectors

Metamodel Repository

RFC destination for the BW system

SAP Mobile Infrastructure

In the context of monitoring the SAP Mobile Infrastructure with the CCMS, various jobs are monitored; the monitoring
architecture must be made aware of these jobs. The SAP Mobile Infrastructure also uses availability monitoring with the
GRMG.

Standalone Database

To monitor the relevant host, register the host agent and the operating system collector as described in Registering SAP
NetWeaver Components and Hosts in CEN.

To monitor the availability of a database, use the monitoring of selected processes with SAPOSCOL. Proceed as
described in Con guring Process Monitoring of the Database.

Adobe Document Services

The Adobe Document Services are used to create and process PDF-based forms. These are used both in mass printing in
backend systems and in interactive business processes.

You can use the GRMG to monitor the availability of the following components:

Web Service interface

XML Form module

PDF Manipulation module

This is custom documentation. For more information, please visit the SAP Help Portal 15
5/30/2022
The necessary con guration steps are described in GRMG Monitoring of SAP NetWeaver Components.

Con guring the Monitoring Architecture start page

Registering SAP NetWeaver Components and Hosts in CEN

Use
To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the corresponding component in
CEN. There are two ways of doing so:

If you are using the SAP NetWeaver Administrator (NWA), we recommend that you con gure the monitored components
using the Con guration Wizard.

If you are using the Alert Monitor, register the desired component in the con guration transaction for the Alert Monitor
(transaction RZ21). This procedure is described here.

Prerequisites
There is a CSMREG user in CEN.

There is also a CSMREG user on the ABAP or double-stack system to be monitored.

If you want to register a host with no SAP NetWeaver components in CEN, install the host agent on that host.

The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0 EhP2.

 Note
You can register Java and TREX systems with a release status up to SAP NetWeaver 7.0 EhP1 with CEN using CCMS
agents.

Procedure
1. To monitor an additional system or host, call transaction RZ21.

2. Choose Technical Infrastructure Con gure Central System Create Remote Monitoring Entry .

3. Choose which component type you want to register in CEN.

4. In the group box CSMREG User of the Central System, enter the password for the CSMREG user in CEN.

5. Depending on the type of component to be monitored, enter the following system and connection data for the
component to be monitored:

Type Input Data More Information

This is custom documentation. For more information, please visit the SAP Help Portal 16
5/30/2022
ABAP System ID The connection to the monitored system
is tested with user CSRMREG when you
Double-Stack Message Server
save (or if you choose the button in
Logon Group; the SPACE, which the RFC Connections to Remote
always exists, is set as the Component) group box. The monitored
default component is only added and the RFC
destinations (see below) are only created
Password of CSMREG on the if the test is performed successfully.
monitored system

Java
System ID

Message Server

HTTP port of the message

server

TREX You require the user at operating system

System ID
level to execute a con guration script on
Server the TREX host (see TREX
documentation).
Instance number

Register only hosts without SAP

Host Host Name
NetWeaver components here. Ensure that
the host agent is installed on the host.

 Note
You require this authentication since the Web service call for registering a component in CEN is protected.

7. Save your entries.

Technical Background

To monitor an ABAP or dual-stack system centrally, the system creates two RFC destinations in that system:

<SysID>_RZ20_COLLECT reads monitoring data for the monitored system; the connection uses the CSMREG
user.

This is custom documentation. For more information, please visit the SAP Help Portal 17
5/30/2022
a new monitor (see Creating and Changing Monitors).

 Note
To deregister a component again, call the topology display (see Technical Topology of the Monitoring Architecture).

More Information
Infrastructure of the SAP NetWeaver Management Agents Start Page

Host Agent

GRMG Monitoring of SAP NetWeaver Components

If the SAP NetWeaver components listed exist in your system landscape, you can use GRMG to monitor them. By following the
links below, you can view information about the associated con guration:

Setting Up GRMG Monitoring of the SAP Business Warehouse

Setting Up GRMG Monitoring of the Exchange Infrastructure

Setting Up GRMG Monitoring of the ICM

This section describes the con guration of the following functional units:

AS Java

Process Monitoring Infrastructure

Adobe Document Services

Business Communication Broker

Portal Infrastructure

Web Dynpro

2. Download the desired template by downloading the desired archive and decompressing it.

<scenstarturl>, in which you usually need to enter the host and port of the monitored component

<scendesc>, in which you usually need to enter the system ID and host of the monitored component

4. In CEN, call transaction GRMG, choose the Upload button, and specify the le that you have just downloaded.

5. Select the scenario that you have just uploaded and choose Edit GRMG Customizing.

7. To start the availability monitoring, select the corresponding row, and choose Start.

Checking the Entries (Optional)

This is custom documentation. For more information, please visit the SAP Help Portal 18
5/30/2022
1. After you have started the scenario, you can nd out from the Scenario Execution Status, whether the scenario was
correctly executed. After the scenario has been executed, there should be a green check mark ( ) here.

Setting Up GRMG Monitoring of the Portal Infrastructure

Use
You can use the Generic Request and Message Generator (GRMG) to monitor the availability of the Portal Infrastructure. You
de ne the required con guration settings in a GRMG Customizing le that has been transferred to the central monitoring
system (CEN) in accordance with the prerequisites below.

Prerequisites
The GRMG Customizing le has been transferred to CEN and adjusted. You can do this by transferring the required PI GRMG
Monitoring Template to the CEN in accordance with GRMG Monitoring of SAP NetWeaver Components.

Procedure
Steps in the Enterprise Portal

These steps are only necessary if you are using user names and passwords for authentication (see below).

1. The GRMG scenario for the portal requires an authenticated user (without a special role). To authenticate the user,
proceed as follows:

a. In the portal, choose System Administration → Permissions → Portal Permissions.

b. Open the folder Security Zones → sap.com → NetWeaver.Portal → low_safety → com.sap.portal.heartbeats →

components → PortalHeartbeat.

c. Double-click the PortalHeartbeat entry and switch to the Authorization Editor.

d. Add the desired user and assign the authorization to the user as an End User.

e. Save your entries.

Steps in CEN

This is custom documentation. For more information, please visit the SAP Help Portal 19
5/30/2022

1. Call transaction GRMG, and choose Upload/Download → Poll agent

for new scenario. Con rm the following question.

2. In the list, you see a scenario with the description GRMG:J2EE.PI<SID>:<Host> and the URL http://<Host>:
<Port>/irj/servlet/prt/portal/prtroot/ com.sap.portal.heartbeats.PortalHeartbeat. Select the relevant line, and choose

the button Edit GRMG Customizing.

3. Proceed as follows, depending on the type of authentication you are using:

Authentication using a user name and password

For the property USE_BASIC_AUTHENTICATION, set the value X .

In the editable properties for the property names LOGON_USER and LOGON_PASSWORD, enter the values for
the above user.

 Note
The password is stored in encrypted form in the secure storage.

Authentication using a client certi cate

 Note
With this type of authentication, in the URL/Destination input eld, you need to replace the pre x http with
https.

This is custom documentation. For more information, please visit the SAP Help Portal 20
5/30/2022

Insert a line in the editable properties, by choosing the Insert

Line button. Specify the following values for this property:

Component GRMG_RT

Version 1

Property Name SSL_CLIENT_ID

Property Value ANONYM (no certi cate, SSL encryption only),

DFAULT(standard certi cate of an SAP system), or the
name of the SSL client PSE to be used.

4. Save your changes.

5. Select the line of the scenario, and choose the Start button.

Checking the Con guration (Optional)

1. Call transaction RZ20 in CEN.

2. Expand the monitor set SAP CCMS Monitor Templates, and start the Availability and Performance Overview monitor. The
availability of the activated scenarios is displayed in the subtree GRMG-Tested Availability (Web Components).

Result
You have set up and started the availability monitoring of the Enterprise Portal.

This is custom documentation. For more information, please visit the SAP Help Portal 21
5/30/2022

Monitoring with the Generic Request and Message Generator start page

Setting Up GRMG Monitoring of the Exchange Infrastructure

Use
If you are operating XI Java components with a release speci ed in SAP Note 634771 in your system landscape, you can use
GRMG to monitor their availability. To do this, you must edit an appropriate template for a GRMG Customizing le and upload it
to the central monitoring system.

Prerequisites
So that all of the data for the XI infrastructure can be displayed in the Alert Monitor, you must create the system group
ExchangeInfrastructure_Systems in the central monitoring system (CEN). This system group must contain all systems in your XI
infrastructure (see Maintaining System Groups).

Procedure
1. Call SAP Note 634771, and download the le SAP_XI30_GRMG_Cust_Template.txt from the appendix to the note. The
template consists of six scenarios (enclosed by <scenario> … </scenario>); each scenario represents a component that
can be monitored with the GRMG:

Component <scenname> Path Pre x

Integration Repository XI_REP1 rep/rtc

Integration Directory XI_DIR1 dir/rtc

Runtime Workbench XI_RWB1 rwb/rtc

System Landscape Directory XI_SLD1 sld/rtc

J2SE Adapter Engine XI_ADP1 rtc

J2EE Adapter Engine XI_AF1 AdapterFramework/rtc

2. Delete the scenarios that you do not want to monitor with the GRMG from the template.

3. If you want to monitor multiple J2EE/J2SE Adapter Engines, copy the section for the corresponding scenario in the
template, insert the copied text between any two scenarios in the template, and change the value of the tag
<scenversion> in the newly inserted scenario.

4. Log on to CEN, and create an RFC destination of type HTTP for each scenario in transaction SM59.

a. If the component is running on a J2EE Engine, enter G as the type of the RFC destination; otherwise enter H as
the type. By default:

Component Type

Integration Repository G

Integration Directory G

Runtime Workbench G

System Landscape Directory G

This is custom documentation. For more information, please visit the SAP Help Portal 22
5/30/2022

Component Type

J2SE Adapter Engine H

J2EE Adapter Engine G

b. On the Technical Settings tab page, enter:

Field Entry

Target Host Name of the host on which the component is running

Service Number Port number of the component; this is assigned during

installation and can also be determined in the SLD

Path Pre x One of the values from the table above, depending on the
monitored component

c. On the Logon/Security tab page, enter:

Field Entry

User Name of the user; we recommend that you use the

XIRWBUSER user here, which should be available on all
components

Password User password; XIRWBUSER has the initial password

XIPASS (note that this is case-sensitive)

 Note
Note that, in the case of HTTP connections, the logon
tickets could be intercepted. You should therefore
always ensure that Secure Socket Layer (SSL) is used
for encryption, or that both systems are in a protected
environment.

Security Options In the case of an RFC destination of type G, choose the

Basic Authentication button.

d. Save your entries.

5. In the template, replace the value of the <scenstarturl> tag in the scenarios with the relevant name of the RFC
destination of type HTTP that you created above.

6. Save the GRMG Customizing le.

7. Call transaction GRMG in CEN.

8. To upload the GRMG Customizing le into CEN, choose the Upload button, and specify the above le.

9. Select the scenarios that you have just uploaded, and start these by choosing Start sel.

Checking the Con guration (Optional)

1. Call transaction RZ20 in CEN.

2. Expand the monitor set SAP CCMS Monitor Templates, and start the Exchange Infrastructure monitor. You can view the
availability of the activated scenarios.

Result
This is custom documentation. For more information, please visit the SAP Help Portal 23
5/30/2022
You have set up and started the availability monitoring of the Exchange Infrastructure.

Monitoring with the Generic Request and Message Generator start page

Setting Up GRMG Monitoring of the SAP Business Warehouse

Use
If you are operating a SAP Business Warehouse with a release speci ed in SAP Note 706290 in your system landscape, you can
use GRMG to monitor the availability of the following BW components:

UDC Enterprise Beans

SAP BI Java connectors

Metamodel Repository

RFC destination for the BW system

Prerequisites
You have installed a BI Java component for which you want to monitor the availability with the GRMG.

You have registered the system of the BI Java component with the central monitoring system (CEN) (see Registering
SAP NetWeaver Components and Hosts in CEN).

Procedure
1. You can nd a template for the GRMG Customizing le in the UD Connect Bean le bi_sdk_grmg.ear. The name of
this le is grmg-customizing.xml. Copy this le to a location that is readable from your front end.

2. Call transaction GRMG in CEN.

3. Choose the Upload button, and then select the above le grmg-customizing.xml.

4. Select the line with the name BI UDC, and choose the button Edit GRMG Customizing.

5. Edit the URL/Destination input eld. Replace hostname and port number with the corresponding values for your J2EE
server, on which you have performed deployment of UD Connect.

6. Enter the values of the property name JNDI_Name for component CONNECT0. This is the JNDI name of a connector for
which you have performed deployment.

By default, the BI Java connectors have the following JNDI names:

Connector JNDI Name

BI JDBC Connector SDK_JDBC

BI ODBO Connector SDK_ODBO

BI SAP Query Connector SDK_SAPQ

BI XMLA Connector SDK_XMLA

If you have cloned your connector, specify the name of the clone.

7. Create GRMG components for additional BI connectors:

a. Choose the Append Line button.

This is custom documentation. For more information, please visit the SAP Help Portal 24
5/30/2022
b. Enter the following values in the new line:

Column Value

Component CONNECT<n> (start with 1 and increment upwards for each

additional connector)

Version Type 1

Property Name JNDI_Name

Property Value <JNDI Name of the connector>

c. Save your changes and con rm that you want to use a new component name.

d. Enter a description of the component. When doing so, use the following naming convention: SAP BI Java
Connectors <n> (where <n> is the value speci ed for CONNECT<n> above).

e. Choose Continue, and con rm that you have created a new component.

8. Adjust the speci cations for the component RFC. In doing so, you specify the RFC destination for the BW system. You can
nd the corresponding values in the SAP NetWeaver Administrator. To do this, choose Con guration
Management Infrastructure Management JCo RFC Destinations .

Choose the RFC destination for the BW system and transfer the values from the Host Information and User Information
tab page to the following lines of the editable properties:

ApplicationServerHostClientLanguagePasswordSystemNumberUserName

9. Save your entries and exit the screen for editing the GRMG Customizing.

10. Select the scenario that you have just edited, and choose Start. As of this point, the scenario is periodically executed.

Checking the Con guration (Optional)

2. To view the availability data for the monitored components, call transaction RZ20 in CEN, and start the Heartbeat
monitor in the SAP J2EE Monitor Templates monitor set. Expand the subtree BI UDC GRMG: SAP BI UD Connect on
<Hostname> .

Result
You have set up and started the availability monitoring of the speci ed BW components.

Related Information
Monitoring with the Generic Request and Message Generator

Con guring Alert Triggering and Alert Reactions

Use
You have performed the following processes in the context of Con guring the Monitoring Architecture:

Con guring a Central Monitoring System (CEN)

Monitoring: Con guring ABAP Instances

Monitoring: Con guring Java Instances

This is custom documentation. For more information, please visit the SAP Help Portal 25
5/30/2022
Monitoring: Con guring Other SAP NetWeaver Components

You have therefore created the required connections from the central monitoring system (CEN) to the monitored components;
the data required for monitoring is determined and transferred to CEN.

You should next adjust the settings in the Alert Monitor to your requirements. These steps are not vital for the functioning of
the monitoring architecture, but are strongly recommended for optimal use. The steps belong to three areas:

Adjusting the threshold values and other properties of the nodes - when should an alert be triggered for a node?

Adjusting the auto-reaction methods - what should happen in the case of an alert (and in particular: who should be
informed in the case of an alert)?

Adjusting the display in the Alert Monitor - how should the data be displayed?

Prerequisites
This process is part of Con guring the Monitoring Architecture. To completely con gure landscape-wide monitoring, you must
also perform the other processes.

Process
Optional: Creating Properties Variants

If you want to set threshold values or other properties of MTEs that are time-dependent, use Monitoring Properties Variants to
do this. A properties variant of this kind contains properties and method assignments for MTEs. You can also assign a properties
variant to an operation mode. The assigned properties variant is then automatically activated at every change of operation
mode.

 Note
If you have created your own properties variants, whenever you change properties and methods, the system queries for
which properties variant the change should apply.

More Information
Creating a Monitoring Properties Variant

Adjusting the Threshold Values

1. Call the alert monitor by starting transaction RZ20, and start the desired monitor.

2. Select a desired node and choose the Properties button.

3. You can set diﬀerent properties, depending on whether you have selected a performance attribute, a

log attribute, or a

status attribute. The most important change aﬀects the maintenance of threshold values for performance attributes. To
do this, follow the procedure below:

a. Switch to change mode by choosing the button.

b. Specify the desired values in the Threshold Values group box.

c. Save your entries.

This is custom documentation. For more information, please visit the SAP Help Portal 26
5/30/2022

 Note
By default, your changes apply for all nodes in the same MTE class/attribute group. However, you can also
make changes that apply only to the relevant node itself (see

Changing Properties in the Alert Monitoring Tree).

Adjusting the Auto-Reaction Methods

Auto-reaction methods start automatically, if an alert occurs in the corresponding MTE. The most import application of auto-
reaction methods are automatic noti cations in the case of an alert, for example, using e-mail or SMS.

If you want to work with auto-reactions, you should rst decide whether you want to execute the auto-reactions locally or
centrally:

Local auto-reaction

This is the default setting of the monitoring architecture: the auto-reaction method is executed in the system in which
the alert occurs. In large system landscapes in particular, this means a more con guration and maintenance work is
required, since you must adjust the auto-reactions in each system.

 Caution
In the case of MTEs of the monitor set SAP J2EE Monitor Templates (with the exception of MTEs of the Availability
Monitoring with GRMG), you cannot assign any local auto-reactions.

Central auto-reaction

In the case of a central auto-reaction, the method is not started in the system in which the alert occurs, but rather in the
CEN. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately
in a central location. We recommend this type of auto-reaction (more information: Setting Up Central Auto-Reaction
Methods).

 Note
If you are using a central auto-reaction, you cannot determine the method executed using properties variants. To
nevertheless allow diﬀerent settings depending on the time at which the alert occurs, we recommend Forwarding
Alerts to Alert Management (ALM).

For automatic noti cation in the case of alerts, you must rst adjust the relevant method to your requirements; when doing so,
you can choose between two techniques. Of these, forwarding alerts to Alert Management means a greater con guration eﬀort
is required, but also provides more advanced functions:

Forwarding Alerts to Alert Management (ALM)

De ning Automatic Alert Noti cation

 Note
If you want to use central auto-reactions, you must activate the radio button Only in Central System, Triggered by
CCMS Agent on the Control tab page in the de nition of the method used.

Assigning the Auto-Reaction Methods

You must nally assign the adjusted methods to your desired MTEs:

Assignment to a local auto-reaction

This is custom documentation. For more information, please visit the SAP Help Portal 27
5/30/2022
1. Call the alert monitor by starting transaction RZ20, and start the desired monitor.

2. Select a desired node and choose the Properties button.

3. Choose the Methods tab page and then choose the Method Assignment pushbutton.

4. Switch to change mode by choosing the button.

5. Switch to the Auto-Reaction tab page, select the Method Name in the Method Assignment group box, and specify
the name of your adjusted auto-reaction method in the corresponding input eld.

6. Save your entries.

 Note
By default, your changes apply for all nodes in the same MTE class/attribute group. However, you can also
make changes that apply only to the relevant node itself (see

Changing Properties in the Alert Monitoring Tree).

Assignment to a central auto-reaction

1. In CEN, start transaction RZ21, and choose Technical Infrastructure Con gure Central System Assign Central
Auto-Reactions .

2. In the System ID subscreen, select the desired systems, and the desired MTE classes in the MTE Class
subscreen, to which you want to assign a central auto-reaction method. You can always select multiple systems
and MTE classes.

 Note
Diﬀerent systems usually have diﬀerent MTE classes. After calling the function, the MTE classes of the local
system are displayed rst. To include the MTE classes of other systems in the list, select the desired systems
and choose MTE Classes of System. The system then displays the MTE classes of the selected system in
the list of MTE classes.

3. In the De ned Central Auto-Reactions subscreen, select the desired method that you want to assign to the
selected MTE classes of the selected systems.

4. Choose Assign Central Auto-Reaction Method. The system then immediately displays the corresponding
assignments in the lower subscreen.

Creating Your Own Monitors

We recommend that you only use the monitors in the delivered monitor sets as templates for your own monitors. More
information about creating your own monitors: Creating and Changing Monitors.

Setting Up Central Auto-Reaction Methods

Use
In the monitoring architecture, you can react automatically to an alert using auto-reaction methods. These methods are
automatically started in the case of an alert and by default are executed in the system in which the alert occurs.

As of SAP Web Application Server 6.10, you can de ne central auto-reaction methods in the monitoring architecture in the
context of the central monitoring of SAP components. The auto-reaction methods are not started in the system, in which the
alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in
monitored components to be performed immediately in a central location.

This is custom documentation. For more information, please visit the SAP Help Portal 28
5/30/2022

Prerequisites
The central monitoring system (abbreviated to CEN in the following) has a release status of at least SAP Web
Application Server 6.10.

The monitored SAP components have a release status of at least release 4.6B with a kernel as of 4.6D AKK patch level
692.

The monitored SAP components are connected to CEN using the CCMS agent SAPCCM4X. The agent must have a
release status of at least version 6.10.

You can determine the version of the CCMS agent by calling it with the option -v (such as: sapccm4x -v). The version
is the number after the term kernel (for example:
20010110, compiled at Aug 19 2001, kernel 6100_0_104 platform 00230_32bit).

 Note
Monitored SAP components with SAP R/3 3.1 and systems and components that are centrally linked using the
SAPCCMSR agent (such as values in the Operating System Monitor) formally belong to CEN (see Monitoring SAP
R/3 3.x Systems). Therefore, auto-reaction methods can always be started centrally here. You can therefore nd the
relevant MTE classes in the list of the MTE classes of CEN.

Restrictions

You cannot assign any central auto-reaction methods to the MTE classes that belong to the application servers of CEN as
described below. In this case, use the conventional assignment using a local auto-reaction method.

Procedure
Perform all con guration steps for the central auto-reaction method only in CEN.

1. Choose CCMS Con guration Alert Monitor , or call transaction RZ21.

2. The system displays the Monitoring: Properties and Methods screen. Choose Technical Infrastructure Con gure
Central System Assign Central Auto-Reactions .

3. The Maintain Central Auto-Reactions screen appears. On this screen, you can perform all work steps to de ne, assign,
and edit central auto-reaction methods. A normal rst step is to create a central auto-reaction method from an existing
(local) auto-reaction method and to then assign this to the desired MTE class in the desired system. You can make the
following settings:

This is custom documentation. For more information, please visit the SAP Help Portal 29
5/30/2022

Creating, Editing, or Deleting a Central Auto-Reaction Method

You can execute any auto-reaction method centrally that is de ned as an auto-reaction method in the central system. The
method does not need to be known in the monitored system.

You can also use the prede ned auto-reaction methods of the monitoring architecture for this. These are, for example:

Automatic Alert Noti cation

Automatic Execution of Operating System Commands

To have an existing auto-reaction method executed centrally, follow the procedure below:

1. In the De ned Central Auto-Reactions subwindow, choose . On the following dialog screen, enter the desired auto-
reaction method in the input eld next to the Create with Template pushbutton, or use the input help, which provides a
list of all released auto-reaction methods. Choose Create with Template.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 30
5/30/2022
You can also use an existing central auto-reaction method as a template for a new auto-reaction method. To do this,
select the desired method in the De ned Central Auto-Reaction subscreen and choose .

2. The Monitoring: Methods screen appears. The settings are copied from the template, with the exception that the
indicator Only in central system, triggered by CCMS agent is activated in the Execute Method group box of the Control
tab page. Therefore, you do not usually need to change the settings, other than to enter a name for the central auto-
reaction method.

3. Save your entries. The system then displays the method immediately in the De ned Central Auto-Reactions subscreen.

To create a new central auto-reaction method, follow the procedure below:

1. In the De ned Central Auto-Reactions subwindow, choose . On the following dialog screen, enter the desired name for
the method in the input eld next to the Create button and choose Create.

2. The Monitoring: Methods screen appears. Enter the desired settings for the method (for more information about
creating auto-reaction methods, see De ning, Releasing, and Transporting Methods) and ensure that you activate the
radio button Only in central system, triggered by CCMS agent.

3. Save your entries. The system then displays the method immediately in the De ned Central Auto-Reactions subscreen.

To edit a central auto-reaction method, follow the procedure below:

1. In the De ned Central Auto-Reaction Methods subscreen, select the desired method and choose Edit.

2. The Monitoring: Methods screen appears. Make the desired changes to the method de nition and ensure that the
selection eld Only in central system, triggered by CCMS agent is activated.

3. Save your changes.

To delete a central auto-reaction method, follow the procedure below:

1. In the De ned Central Auto-Reaction Methods subscreen, select the desired method and choose

2. Con rm that you want to delete the method. If the method is used in an assignment, the system will also inform you of
this, and ask whether you want to delete the method and all of its assignments.

Assigning a Central Auto-Reaction Method

Enter the MTE classes and system to which you want to assign a central auto-reaction method. The system checks the
assignment regularly.

1. In the System ID subscreen, select the desired systems, and the desired MTE classes in the MTE Class subscreen, to
which you want to assign a central auto-reaction method. You can always select multiple systems and MTE classes.

 Note
Diﬀerent systems usually have diﬀerent MTE classes. After calling the function, the MTE classes of the local system
are displayed rst. To include the MTE classes of other systems in the list, select the desired systems and choose
MTE Classes of System. The system then displays the MTE classes of the selected system in the list of MTE classes.

2. In the De ned Central Auto-Reactions subscreen, select the desired method that you want to assign to the selected
MTE classes of the selected systems.

3. Choose Assign Central Auto-Reaction Method. The system then immediately displays the corresponding
assignments in the lower subscreen.

Perform these steps for all desired central auto-reaction methods.

This is custom documentation. For more information, please visit the SAP Help Portal 31
5/30/2022
Assigning a Central Auto-Reaction Method from the Alert Monitor

In practice, of the procedures described here, you will use the assignment of MTE classes to a central auto-reaction method
most frequently. To make this procedure simpler, you can also call it directly from the Alert Monitor (transaction RZ20).

1. Start the Alert Monitor by calling transaction RZ20.

2. Activate maintenance functions by choosing Extras Activate Maintenance Functions .

3. Expand the monitor set that contains the monitor that you require, and choose Load Monitor, or double-click the desired
monitor.

4. Select the MTEs to whose MTE classes you want to assign a central auto-reaction method, and choose Edit Node
(MTE) Assignment Central Auto-Reaction Method .

 Note
In this way, you can also very quickly assign a central auto-reaction to all MTE classes of performance attributes in a
monitor. To do this, select all nodes by choosing Edit Selections Select All Nodes (MTE) , before switching to the
administration of central auto-reactions.

5. The Central Auto-Reactions screen appears. The desired systems and MTE classes are selected, meaning that you now
only need to select the desired method.

6. Choose Assign Central Auto-Reaction Method. The system then immediately displays the corresponding
assignments in the lower subscreen.

Deleting an Assignment of a Central Auto-Reaction Method

In the lower subscreen, the system displays the existing assignments of central auto-reaction methods. To delete assignments,
select one or more rows of this table and choose Delete Assignment.

 Caution
The central auto-reaction methods are always started under the user in the client that activated the central method
dispatcher (to do this, choose Technical Infrastructure Method Execution Activate Central System Dispatching in
transaction RZ21). As the client is also of great importance for automatic alert noti cation, ensure that you are in the client
from which the mails are to be sent when you activate the central system dispatching.

If you have activated the central system dispatching using the wrong user or in the wrong client, rst deactivate it by
deleting the job SAP_CCMS_CENSYS_DISPATCHER in transaction SM37. The job is controlled by the event
SAP_CSM_TRIGGER_CENSYS_DISPATCH. Then reactivate the central system dispatching using the correct user in the
desired client.

Result
Alerts in the assigned MTE classes of the monitored systems now trigger an auto-reaction in the central monitoring system.

 Note
If central auto-reactions are not reliably executed, that is, the corresponding nodes in the monitored system remain on the
runtime status Run required, refer to SAP Note 1265906.

Forwarding Alerts to Alert Management (ALM)

Purpose
Alert Management (ALM) provides numerous functions for handling alerts, such as representation rules, escalation, or
noti cation using external communication methods.

Conditions for critical situations are prede ned in Alert Management. If an alert is triggered in ALM that meets these
conditions, those responsible or interested are identi ed and are informed about the situation by the immediate sending of
alerts. The alerts are displayed to the recipient in one of the following programs:

In the Universal Work List (UWL of the Enterprise Portal) as of SAP NetWeaver '04

In the Alert Inbox. The Alert Inbox is an application based on Business Server Pages (BSP), which can be called using the
transaction ALRTINBOX or the corresponding URL (http://<host>:<port>/sap/bc/bsp/sap/alertinbox).

There are also a number of external communication methods available. You can con gure these in SAPconnect (transaction
SCOT) and use them in addition to inform the recipient of an alert about the problem: Internet mail, SMS, and fax.

The auto-reaction method CCMS_Send_Alert_to_ALM, which forwards alerts for assigned monitoring architecture nodes to the
ALM, is available in the alert monitor. This method is therefore used in a similar way to the auto-reaction method
CCMS_OnAlert_Email, with which you can de ne an automatic alert noti cation. A diﬀerence is that when you are forwarding
alerts to the ALM, you no longer need to specify the sender and recipient in the method de nition, and recipients can also be
de ned using authorizations and roles. More communication methods and additional Alert Management functions, such as
escalations or con rming the alert, are also available.

This is custom documentation. For more information, please visit the SAP Help Portal 33
5/30/2022

Prerequisites
Central system dispatching must be activated in the central monitoring system (CEN). To activate central system
dispatching, call transaction RZ21 in client 0 and choose Technical Infrastructure Con gure Central System Activate
Central System Dispatching .

Background dispatching must be activated for all monitored systems and in CEN. To activate background dispatching, call
transaction RZ21 in client 0 and choose Technical Infrastructure Local Method Execution Activate Background
Dispatching .

To be able to display alerts in the Alert Inbox (transaction ALRTINBOX or URL), which is based on BSPs, you must
activate the corresponding BSP service. To do this, in transaction SICF, choose Default_host sap bc bsp sap alert
inbox . Open the context menu for the alert inbox and choose Activate.

Process Flow
The gure below represents the route of the CCMS alerts from the system that triggers the alert through the central
monitoring system (CEN) and RFC to the central ALM system. The ALM system forwards the alerts in every case to the relevant
display program of the recipients (Alert Inbox, UWL) and as an e-mail, fax, or SMS, if these external communication methods
are con gured in SAPconnect.

 Note
Note in the following description that settings in ALM and in SAPconnect are client-dependent.

To con gure the forwarding of CCMS alerts to the ALM, proceed as follows:

Setting Up a Destination Between the Central Monitoring System and the Alert Management Framework

This is custom documentation. For more information, please visit the SAP Help Portal 34
5/30/2022
You require an RFC destination to transfer alerts between the central monitoring system (CEN) and the central alert
management system. This RFC destination points from client 0 of CEN to the work client of the central AML system and must
have the necessary authorizations to log on to the ALM system. Perform the following steps:

If no suitable user exists yet, create a user for the RFC destination in the work client of the ALM system (transaction
SU01).

In CEN, create an RFC destination to the work client of the ALM system with a xed user/password combination
(transaction SM59).

Specify this RFC destination in transaction SALRT1 in client 0 of CEN, to make the destination for the ALM system known
to the monitoring architecture.

 Note
You require this RFC destination even if CEN and ALM are in the same system.

Con guring Alert Management

Alerts from the CCMS have the alert classi cation CCMS ALERTS in Alert Management (ALM). You can specify diﬀerent alert
categories within this classi cation. These categories can have diﬀerent properties. The name of the category corresponds to
the parameter CATEGORY of the auto-reaction method CCMS_Send_Alert_to_ALM.

 Note
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.

You can set separate properties for each alert category; these include, for example, the priority of the alert, escalation settings,
or the recipients in each case. You can de ne the recipients in the following ways:

Using the name ( Fixed Recipients button)

Using the user role ( Recipients Via User Roles button)

Using the authorizations ( Subscription Authorization button)

Con guring SAPconnect

The alerts are displayed in the UWL, application or in the Alert Inbox in each case. If alerts are also to be delivered using the
external communication methods e-mail, SMS, or FAX, these communication methods must be con gured in SAPconnect of the
ALM work client.

 Note
Note that the recipients and the users for the RFC destination between the central monitoring system (CEN) and the ALM
system must be assigned the desired communication method in User Maintenance (transaction SU01).

Adjusting and Assigning the Method

Adjust the auto-reaction method CCMS_Send_Alert_to_ALM to your requirements in the work client of CEN, and assign the
method to the desired nodes as a local or as a central auto-reaction method (see Con guring the Method for Forwarding Alerts
to the ALM). Specify a valid ALM alert category in the CATEGORY parameter in the method de nition. If you want to use
diﬀerent alert categories, use diﬀerent copies of the method de nition accordingly.

Result

This is custom documentation. For more information, please visit the SAP Help Portal 35
5/30/2022
You have set up the forwarding of selected alerts to Alert Management. If an alert occurs in one of the assigned nodes of the
alert monitor, the speci ed recipients are immediately informed using ALM.

Example
For an example for the con guration, see Example Con guration: Forwarding Alerts to the ALM.

De ning an Automatic Alert Noti cation

Use
With the monitoring architecture, you can de ne auto-reaction methods that are automatically executed when alerts occur. As
of SAP R/3 4.6A, you can assign the method CCMS_OnAlert_Email to MTE classes in your system. If an alert occurs in this MTE
class, you are informed by e-mail, fax, or pager, even if you are not working in the Alert Monitor.

CCMS_OnAlert_Email can automatically dial a pager or send an e-mail or a fax to the following addressees:

A Business Workplace user in client 000

A distribution list or an external e-mail address

The auto-reaction method for sending the e-mail is started at most ve minutes after the alert occurs. However, there can be a
delay before the e-mail is sent to external e-mail addresses (that is, addresses of users that are not de ned in client 000 of the
same SAP system), depending on the settings in SAPconnect. You should therefore set the period for the SAPconnect send
process to less than an hour.

The message text contains the same information that is displayed in the Alert Monitor:

Description of the problem that exists

Time and location at which the problem occurred

Severity and color of the alert

Prerequisites
To dial multiple pagers or to send an e-mail or a fax to multiple users (external recipients or recipients in client 000), you must
rst create a distribution list that contains the required data for the recipients (pager number, name, e-mail address, fax
number).

 Note
SAPconnect must be con gured in client 000, if the message is to be sent to an external address.

Procedure
Tailoring the Auto-Reaction Method

1. Choose CCMS → Con guration → Alert Monitor, or call transaction RZ21.

2. In the Methods group box, select Method De nitions and choose Display Overview.

3. Select the method CCMS_OnAlert_Email and choose Edit Data.

4. Choose change mode with the Display «Change ( ) pushbutton, and choose the Parameters tab page.

5. Fill out the elds as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 36
5/30/2022

Parameter Meaning

SENDER SAP username of the person in whose name the e-mail is sent

RECIPIENT SAP user name of the e-mail recipient, distribution list, or

external e-mail address; to automatically send an e-mail to
multiple external e-mail addresses, you must create a
distribution list in client 000 that contains these external
addresses.

If the user is not de ned in client 000 you must also specify
the system and the client in which the user exists (such as
C11:003:PARKERJ).

RECIPIENT-TYPE ID Flag for the address type

 Note

Users that are de ned in the system in clients other than 000 cannot be speci ed in the Business Workplace
directly as sender or recipient; they are regarded as external recipients. You should therefore specify the address
type R (remote address) for client-speci c senders and recipients in the Parameters tab page.

If you want to de ne diﬀerent recipients for diﬀerent alerts, copy the method de nition of CCMS_OnAlert_Email.
To do this, select the method in the list and choose Copy ( ). Note that you must release the copied method as
an auto-reaction method again (see De ning, Releasing, and Transporting Methods).

a. Save your entries.

Assigning the Method to the Desired Node

1. Start the Alert Monitor using transaction RZ20 or choose CCMS → Control/Monitoring → Alert Monitor.

2. Start the desired monitor from the list by double-clicking it.

3. Select the desired node and choose Properties.

4. The Monitoring: Properties and Methods screen appears. The rest of the procedure depends on whether you want to
assign the analysis method only to this node or to the entire MTE class.

Assign Analysis Method to Only this MTE

1. Choose the Methods tab page and then choose the Method Assignmentbutton.

2. The Monitoring: Methods screen appears. Choose change mode with the Display «Change ( ) button, and choose the
Auto-Reaction tab page.

3. In the Method Assignment group box, choose the Method Name radio button and enter CCMS_OnAlert_Email in the
associated eld.

4. Save your entries.

Assign Analysis Method to the Selected MTE Class

1. Choose the name of the MTE class in the header data of the screen by double-clicking it, and then choose the change
mode with the Display «Change ( ) button.

2. In the Auto-Reaction Method group box, choose the Method Name radio button and enter CCMS_OnAlert_Email in the
associated eld.