Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS
Use this rule primarily in the following cases:
- You want to display multiple MTE classes that have a common naming convention in the monitor, especially if you do not yet have the names of all of the MTE classes to be displayed when you are creating the monitor definition (see example 1).
- You want to restrict the search for MTE classes at runtime when creating the monitor to certain segment types to improve performance or clarity (see example 2).
To create a monitor, proceed as described in Creating and Changing Monitors. The figure below shows a simple rule-based monitor definition using the above rule (for information about the possible rules and display options, see Rule MTEs: Rule Descriptions and Use):
The MTE classes to be displayed for the availability of the GRMG scenarios have the naming convention GRMG_ScenAvail_<scenario name> (see Monitoring with the Generic Request and Message Generator). If you wanted to display the availability of all scenarios, you would need to enter all MTE classes without this rule. However, the names of these MTE classes are not currently available to you.
If you choose Generate Monitor (
) for this monitor definition, the following monitor is generated:
In this case, you are using the options of the rule CCMS_GET_MTE_BY_CLASS_AND_OPTIONS. Among other things, you can use the options OnlyAgent and NoAgent to define whether the MTE class must be in an agent segment or must not be in an agent segment. The Java nodes, for example, always belong to the monitoring segment of a SAPCCMSR CCMS agent (for more options, see Rule MTEs: Rule Descriptions and Use).
If you choose Generate Monitor (
) for this monitor definition, the following monitor is generated:
