A rule node or rule monitoring tree element specifies a rule that defines which nodes are to be included in a monitor. The monitoring architecture interprets the rule and includes in the monitor the monitoring tree elements (MTEs) that fulfill the selection criteria in the rule. The rules are regularly reinterpreted, so that your own monitor automatically corresponds to the current system landscape. A monitor defined with rules will, for example, automatically include a newly started SAP application server. This means that a monitor that consists of rule MTEs has the following properties:
· The monitor automatically contains various MTEs
· The monitor retains an up-to-date status if you make changes to your system landscape
Rules allow the dynamic selection of MTEs using selection criteria. On the other hand, with static selection, you explicitly select individual MTEs. These are not updated if you make changes to the system landscapes.
When creating a rule MTE, you select a predefined rule for selecting MTEs for your new monitor. The alert monitor interprets this rule and selects the MTEs that fulfill the specified selection criteria.
The following rules are available:
This rule creates virtual MTEs for systems that have been added to the monitor. Use this rule to set up rule-based monitoring of one or more systems. Rule MTEs that you add under this MTE are created for every selected system. You can add monitoring functions by creating virtual and rule MTEs under this MTE.
The parameter R3System is the name of the system that is to be monitored in the relevant monitor. Additional selection options are: <ALL> (all available systems), <CURRENT> (system of the alert monitor) and all system groups that you have defined in your system landscape.
This rule adds MTE classes as real nodes in the monitor. Since all monitoring objects and monitoring attributes are assigned MTE classes, you can use this rule to monitor certain types of monitoring objects and monitoring attributes. For example, the monitoring attribute ResponseTime is assigned to the MTE class R3DialogResponseTime, and AbortedJobs is assigned to the MTE class R3BPServerSpecAbortedJobs.
Since all copies of a particular MTE belong to the same MTE class, even beyond system boundaries, you can use the rule to select monitoring objects in all SAP instances and systems.
All subordinate MTEs are also added with the MTE class (for example, with the MTE class CPU, the subordinate MTEs CPU_Utilization and 5minLoadAverage are also added, although these MTEs are assigned to other MTE classes).
You can use the input help to display the available MTE classes. Since the help does not show where an MTE class is displayed in the monitoring tree, it can be difficult to find the desired MTE class. To find the required MTE class, open a standard monitor to the MTE that you want to add into the monitor. Then display the MTE class of the MTE by choosing Properties.
Use these two rules together. In this way, you receive the same results as you would with the rule CCMS_GET_MTE_BY_CLASS; however, the information that you have requested is displayed in a clearly structured format.
If you choose the rule CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL, use the parameter MTEClass to include the MTE class as a virtual node in the tree. Then choose the rule CCMS_GET_MTE_BY_CLASS_UNDER_CLASS. Specify the MTE classes in the parameter ChildMTEClass that you want to monitor as real nodes in your monitor.
The rule adopts the parameters MTEClass and R3System from the higher-level rule (CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL).
We recommend that you use this rule as an alternative to the rules CCMS_GET_MTE_BY_CLASS and CCMS_GET_MTE_BY_CLASS_AS_VIRTUALdescribed above, since the performance has been significantly improved, in particular in comparison to the second rule.
You can also use the wildcard characters question mark (?) and asterisk (*) when specifying the MTE class and use the Options parameter to specify details about the desired MTE classes.
¡ To use the rule as an alternative to CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL, specify under MTEClass the MTE class that you want to include in the tree as a virtual node. The parameter 2ndMTEClass is reserved for later use; do not enter any values here. Enter the value VirtualMTE for the Options parameter. The rest of the use is identical to the rule CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL (see above).
¡ To use the rule as an alternative to CCMS_GET_MTE_BY_CLASS, enter the desired MTE class in the parameter MTEClass.
¡ Many MTE classes always come from the segment of an application server (for example, all classes with the prefix R3) or of a CCMS agent (such as all classes of the SAP J2EE Monitor Templates monitor set). If you want to know, when creating a monitor definition, whether the MTE class comes from the monitoring segment of an application server or from a CCMS agent (but only then), you can additionally specify the value OnlyAgent or NoAgent in the Options parameter. This will also improve the performance of the monitor.
¡ You can restrict the selection of MTE classes to monitoring contexts. Use the option OnlyContext to do this. If this option is set, only the monitoring contexts of the specified MTE class (parameter MTEClass) are selected.
Set MTEClass=*GRMG* and set the option OnlyContext. All monitoring contexts whose MTE class contains the character string GRMG will be displayed in the monitor.
· CCMS_GET_MTE_BY_CLASS _AND_CLIENT
This rule is largely similar to CCMS_GET_MTE_BY_CLASS; however, you can also restrict the monitoring to specific clients.
· CCMS_GET_MONITORING_SEGMENT_NAMES and CCMS_GET_MONITORING_CONTEXT_NAMES
These rules are only for internal SAP purposes. Although you can experiment with them, we recommend that you do not use them in your own monitor definitions.
This rule is reserved by SAP for later use. We recommend that you do not use it in your own monitor definitions.
When defining your own monitors, you can determine how the names of the monitoring tree elements are created when constructing the alert monitoring tree. An MTE is characterized by four name parts:
· System: the system to which the associated monitoring attribute refers
· Context: the monitoring context (the root node of a monitoring tree)
· Object : the monitoring object
· Short Name: the short name of the MTE
CEN\Host1_CEN_01\...\Dialog\ ResponseTime is the long name of the dialog response time; the monitoring object is Dialog, and the short name of the MTE is ReponseTime. When creating or editing a rule node, you can either display the long MTE name or any of the four parts of which the long name consists, which are listed above.
When defining your rule MTEs, you can define whether the monitor is to display virtual nodes, which originate from this rule. The indicator Display Virtual Summary Nodes in the Monitor on the Edit Rule Nodes screen is used for this purpose.
The top node of most SAP monitor definitions is a rule node with the rule CCMS_DEFINE_R3_SYSTEMS. This rule creates virtual summary nodes for the monitored systems. SAP recommends the following setting, depending on your system landscape:
· If you are only monitoring one system (R3System = <CURRENT> or <systemname>), another level with the system name does not provide any new information, but rather makes the monitor less clear. You should therefore deactivate the indicator Display Virtual Summary Nodes in the Monitor.
· If you are monitoring multiple systems (R3System = <ALL> or <system group>), the monitored systems should create the next level of the monitor so that the application servers of the various systems are grouped in a clearer way. You should therefore activate the indicator Display Virtual Summary Nodes in the Monitor.
You cannot organize multiple copies of a rule MTE hierarchically. The alert monitor displays an error message if you attempt to create a rule MTE CCMS_DEFINE_R3_SYSTEMS under another MTE CCMS_DEFINE_R3_SYSTEMS.