Activating and Customizing Monitoring with the GRMG

Purpose

This process describes the activation of availability monitoring with the GRMG for Java or other HTTP-compatible components.

Prerequisites

You have completed the installation of SAP components in your system landscape; all SAP components should have the newest Support Packages installed.

Process Flow

The steps required to customize availability monitoring with the GRMG to your installation and to start the monitoring are described below.

  1. It is a prerequisite for availability monitoring with the GRMG - and for the CCMS Monitoring Architecture in general - that there is a central monitoring system (CEN) in your system landscape.

    If possible, reserve a separate SAP system for monitoring and system management. 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 always profit from the newest developments in the areas of monitoring and system management. CEN does not require any special and expensive hardware features.

  2. The Internet Communication Manager (ICM) must be configured and active.
  3. You require a suitable GRMG Customizing file for each GRMG scenario. The file contains information that the GRMG infrastructure (which runs on CEN) requires to monitor a particular application.

    Templates for these Customizing files are delivered with the application. These templates must be loaded into CEN and do not usually need to be manually adjusted. To start the availability monitoring, the associated scenario must be started. There are different ways to perform this process, depending on the monitored application:

    • For AS Java and applications that run on AS Java, the activation of the availability monitoring is normally performed in the Configuration Wizard. If you transfer the Customizing file to a CCMS agent there, the corresponding scenario is transferred to CEN and started there. Depending on the application, you may still have to adjust the scenario in CEN.
    • In CRM, there is the Extended Configuration Manager, in which you can activate availability monitoring for different CRM components (CRM Internet Sales and CRM Internet Customer Self-Service). The adjustment of the Customizing file, the transfer to CEN, and the start of the scenarios selected in this way is then performed automatically.
  4. If the application does not support these automatic methods, you can perform the steps required to start availability monitoring manually from CEN:
    1. Check the documentation for the application to find out where the templates are stored, and load these into CEN (more information: Loading a GRMG Customizing File into the Central Monitoring System).
    2. Adjust the templates (more information: Adjusting a GRMG Customizing File). For information about exactly which changes you need to make, refer to the documentation for installing or operating the application or current extensions to this documentation in SAP Notes. You usually only need to adjust the URL so that it specifies the host and port of your installation.
    3. After you have loaded all Customizing files into the central monitoring system, start the availability monitoring (more information: Starting GRMG Scenarios).

Restrictions with Encrypted Passwords

Do you use scenarios that use encrypted passwords?

If you use scenarios of this type, note the following restrictions when selecting your work client:

  • We recommend that you use client 000 as the work client for all GRMG-related work. In detail, this means:
  • If this is not possible in your IT environment, you can run the data collection method GRMG_TRIGGER in a background process as a workaround. In this way, you can run the method in a work client other than client 000. Then use this client for all GRMG-related work.

    To run GRMG_TRIGGER in the background, follow the procedure described in Executing GRMG Scenarios in the Background.

The reason for these restrictions is that the Secure Storage/DB function that encrypts the GRMG passwords uses a client-dependent table in SAP NetWeaver 04.

During the execution of scenarios, the GRMG can only access passwords if the execution is performed in the same client as the original encryption. When executing the data collection method GRMG_TRIGGER in dialog, this must be client 000; in the case of execution in the background, this can be any client.

Linking a GRMG Scenario with the System ID of the Corresponding Monitored System

You can link a GRMG scenario with the System ID (Long SID, more information: Monitoring Multiple Systems with Identical System IDs) of the monitored system in which the relevant scenario is running. This improves the performance of GRMG availability monitoring in the following cases:

If you create a new GRMG scenario, the relevant field for the linked system will already be filled in most cases; however, you can also manually create the assignment for any scenario by entering the system ID in the input field CCMS Long SID of Monitored System (If Applicable) of the GRMG Scenario screen. You can also check and set the assignments of all GRMG scenarios by choosing the button  Edit/Delete →Assign SIDs to Scenarios.

 Monitoring with the Generic Request and Message Generator start page