Creating the Template for the Customizing
File 
Use
To start the availability monitoring of a GRMG scenario, the central monitoring system requires a Customizing file, which primarily contains information about the GRMG scenario:
· URL (or RFC destination of type HTTP) of the GRMG application that is called to perform the actual availability monitoring
· Components of which the GRMG scenario to be monitored consists
· Additional parameters that are required for the check routine for a component (such as the name of a Web shop or an additional URL)
· Name of the monitored scenario and its components in the display of the Alert Monitor
The Customizing file is a well-defined XML document, which you can edit with any XML editor or normal text editor.
When instrumenting an application, first create a template for the Customizing file. This template already contains the information about the components of the scenario and the names of the monitored objects in the alert monitor. This template must be part of the standard delivery of the application, or program-controlled generation of the template by the application must be possible.
When Customizing the GRMG Monitoring, the user must adjust the Customizing files. This usually consists of adjusting the URL that is called to perform the availability monitoring.
The central monitoring system requires the information combined in the Customizing file. To do this, the user must upload every Customizing file into the central monitoring system.
Features
The Customizing file has the following structure (in the following Customizing file, the data types of the individual tags are specified in square brackets [ ]):
</component>
..
<components>
</scenario>
..
</scenarios>
</customizing>
See also: Example Customizing File
The individual tags have the following meanings:
· Administrative information that is identical for all scenarios in the Customizing file
Tag Name |
Description |
grmgruns |
Specifies whether a GRMG infrastructure is running; if GRMG scenarios are to be executed, the element must have the value X |
runlog |
Specifies whether a log file is to be created (X); the XML element must be empty in delivered templates |
errorlog |
Specifies whether an error log is to be created (X); the XML element must be empty in delivered templates |
If runlog is set, table GRMG_RUN_LOG, which contains log entries, is filled. In the same way, if errorlog is set, table GRMG_ERROR_LOG is filled.
· Information about the scenario
A scenario combines all components that are required for the availability of the associated business process.
Tag Name |
Description |
scenname |
Technical name of the GRMG scenario; is used for the name of the MTE classes within the GRMG monitoring subtree (see Creating a Rule-Based GRMG Monitor) |
scenversion |
Version of the GRMG scenario (>0); allows the support of more than one version of a GRMG scenario
We recommend that you leave the versioning of the GRMG scenarios to the system, by leaving scenversion empty. When the Customizing file is loaded in the central monitoring system, a new version is then automatically created, if the newly loaded scenario is monitored using a new scenstarturl; otherwise, an existing scenario with the same scenstarturl is overwritten. |
sceninst |
Instance of the GRMG scenario (>0); we recommend that you use scenversion for the versioning of different scenarios, and assign the value 001 to this XML element |
scentype |
Scenario type; the following values are possible: URL: The URL is specified directly in the field SCEN_START_URL HRFC: An RFC destination of type G (HTTP connection to external server) or H (HTTP connection to ABAP system) is specified in the SCEN_START_URL field (SAP-component or non-SAP component) |
scenstarturl |
For
SCEN_TYPE=URL: For
SCEN_TYPE=HRFC: |
scenstartmod |
Name of a function module as an alternative to a URL; it is not yet supported, and should therefore contain a value such as Not Used |
scenlangu |
Language of the scenario description; since you can only specify one language for the description, specify an English description (E) |
scendesc |
Scenario description in the above language. This description is used in the monitoring architecture as the name of the context for the scenario and is displayed in the alert monitor (maximum of 26 characters)
Since there can be multiple instances for each scenario, you should make the scendesc unique by including the host name or the J2EE instance (for example, not Broadcast Message Server, but rather Broadcast Message Server on Host123). |
· Information about components
Tag Name |
Description |
compname |
Technical name of the component; is used for the name of the MTE classes within the GRMG monitoring subtree (see Creating a Rule-Based GRMG Monitor) |
compversion |
Version of the component (>0); we recommend that you leave the versioning of the GRMG scenarios to the system, by leaving compversion empty. |
comptype |
Component type; it is not yet supported, and should therefore contain a value such as Not Used |
complangu |
Language of the component description; since you can only specify one language for the description, specify an English description (E) |
compdesc |
Component description in the above language. This description is used in the monitoring architecture as the name of the component |
· Information about the parameters for components
These tags contain parameters that are required for the check routine of a component (such as the name of a Web shop or another URL).
Tag Name |
Description |
propname |
Name of a parameter that is sent in a GRMG request of a GRMG application |
proptype |
Type of the parameter to be sent |
propvalue |
Value of the parameter to be sent |
Example
Monitoring with the
Generic Request and Message Generator start page