Sap Ccms
2021年2月9日Download here: http://gg.gg/o95xe
*Sap Ccms Configuration
*Sap Ccms
*Sap Ccms Zabbix
*Sap Sap_ccms_dt_schedulerSkip to end of metadataGo to start of metadata
SAP CEN configuration for CCMS Alerts (Kernel 7.21 and above for satellite system) Summary:-This document contain the step by step how to configure the CEN configuration for CCMS alerts in kernel 7.21 and above of satellite systems. RZ20 SAP tcode for – CCMS Monitoring Here we would like to draw your attention to RZ20 transaction code in SAP. As we know it is being used in the SAP BC-CCM (Use Subcomponents in Basis) component which is coming under BC module (BASIS).RZ20 is a transaction code used for CCMS Monitoring in SAP.Purpose
The purpose of this page is toexplain how the work processes of an SAP instance can be monitored through the CCMS infrastructure.Overview
This page provides details about the CCMS monitoring infrastructure, specifically focused in the work process monitoring, providing details about how to find the monitoring functions and how to configure them accordingly.CCMS Transaction RZ20
The CCMS monitoring infrastructure, a solution within SAP NetWeaver, centrally monitors any IT environments - from individual systems through networked SAP NetWeaver solutions, to complex IT landscapes incorporating several hundred systems. In this section, you learn about the Alert Monitor (transaction RZ20) and its monitoring functionalities.Most of the work process monitoring functionalities can be found in transaction RZ20, by following the below path.RZ20 transaction → SAP CCMS Monitor Templates → Entire System → <SID> → Application Server → R3Services.
Monitoring Dialog Work Process Resources
By expanding the Dialog box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the dialog work process monitoring structure, as you can see below.
The MTEs for dialog work process monitoring shown above, can monitor the following resources.
Utilisation - Average usage of dialog work processes of an application serverPrivMode Utilisation - Percentage of dialog work processes in PRIV modeNumberOfWpDIA - Number of dialog work processesErrorsInWPDIA - Number of errors in dialog work processesErrorFreqInWpDIA - Number of errors in dialog work processes per minuteEndedWpDIA - Number of completed dialog work processesQueueLength - Average usage of dispatcher wait queue for dialog work processesLongRunners - Average time for long-running dialog work processesMonitoring Background Work Process Resources
By expanding the Background box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the background work process monitoring structure, as you can see below.
The MTEs for background work process monitoring shown above, can monitor the following resources.
Utilisation - Average usage of background work processes of an application serverNumberOfWpBTC - Number of background work processesErrorsInWPBTC - Number of errors in background work processesErrorFreqInWpBTC - Number of errors in background work processes per minuteEndedWpBTC - Number of completed background work processesProgramErrors - Program error when executing background jobsServerSpecificQueueLength - Number of released jobs that are waiting to be executedAbortedJobs - Terminated jobs on an application serverMonitoring Spool Work Process Resources
By expanding the Spool box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the spool work process monitoring structure, as you can see below.
The MTEs for spool work process monitoring shown above, can monitor the following resources.
Utilisation - Spool work process load percentageNumberOfWpSPO - Number of spool work processesErrorsInWpSPO - Number of errors in spool work processesErrorFreqInWpSPO - Number of errors in spool work processesEndedWpSPO - Number of completed spool work processesQueueLength - Utilized area of dispatcher queue (percentage)ServiceQueue - Utilized area of spool service queue (percentage)ServiceQueuePriv - Utilized area of spool request queue for processing in order (in %)ServiceQueuePages - Number of pages to be output in spool request queueDeviceCacheUsed - Utilized area of entire device cache (percentage)DeviceCacheFixed - Utilized area of fixed device cache (percentage)HostspoolListUsed - Utilized area of host spool request list (percentage)Sap Ccms ConfigurationMonitoring Update and Update 2 Work Process Resources
By expanding the Update box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the update V1 and V2 work process monitoring structure, as you can see below.
The MTEs for update V1 and V2 work process monitoring shown above, can monitor the following resources.
Update V1QueueTime - SAP update task V1: Average wait time in dispatcher queueUtilisation - SAP Update Task V1: Percentage load for update task work processNumberOfWpUD1 - Number of update1 work processesErrorsInWpUD1 - Number of errors in update 1 work processesErrorFreqInWpUD1 - Number of errors in update 1 work processes per minuteEndedWpUD1 - Number of completed update 1 work processes
Update V2QueueTime - SAP update task V2: Average wait time in dispatcher queueUtilisation -SAP Update Task V2: Percentage load for update task work processNumberOfWpUD2 - Number of update 2 work processesErrorsInWpUD2 - Number of errors in update 2 work processesErrorFreqInWpUD2 - Number of errors in update 2 work processes per minuteEndedWpUD2 - Number of completed update 2 work processesMonitoring Enqueue Work Process Resources
By expanding the Enqueue box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the enqueue work process monitoring structure, as you can see below.
The MTEs for enqueue work process monitoring shown above, can monitor the following resources.
QueueLength - Monitoring object enqueue server: Percentage length of the queueErrorsInWpENQ - Number of errors in enqueue work processesErrorFreqInWpENQ - Number of errors in enqueue work processes per minuteEndedWpENQ - Number of completed enqueue work processesMonitoring Scenarios Examples
*Using the MTEs called QueueLength, monitor the percentage of the dispatcher queue utilisation for that specific work process type. With this, you can proactively detect system bottleneck situations soon enough to prevent a system outage. SAP Note 15606 provides more details about the dispatcher queue overflow situations.
*Using the MTEs called Utilisation, you can proactively monitor whether all the work processes of an specific type are simultaneously occupied in the system, therefore, detecting specific scenarios where a bottleneck situation might occur, leading to requests waiting in the dispatcher queue.
*Using the MTEs called ErrorsInWp<type> you can proactively monitor whether errors occur in the work processes. These errors might point to other undesired known system misbehaviors, bringing them to your knowledge and allowing you to correct them.CCMS Auto-Reaction Methods
In the CCMS monitoring infrastructure, you can set up any MTE available in transaction RZ20 to automatically trigger email alerts in case the values reported by them meet the threshould values defined. The next chapters will explain more details about the configuration process to achieve this.Defining Threshold Values for the Monitored MTEs
The first step is to define which MTEs you want to monitor in transaction RZ20, with this, you can start to set up their thresholds accordingly, so you are alerted in the correct scenario. Follow the Adjusting the Threshold Values chapter from the Configuring Alert Triggering and Alert Reactions SAP online help documentation for a detailed step by step on how to achieve this.Defining and Assigning Auto-Reaction Methods for the Monitored MTEs
The second step to achieve this configuration is to define and assign the auto-reaction methods to the desired MTEs in the CCMS monitoring infrastructure. In order to perform this configuration, follow the steps mentioned in the Defining an Automatic Alert Notification SAP online help documentation.
Alternatively, you can choose to define Central auto-reaction methods, which will trigger the email alert from the central system instead of the local system. For this configuration, refer to the SAP online help Setting Up Central Auto-Reaction Methods for more details.Displaying MTE Performance Information Graphically
Withing the CCMS transaction RZ20, you can display the performance values shown by an specific MTE as a graphic, allowing you to make faster and more accurate analysis based on the reported data. In order to display the MTE values as a graphic, follow the below steps.
*Select the Performance MTE in RZ20.
*Click in the Display Details button.
*Select whether you want to display the last 30 minutes or 24 hour value.
*Click in the ’Display performance values graphically’ button.
*The graphic is finally shown in the below format.Related DocumentsSap CcmsRelated SAP Notes/KBAs
SAP Note 939616 - CCMS auto-reactions: Help with troubleshootingSap Ccms Zabbix
SAP Note 176492 - Automatic email when an alert occurs (RZ20)Sap Sap_ccms_dt_scheduler
SAP Note 15606 - Overflow of dispatcher request queue
Download here: http://gg.gg/o95xe
https://diarynote.indered.space
*Sap Ccms Configuration
*Sap Ccms
*Sap Ccms Zabbix
*Sap Sap_ccms_dt_schedulerSkip to end of metadataGo to start of metadata
SAP CEN configuration for CCMS Alerts (Kernel 7.21 and above for satellite system) Summary:-This document contain the step by step how to configure the CEN configuration for CCMS alerts in kernel 7.21 and above of satellite systems. RZ20 SAP tcode for – CCMS Monitoring Here we would like to draw your attention to RZ20 transaction code in SAP. As we know it is being used in the SAP BC-CCM (Use Subcomponents in Basis) component which is coming under BC module (BASIS).RZ20 is a transaction code used for CCMS Monitoring in SAP.Purpose
The purpose of this page is toexplain how the work processes of an SAP instance can be monitored through the CCMS infrastructure.Overview
This page provides details about the CCMS monitoring infrastructure, specifically focused in the work process monitoring, providing details about how to find the monitoring functions and how to configure them accordingly.CCMS Transaction RZ20
The CCMS monitoring infrastructure, a solution within SAP NetWeaver, centrally monitors any IT environments - from individual systems through networked SAP NetWeaver solutions, to complex IT landscapes incorporating several hundred systems. In this section, you learn about the Alert Monitor (transaction RZ20) and its monitoring functionalities.Most of the work process monitoring functionalities can be found in transaction RZ20, by following the below path.RZ20 transaction → SAP CCMS Monitor Templates → Entire System → <SID> → Application Server → R3Services.
Monitoring Dialog Work Process Resources
By expanding the Dialog box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the dialog work process monitoring structure, as you can see below.
The MTEs for dialog work process monitoring shown above, can monitor the following resources.
Utilisation - Average usage of dialog work processes of an application serverPrivMode Utilisation - Percentage of dialog work processes in PRIV modeNumberOfWpDIA - Number of dialog work processesErrorsInWPDIA - Number of errors in dialog work processesErrorFreqInWpDIA - Number of errors in dialog work processes per minuteEndedWpDIA - Number of completed dialog work processesQueueLength - Average usage of dispatcher wait queue for dialog work processesLongRunners - Average time for long-running dialog work processesMonitoring Background Work Process Resources
By expanding the Background box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the background work process monitoring structure, as you can see below.
The MTEs for background work process monitoring shown above, can monitor the following resources.
Utilisation - Average usage of background work processes of an application serverNumberOfWpBTC - Number of background work processesErrorsInWPBTC - Number of errors in background work processesErrorFreqInWpBTC - Number of errors in background work processes per minuteEndedWpBTC - Number of completed background work processesProgramErrors - Program error when executing background jobsServerSpecificQueueLength - Number of released jobs that are waiting to be executedAbortedJobs - Terminated jobs on an application serverMonitoring Spool Work Process Resources
By expanding the Spool box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the spool work process monitoring structure, as you can see below.
The MTEs for spool work process monitoring shown above, can monitor the following resources.
Utilisation - Spool work process load percentageNumberOfWpSPO - Number of spool work processesErrorsInWpSPO - Number of errors in spool work processesErrorFreqInWpSPO - Number of errors in spool work processesEndedWpSPO - Number of completed spool work processesQueueLength - Utilized area of dispatcher queue (percentage)ServiceQueue - Utilized area of spool service queue (percentage)ServiceQueuePriv - Utilized area of spool request queue for processing in order (in %)ServiceQueuePages - Number of pages to be output in spool request queueDeviceCacheUsed - Utilized area of entire device cache (percentage)DeviceCacheFixed - Utilized area of fixed device cache (percentage)HostspoolListUsed - Utilized area of host spool request list (percentage)Sap Ccms ConfigurationMonitoring Update and Update 2 Work Process Resources
By expanding the Update box under the R/3 Services monitoring tree, as per the iniital image, you will have accessed to the update V1 and V2 work process monitoring structure, as you can see below.
The MTEs for update V1 and V2 work process monitoring shown above, can monitor the following resources.
Update V1QueueTime - SAP update task V1: Average wait time in dispatcher queueUtilisation - SAP Update Task V1: Percentage load for update task work processNumberOfWpUD1 - Number of update1 work processesErrorsInWpUD1 - Number of errors in update 1 work processesErrorFreqInWpUD1 - Number of errors in update 1 work processes per minuteEndedWpUD1 - Number of completed update 1 work processes
Update V2QueueTime - SAP update task V2: Average wait time in dispatcher queueUtilisation -SAP Update Task V2: Percentage load for update task work processNumberOfWpUD2 - Number of update 2 work processesErrorsInWpUD2 - Number of errors in update 2 work processesErrorFreqInWpUD2 - Number of errors in update 2 work processes per minuteEndedWpUD2 - Number of completed update 2 work processesMonitoring Enqueue Work Process Resources
By expanding the Enqueue box under the R/3 Services monitoring tree, as per the initial image, you will have accessed to the enqueue work process monitoring structure, as you can see below.
The MTEs for enqueue work process monitoring shown above, can monitor the following resources.
QueueLength - Monitoring object enqueue server: Percentage length of the queueErrorsInWpENQ - Number of errors in enqueue work processesErrorFreqInWpENQ - Number of errors in enqueue work processes per minuteEndedWpENQ - Number of completed enqueue work processesMonitoring Scenarios Examples
*Using the MTEs called QueueLength, monitor the percentage of the dispatcher queue utilisation for that specific work process type. With this, you can proactively detect system bottleneck situations soon enough to prevent a system outage. SAP Note 15606 provides more details about the dispatcher queue overflow situations.
*Using the MTEs called Utilisation, you can proactively monitor whether all the work processes of an specific type are simultaneously occupied in the system, therefore, detecting specific scenarios where a bottleneck situation might occur, leading to requests waiting in the dispatcher queue.
*Using the MTEs called ErrorsInWp<type> you can proactively monitor whether errors occur in the work processes. These errors might point to other undesired known system misbehaviors, bringing them to your knowledge and allowing you to correct them.CCMS Auto-Reaction Methods
In the CCMS monitoring infrastructure, you can set up any MTE available in transaction RZ20 to automatically trigger email alerts in case the values reported by them meet the threshould values defined. The next chapters will explain more details about the configuration process to achieve this.Defining Threshold Values for the Monitored MTEs
The first step is to define which MTEs you want to monitor in transaction RZ20, with this, you can start to set up their thresholds accordingly, so you are alerted in the correct scenario. Follow the Adjusting the Threshold Values chapter from the Configuring Alert Triggering and Alert Reactions SAP online help documentation for a detailed step by step on how to achieve this.Defining and Assigning Auto-Reaction Methods for the Monitored MTEs
The second step to achieve this configuration is to define and assign the auto-reaction methods to the desired MTEs in the CCMS monitoring infrastructure. In order to perform this configuration, follow the steps mentioned in the Defining an Automatic Alert Notification SAP online help documentation.
Alternatively, you can choose to define Central auto-reaction methods, which will trigger the email alert from the central system instead of the local system. For this configuration, refer to the SAP online help Setting Up Central Auto-Reaction Methods for more details.Displaying MTE Performance Information Graphically
Withing the CCMS transaction RZ20, you can display the performance values shown by an specific MTE as a graphic, allowing you to make faster and more accurate analysis based on the reported data. In order to display the MTE values as a graphic, follow the below steps.
*Select the Performance MTE in RZ20.
*Click in the Display Details button.
*Select whether you want to display the last 30 minutes or 24 hour value.
*Click in the ’Display performance values graphically’ button.
*The graphic is finally shown in the below format.Related DocumentsSap CcmsRelated SAP Notes/KBAs
SAP Note 939616 - CCMS auto-reactions: Help with troubleshootingSap Ccms Zabbix
SAP Note 176492 - Automatic email when an alert occurs (RZ20)Sap Sap_ccms_dt_scheduler
SAP Note 15606 - Overflow of dispatcher request queue
Download here: http://gg.gg/o95xe
https://diarynote.indered.space
コメント