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 define the required configuration settings in a GRMG Customizing file that has been transferred to the central monitoring system (CEN) in accordance with the prerequisites below.

Prerequisites

The GRMG Customizing file has been transferred to CEN and adjusted. Depending on whether your CEN is a double-stack or an ABAP system, you can do this using one of the following procedures:

Type of CEN	Prerequisites
Double-Stack	You have performed the configuration task Configuring GRMG for Java-Based Components for the monitored portal system, and selected Enterprise Portal or All from the list of available scenarios.
ABAP	You have transferred the required PI GRMG Monitoring Template to CEN from the SAP Service 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 → Authorizations → Authorizations for the Portal.

                            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

       2.      Call transaction GRMG, and choose  Upload/Download → Poll Agents for new scenario. Confirm the following question.

       3.      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.

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

○       Authentication using a user name and password

Set the value X for the property USE_BASIC_AUTHENTICATION.

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

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

○       Authentication using a client certificate

With this type of authentication, you must replace the http prefix with httpsin the URL/Destination input field (see Using Client Certificates for User Authentication).

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 certificate, SSL encryption only), DFAULT (standard certificate of an SAP system), or the name of the SSL client PSE to be used (see also SSL Client PSEs).

Save your changes.

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

Checking the Configuration (Optional)

       6.      Call transaction RZ20 in CEN.

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

  Monitoring with the Generic Request and Message Generator start page