Configuring GRMG Monitoring
Use
To enable GRMG monitoring, you need to set up the GRMG Monitoring scenario for your .NET Runtime server nodes. You set up this scenario per portal.
Prerequisites
· The Central Monitoring System (CEN) in available in your system landscape
· Portal Runtime for .NET is installed on your host
· GRMG Customizing file grmg-customizing.xml is installed (by default, under <Portal Runtime for Microsoft.NET Installation folder >\Tools\CCMS\GRMG)
· The files com.sap.portal.dotnet.framework.sda. and com.sap.portal.dotnet.services.systems.sda are deployed in the portal
· Your portal user account has administrative rights
Procedure
...
1. Log on to the CEN system and call the GRMG transaction. The Generic Request and Message Generator screen opens.
2. To configure a new scenario, click the Upload/Download button, and upload the grmg-customizing.xml file from the available location. A new line is added to the GRMG Availability Scenarios table. If you want to modify an existing scenario, skip this step.
3. Select the line you have added (it contains PDKRTHB in the Name column, and version number in the Version column), click the Edit/Delete button, and choose Edit a Scenario.
4. In the screen that opens, edit the scenario:
a. In the Edit URL or RFC destination name box, replace Host:Port with the IP address and port number of your portal server: http://<IP Address:PortNo>/irj/ servlet/prt/portal/prtroot/com.sap.portal.dotnet.framework.PDKMonitorComp
b. Edit the scenario properties.
Scenario properties are grouped by component. The following table lists the available monitored components:
Component |
Description |
ADNTRT |
Contains properties that apply to an arbitrary .NET Runtime server node: means that a GRMG request can be directed to any .NET Runtime server node |
DNRTCMPS |
Contains properties that apply to the specific .NET Runtime server node components. It serves as a container for all components under monitoring. |
SDNTRTXX |
Contains properties of a specific .NET Runtime server node |
GRMG_RT |
Contains the authentication parameters for the portal component com.sap.portal.dotnet.framework.PDKMonitorComp that implements the actual monitoring checks. By default, it contains the user name and password of a portal administrator; however, it is possible to assign permissions for this component in the portal to another account. |
The following table lists the scenario properties that you should define for the monitoring:
Component Name |
Property Name |
Description |
Default Value |
DNRTCMPS |
SDNTRT00 |
Applies to a specific .NET Runtime node |
|
GRMG_RT |
GET_RUN_TIME |
Enables the response time reporting for the GRMG HTTP session (any value other than ‘X’ disables this option) |
X |
GRMG_RT |
LOGON_USER |
Portal logon user name |
Portal administrator user name |
GRMG_RT |
LOGON_PASSWORD |
Portal logon password |
Portal administrator password |
GRMG_RT |
USE_BASIC_AUTHENTICATION |
Specifies whether to use basic authentication (any value other than ‘X’ disables this option) |
X |
SDNTRT00 |
host |
.NET Runtime host |
localhost |
SDNTRT00 |
port |
.NET Runtime port for communication with the portal |
8050 |
The GRMG Customizing file is a template that contains scenario properties for a single .NET Runtime server node. To set up monitoring for an additional .NET Runtime node, you need to add another SDNTRTXX property to the DNRTCMPS component (where XX is 01, 02 etc.), add a component of the same name, and set its host and port properties to match the configuration parameters of this .NET Runtime node.
5. When finished, click Save, and then click Exit.
6. In the list of available scenarios, select the scenario that you have just edited, and choose Start. The Run Status column displays the scenario execution status: if the scenario was successfully executed, a green check mark is displayed there. After this, the scenario is executed periodically.
Result
You have configured and activated the GRMG Monitoring scenario for your .NET Runtime server nodes.