Rule Node: Rule Description and Use
Definition
A rule node or rule monitoring tree element specifies a rule that defines which nodes should be included in a
monitor. The monitoring architecture interprets the rule and includes monitoring tree elements in the monitor that match the selection criteria specified in the rule. The rules are regularly reinterpreted, meaning that a monitor of your own automatically matches the current system landscape. A monitor defined with rules will, for example, automatically include a newly started SAP application server. In this way, a monitor that consists of rule MTEs has the following properties: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 update if changes are made to the system landscape.
Use
When creating a rule MTE, select a predefined rule for the selection of MTEs for your new monitor. The Alert Monitor interprets this rule and selects the MTEs that match the specified selection criteria.
The available rules are:
This rule creates virtual MTEs for SAP R/3 Systems that are included in the monitor. Use this rule to set up rule-based monitoring of one or more SAP R/3 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 SAP R/3 System that is to be monitored in the corresponding monitor. Additional selection options are <ALL> (all available SAP R/3 Systems), <CURRENT> (SAP R/3 System of the Alert Monitor), and all
This rule inserts MTE classes as real nodes in the monitor. As all monitoring objects and attributes are assigned MTE classes, you can use this rule to monitor certain types of monitoring objects and attributes. For example, the monitoring attribute ResponseTime is assigned the MTE class R3DialogResponseTime. AbortedJobs is assigned the MTE class R3BPServerSpecAbortedJobs.
As all instances of a particular MTE share the same MTE class, even beyond system boundaries, you can select monitoring objects in all SAP instances and systems using the rule.
Adding MTEs by class also adds all subordinate MTEs (for example, the subordinate MTEs CPU_Utilization and 5minLoadAverage are inserted with the MTE class CPU, although these MTEs have other MTE classes).
You can display the available MTE classes using the possible entry help. As the help does not display where an MTE class appears in the monitoring tree, it can be difficult to find the desired MTE class. To find the required MTE class, open a standard monitor for the MTE in which you want to insert the monitor. Then display the MTE class of the MTE by choosing Properties.
Use these two rules together. By doing so, you obtain the same results as with the rule CCMS_GET_MTE_BY_CLASS; however, the information that you require is displayed in a more 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. You then specify the MTE class that you want to monitor as the real node in your monitor in the parameter ChildMTEClass.
The rule uses the parameters MTEClass and R3System from the superordinate rule (CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL).
This rule is largely the same as CCMS_GET_MTE_BY_CLASS; however, you can also restrict the monitoring to particular clients.
These rules are for SAP-internal use only. 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.
Display Options for MTE Nodes
When defining your own monitors, you can specify how the name of the monitoring tree element should be created when the alert monitoring tree is created. An MTE is characterized by a total of four name parts:
CEN\Host1_CEN_01\...\Dialog\ ResponseTime is the long name for 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 listed above, of which the long name consists.
Display Options for Virtual Nodes
When defining your rule MTEs, you can specify whether the monitor should display virtual nodes that emerge from this rule. To do this, use the Display Virtual Summary Nodes in the Monitor indicator on the Edit Rule Node screen.
The top node of most SAP monitor definitions is a rule node with the rule CCMS_DEFINE_R3_SYSTEMS. The monitored systems emerge from this rule as virtual summary nodes. Depending on your system landscape, we recommend the following settings:
Constraints
You cannot arrange multiple copies of a rule MTE hierarchically. The Alert Monitor displays an error message if you attempt to create a CCMS_DEFINE_R3_SYSTEMS rule MTE under another CCMS_DEFINE_R3_SYSTEMS MTE.
See Also:
The Display Virtual Summary Nodes in the Monitor indicator in
Creating and Changing Monitors