GRMG: Instrumenting an Application

This process provides an overview of the steps required to instrument an application for availability monitoring with the GRMG. Before you begin the implementation of the GRMG application, you should study the concept and structure of a GRMG scenario. For a general introduction to the concept, see Monitoring with the Generic Request and Message Generator.

If you want to instrument a component for availability monitoring with the GRMG, you must first perform the following steps:

• Check that the technical prerequisites for GRMG monitoring are fulfilled.

  The central monitoring system requires a SAP Web Application Server 6.20 as of Support Package 12 for the GRMG infrastructure. As of SAP Web Application Server 6.40, the current version of the GRMG infrastructure is part of the standard SAP system. We recommend that you use a system with SAP Web AS 6.20 or higher exclusively as the central monitoring system of your system landscape.

• Design your GRMG scenario.

  Determine which applications, components, or processes are to be monitored. Determine also which files are required for checking, and ensure that a GRMG application can access these files.

  Note

  Scenarios with different software components (especially if there are no active data suppliers available for these components) and Web-based business scenarios are typical examples of applications that you can usefully monitor with the GRMG.

• Create the messages that are to be returned in the GRMG response.

  The GRMG application returns messages in the GRMG response (see Structure of the GRMG Response) as the result of availability tests. Clarify which messages are to be returned in different situations, and whether these messages are to contain parameters.If you use SAP T100 messages, you must ensure that these messages and the associated long texts are available in the central monitoring system (SAP Web Application Server 6.20 or higher). SAP application developers should contact the CCMS group for this.

• For Java Applications: Add the GRMG role to the Deployment Descriptor.
• Create a template for the GRMG Customizing file.

  The GRMG Customizing file contains all the information required about the scenario, the monitored components, and the parameters that are sent to the components with the GRMG request (see Creating the Template for the Customizing File).The GRMG request is automatically generated using the Customizing file (see Structure of the GRMG Request).

  Ensure that a template for the file is delivered with the application.

  You should also document how the template is to be adjusted by the customer (see Customizing and Operating the GRMG Monitoring), and include the instructions for doing this in the Best Practices for the appropriate service.

  Note

  If your application is integrated into the Extended Configuration Management (XCM) of CRM ISA, you can use the XCM functions for program-controlled generation of GRMG Customizing files. The customer can then create, upload, and generate a GRMG scenario at the touch of a button.

• Implement the GRMG application.

  The GRMG application receives the GRMG request with all transferred parameters from the GRMG infrastructure, performs the availability checks, and returns the result to the GRMG infrastructure as the GRMG response (see Principle of Creating a GRMG Application and Example Coding for a GRMG Application).

• Create a monitor definition for the alert monitor (transaction RZ20).

  The results of the availability monitoring are displayed in the Alert Monitor. For optimal display, you should create a corresponding monitor (see Creating a Rule-Based GRMG Monitor). There is usually a separate monitor set for each application that is instrumented in the CCMS monitoring architecture. Create a monitor, or at least a subtree, in this set. SAP application developers should contact the CCMS group so that the monitors are available in the central monitoring system.

 Monitoring with the Generic Request and Message Generator start page