Method dispatchers start data collection and auto-reaction methods. There are four different dispatchers:
· The background dispatcher starts all data collection methods that are executed periodically in the background process (as a job) (see also Defining, Releasing, and Transporting Methods). The associated job SAP_CCMS_MONI_BATCH_DP runs once an hour by default.
· The central system dispatcher is responsible for the central auto-reaction with which alerts from remote systems trigger an auto-reaction in the central monitoring system. The associated job is SAP_CCMS_CENSYS_DISPATCHER.
· The dialog dispatcher starts all data collection methods that are executed periodically in the dialog process (see also Defining, Releasing, and Transporting Methods).
· The agent dispatcher runs on the host of the CCMS agents SAPCCMSR and SAPCM3X. It starts data collection methods there every minute or every ten minutes, the results of which are reported to the central monitoring system.
Use this monitor to monitor the error-free execution of the data collection methods using the method dispatcher messages.
As the monitoring architecture is an infrastructure with a modular structure, problems in certain methods affect only certain monitoring tree elements (MTEs). The majority of the monitoring functions of the monitoring architecture are not affected by method errors.
This monitor starts from the error messages of the dispatcher. An alternative approach would be to start from the individual MTEs and to display errors that occur during data collection or the auto-reaction for the MTEs to which the methods are assigned. To do this, use the Technical View: Status Data Collector and the Technical View: Status Autoreaction.
Integration
This monitor displays a section of the CCMS_Selfmonitoring monitor.
Features
The monitor contains the following MTEs; the MTE class of the attributes is CCMS_Tooldispatching_Messages in each case:
MTE | Meaning | Additional Information |
Tooldispatching | Most critical message of the central system dispatcher during the last 30 minutes (the dispatcher runs centrally system landscape-wide) | CCMS Selfmonitoring Monitor for System-Wide Data |
Tooldispatching | Most critical message of the background dispatcher during the last 30 minutes (the dispatcher runs centrally system-wide) | |
Tooldispatching | Most critical message of the dialog dispatcher during the last 30 minutes (the dispatcher runs on all application servers of the monitored systems) | CCMS Selfmonitoring Monitor for Instance-Specific Data |
Tooldispatching | Most critical message of the agent dispatcher during the last 30 minutes (the dispatcher urns on the hosts on which the CCMS agents SAPCCMSR and SAPCM3X are installed) |
To obtain the newest messages of each dispatcher, select the node and choose Display Details (). The system displays the Monitoring Attributes ‑ Detail Data screen with a list of the newest messages of the dispatcher. You can use this list to find out, for example:
· Which methods run when and for how long
· The number of MTEs provided with data by each method
· Which method provides which MTEs with data (for the agent dispatcher)
· Runtime and error messages output by the started methods
Activities
To start the monitor, follow the procedure below:
...
1. Start the Alert Monitor by calling transaction RZ20, or choose CCMS ® Control/Monitoring ® Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP CCMS Technical Expert Monitor set.
3. Start the Method Dispatching monitor from the list by double-clicking it.
No comments:
Post a Comment