This process describes the activation of availability monitoring with the GRMG for Java or other HTTP-compatible components. For example, the following SAP applications currently use the GRMG:
· Customer Relationship Management
· SAP Exchange Infrastructure
· Portal Infrastructure
· SAP Business Intelligence
· J2EE Engine
· Adobe Document Services
This process is intended for consultants and customers who want to activate GRMG monitoring for an application that has already been instrumented for monitoring with the GRMG (see GRMG: Instrumenting an Application).
You have completed the installation of SAP components in your system landscape; all SAP components should have the newest Support Packages installed.
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:
¡ In the case of the J2EE Engine and applications that run on the J2EE Engine, the availability monitoring is usually activated in the Visual Administrator (see Enabling the Availability Monitoring of J2EE Engine). 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.
In both cases, the Customizing file is transferred to CEN using the CCMS agent SAPCCMSR. The agent must therefore be registered with CEN.
4. If the application does not support these automatic methods, you can perform the steps required to start availability monitoring manually from CEN:
a. Check the documentation for the application to find out where the templates are stored, and load these into CEN (see Loading a GRMG Customizing File into the Central Monitoring System).
b. Adjust the templates (see Adjusting a GRMG Customizing File). For information about exactly which changes you need to make, see 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.
c. After you have loaded all Customizing files into the central monitoring system, start the availability monitoring (see Starting GRMG Scenarios).
The other functions of transaction GRMG are described in Additional Settings for Availability Monitoring with the GRMG.
Do you use scenarios that use encrypted passwords?
You can identify scenarios of this type from the property type PW in the scenario editing mode of transaction GRMG (see Adjusting the GRMG Customizing File). For example, Enterprise Portal scenarios encrypt the property LOGON_PASSWORD.
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:
¡ Register all CCMS agents with client 000 of CEN. This applies both for the administration user and fort he CSMREG user (for more information about registering CCMS agents, see Installing and Registering CCMS Agents).
¡ Also use transaction GRMG only in client 000.
· 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, perform the following steps:
a. Start transaction RZ21; in the Methods group box, select Method Definitions and choose Display Overview.
b. Select the method GRMG_TRIGGER from the list, and choose Edit Data ().
c. Switch to change mode by choosing the button (Display « Change).
d. Choose the Control tab page and, in the Execute Method group box, choose Periodically in background process (as job).
e. Save your changes.
f. By default, the background dispatcher, which starts methods of this type, runs once an hour. This is not often enough for availability monitoring. You therefore need to change the scheduling of the job SAP_CCMS_MONI_BATCH_DP in transaction SM37 so that it runs every two minutes. When you change the scheduling, the job is then, by default, executed using the client/user with which you performed the scheduling.
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.