GRMG Scenario Tables 
Definition
To be able to execute a GRMG scenario, you must upload the corresponding Customizing file into the central monitoring system (see Activating and Customizing Monitoring with GRMG). These Customizing settings are written to the following database tables when you do so:
Table |
Description |
GRMG_CONTROL |
Information for controlling the GRMG infrastructure (applies for all scenarios) |
GRMG_SCENARIOS |
Definition of the scenarios; contains administrative information for each scenario. This includes the technical name of the scenario and the URL that is used by the scenario for availability monitoring. |
GRMG_SCENARIO_T |
Monitoring context name for each scenario (Element scendesc); each scenario must contain a description |
GRMG_COMPONENTS |
Definition of the components to be monitored; a scenario must include at least one component |
GRMG_COMPONENT_T |
Node name for each component (Element compdesc); each component must contain a description |
GRMG_PROPERTIES |
Information about parameters that are to be sent with the GRMG request for the components of a scenario; you must specify at least one parameter for each combination of scenario and component |
You can obtain the following information from the table below:
· Which tag names of the Customizing file correspond to which field names in the database tables?
· In which of the database tables is the content written?
· Which of the corresponding fields is a key?
Tag Name |
Field Name |
Key |
Data Type |
Occurs in Tables |
grmgruns |
GRMG_RUNS |
X |
CHAR(1) |
GRMG_CONTROL |
runlog |
RUN_LOG |
X |
CHAR(1) |
GRMG_CONTROL |
errorlog |
ERROR_LOG |
X |
CHAR(1) |
GRMG_CONTROL |
scenname |
SCEN_NAME |
X |
CHAR(8) |
GRMG_
SCENARIOS |
scenversion |
SCEN_VERSION |
X |
NUMC(3) |
GRMG_
SCENARIOS |
sceninst |
SCEN_INST |
X |
NUMC(3) |
GRMG_
SCENARIOS |
scentype |
SCEN_TYPE |
|
CHAR(10) |
GRMG_ SCENARIOS |
scenstarturl |
SCEN_START_URL |
|
CHAR(250) |
GRMG_ SCENARIOS |
scenstartmod |
SCEN_START_MOD |
|
CHAR(50) |
GRMG_ SCENARIOS |
scenlangu |
SCEN_LANGU |
X |
LANG(1) |
GRMG_ SCENARIO_T |
scendesc |
SCEN_DESC |
|
CHAR(26) |
GRMG_ SCENARIO_T |
compname |
COMP_NAME |
X |
CHAR(8) |
GRMG_COMPONENTS |
compversion |
COMP_VERSION |
X |
NUMC(3) |
GRMG_COMPONENTS |
comptype |
COMP_TYPE |
|
CHAR(10) |
GRMG_COMPONENTS |
complangu |
COMP_LANGU |
X |
LANG(1) |
GRMG_COMPONENT_T |
compdesc |
COMP_DESC |
|
CHAR(20) |
GRMG_COMPONENT_T |
propname |
PROP_NAME |
X |
CHAR(40) |
GRMG_PROPERTIES |
proptype |
PROP_TYPE |
|
CHAR(3) |
GRMG_PROPERTIES |
propvalue |
PROP_VALUE |
|
CHAR(250) |
GRMG_PROPERTIES |
If the contents of one or more tables contain errors, do not correct the entries directly in the tables. Instead, solve the problem by correcting the Customizing file in transaction GRMG.
Example
Monitoring with the
Generic Request and Message Generator start page