This process describes the activation of availability monitoring with the GRMG for Java or other HTTP-compatible components.
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 (more information: 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.
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.
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 both cases, the Customizing file is transferred to CEN using the SAP NetWeaver management agent. The agent must therefore be registered with CEN.
The other functions of transaction GRMG are described in Additional Settings for Availability Monitoring with the GRMG.
Restrictions with Encrypted Passwords
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 (more information: 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:
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.
More information: SAP Note 1249451.