This action might not be possible to undo. Are you sure you want to continue?
EP 6.0 Portal
Introduction to CCMS EP Monitoring Infrastructure Central Computer Monitoring System Integration of SAP Solution Manager
© SAP AG 2004, TEP12, 1
Introduction EP 6.0 Portal Starting & Stopping J2EE and EP Monitoring, Logging & Tracing Support Desk Configuration Management Incident and Problem Management Change Control Software Change Management Backup & Recovery Operations Handbook Introduction to CCMS EP Monitoring Infrastructure Computing Center Management System Solution Manager
© SAP AG 2004, TEP12, 2
Overview: Unit Objectives
At the conclusion of this unit, you will be able to: Describe fundamental concepts and terms of the CCMS monitoring infrastructure Set up useful CCMS monitors Customize thresholds and notifications Activate the Central Performance History (CPH) Run some further CCMS expert fine tuning
© SAP AG 2004, TEP12, 3
TEP12.20 SAP Web Application Server SAP Web Application Server Push SAP Instance SAP Instance SAPCCM3X Shared Memory Segment SAP Instance SAP Instance SAPCCM4X Shared Memory Segment © SAP AG 2004.CCMS Monitoring Architecture Overview Non-SAP Component Non-SAP Component Shared Memory Segment Other SAP Components (EP6.0) Other SAP Components (EP6.0) SAPCCMSR SAPCCMSR Push Shared Memory Segment Central Monitoring SAP Solution Manager 3rd Party Tools SAP Web AS ≥ 6. 4 .
5 .CCMS Monitoring Architecture Details CCMS Alert Monitor Solution Manager Analysis Method 3rd Party Product 3rd Party Product Administration AutoReaction Method A P II AP Data Display Data Storage Monitoring Attribute Monitoring Attribute Monitoring Attribute Local Shared Memory Segments Local Shared Memory Segments Monitoring Attribute Monitoring Attribute DB Data Collection Data Data Supplier Supplier DB Data Data Supplier Supplier OS OS Data Data Supplier Supplier ABAP Data Data Supplier Supplier J2EE Data Data Supplier Supplier NonSAP © SAP AG 2004. TEP12.
CCMS Expert Transaction RZ20 SAP Monitor collections: . 6 .Immediately usable non-changeable template Monitoring Attribute Monitoring Attribute Monitoring Attribute Monitoring Segment © SAP AG 2004.Different predefined views on the same data .Immediately usable non-changeable template SAP Monitors: . TEP12.
7 .CCMS Monitor: Terminology View Monitoring Tree Elements All tree nodes Monitoring Objects Represent one physical or logical object Summarize alerts and propagate them to higher nodes Monitoring Attributes Receive data and may create alerts Use data for analysis alerts © SAP AG 2004. TEP12.
but no transport possible! CPU CPU Properties Variant Y Properties Variant X Utilization Utilization Attribute group "CPU_Utilization" Thresholds definable for the group Utilization Utilization Threshold values Threshold values green <-> yellow green <-> yellow yellow <-> red yellow <-> red Attribute group: Container for similar MTEs with respect to MTE thresholds © SAP AG 2004.Thresholds and Attribute Groups <SID> <hostX>_<SID>_<no> <hostY>_<SID>_<no> Operating System Operating System Thresholds can be set for each performance monitoring attribute. 8 . TEP12.
9 .How to Determine the Attribute Group Choose “Properties” 1. Mark MTE Attribute group name © SAP AG 2004. TEP12.
Methods MTE MTE MTE MTE MTE MTE MTE MTE Data collection method Auto-reaction method Analysis method What collects the data? What is done in case of an alert? How to analyse an alert? MTE © SAP AG 2004. 10 . TEP12.
but no transport possible! CPU CPU Properties Variant Y Properties Variant X Utilization Utilization Threshold values green <-> yellow yellow <-> red MTE class "CPU_Utilization" Method assignment for the group MTE class: Container for similar MTEs with respect to method assignments © SAP AG 2004. TEP12.Methods and MTE Classes <SID> Methods can be passed to lower levels <hostX>_<SID>_<no> <hostY>_<SID>_<no> Operating System Operating System Methods definable for each node. 11 .
TEP12. Mark MTE Methods © SAP AG 2004.How to Determine MTE Class and Methods Choose “Properties” MTE class name 1. 12 .
you have to to set up and fine tune CCMS: Register the complete SAP solution landscape Set up central monitors for the complete SAP solution landscape Customize thresholds Customize an automatic notification procedure in case of an alert Activate CPH for collecting CCMS monitoring infrastructure data for long time storage and analysis © SAP AG 2004. To achieve this.Overview: Business Scenario The main JAVA supportability features are activated at customer site. The customer wants to use additional CCMS functionality. 13 . TEP12.
14 .CCMS EP 6.0 Portal CCMS Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH Fine-tuning © SAP AG 2004. TEP12.
no alerting. No useful monitors. but not the customer! No central monitoring of the complete system landscape (besides EP). Do some valuable fine tuning. Check thresholds and configure auto-reactions. 15 . Create your own monitors. © SAP AG 2004. Activate Central Performance History for long term CCMS data storage. RZ20 is full of alerts. TEP12. Solution: Setup central CCMS monitoring! Register complete system landscape at CEN.Roadmap Precondition: JSTF features are installed and ready for use. no notification. Problem: SAP Support is satisfied.
CCMS Customizing EP 6. 16 . TEP12.0 Portal CCMS Customizing Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH Fine-tuning © SAP AG 2004.
TEP12. 17 .Central Monitoring of ABAP Components Central Monitoring SAP Instance Local Monitoring RFC RZ20 Shared Memory RFC © SAP AG 2004.
18 .Steps to include remote SAP systems Create 2 RFC connections via SM59 from the central monitoring system to the remote SAP system: One for data transfer. user type CPIC (or Communications)/ System in the remote system One for remote analysis. TEP12. without user entry. mark Current user Register the SAP system in CEN via RZ21 Technical infrastucture Create remote monitoring entry Adapt monitors in RZ20 to include MTEs from the remote SAP system © SAP AG 2004.
Setup RFC Connections via SM59 RFC connection for data transfer RFC connection for analysis © SAP AG 2004. TEP12. 19 .
TEP12.Registering ABAP Components in CEN Choose "Save" to include the remote SAP system T70CLNT400_DATA T70CLNT400_ANALYSIS RFC connections for data transfer and analysis © SAP AG 2004. 20 .
Creating System Groups Transaction RZ21 The groups can be used in rule-based monitor definitions! Use right mouse button or icons to create groups or to add systems to groups © SAP AG 2004. TEP12. 21 .
TEP12. 22 .CCMS Customizing EP 6.0 Portal CCMS Customizing Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH Fine-tuning © SAP AG 2004.
© SAP AG 2004. No monitoring data of remote components is displayed. but: The information is distributed across several monitors. Create your own monitors that show only data crucial to YOUR business. TEP12. 23 . Solution: Create your own monitors! Create your own monitor sets.Motivation Precondition: All important components are registered at CEN. Problem: There is a lot of important information visible in CEN. Important data is not obvious. A monitor shows a lot of less important data and alerts.
TEP12. 24 . Activate maintenance function 2. Choose "create" Note: SAP monitors and monitor sets should not be changed! © SAP AG 2004.Creating an Own Monitor Set (Part 1) 1.
25 . Your new monitoring set is ready for use! © SAP AG 2004.Creating an Own Monitor Set (Part 2) 3. "New monitor set" is selected 4. Enter name and visibility options. Do not use names beginning with "SAP"! 5. TEP12.
TEP12.Defining Monitors (Part 1) 1. Mark your monitor set 2. 26 . Choose "Create" © SAP AG 2004.
TEP12.Defining Monitors (Part 2) Add new node Monitor name Virtual node Rule node with rule parameters Existing MTEs of registered systems © SAP AG 2004. 27 .
TEP12.Example: Static Monitor Static monitor for watching R/3 buffers Simply mark the nodes of interest © SAP AG 2004. 28 .
Overcoming the Restrictions of Static Monitoring Disadvantages of static monitors: Many nodes to select in large system landscapes Only active components can be selected Maintenance of the layout necessary after inserting new remote systems into the monitoring architecture Idea: Use arguments for pre-defined rules to specify which nodes to display The monitoring architecture checks the result of rules each time a monitor is called © SAP AG 2004. 29 . TEP12.
a system group. <ALL>. 30 .Rule: CCMS_GET_MTE_BY_CLASS CCMS_GET_MTE_BY_CLASS determines MTEs by their class name and uses these names as virtual nodes Parameters: . or <CURRENT> . TEP12.R3System: any connectred SAP System.MTEClass: name of the MTE class that can be found in RZ20 (click on MTE Properties) © SAP AG 2004.
Example: Setup of an Overall Availability Monitor How to create an overall availability monitor: Create a monitor set Create a monitor structure proposal: What exactly should be displayed? Is there an existing availability monitor template? Is there availability information contained in RZ20 (Monitor System / All Monitoring Segments / All Monitoring Contexts)? Create the new monitor using two SAPGUI modes in parallel Copy MTE class names Be careful: what is the R3system? © SAP AG 2004. 31 . TEP12.
Example: Setup of an Overall Availability Monitor © SAP AG 2004. TEP12. 32 .
please feel free to send the XML monitor definition to: ccms@sap. TEP12.com © SAP AG 2004. 33 .Monitor Examples Some examples for highly useful monitors: Availability Complete JAVA / EP related information Complete configuration information (including SAP WebAS) JARM performance data If you have designed highly useful monitors on your own.
EP 6.0 Portal
Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH Fine-tuning
© SAP AG 2004, TEP12, 34
Precondition: You have set up your own monitors.
Problem: The online monitoring data is alright, but:
The monitor is full of alerts, although there is no problem. Severe problems do not raise alerts.
Solution: Check SAP default threshold settings!
Check the thresholds for MTEs included in your monitors. Check thresholds for CEN MTEs only. If necessary, thresholds can be transported to remote components. Neglect alerts for unimportant MTEs. They are completed automatically.
© SAP AG 2004, TEP12, 35
Threshold Customizing Using RZ20 (1)
1. Select the node
2. Choose “Properties”
© SAP AG 2004, TEP12, 36
37 . Customize threshold values © SAP AG 2004. Choose “Change” Name of the attribute group 4. TEP12.Threshold Customizing Using RZ20 (2) 3.
TEP12.Alert Handling: History and Current View Switch between views Current History © SAP AG 2004. 38 .
Alert Handling: Display Alerts Double-clicking a node shows all corresponding alerts © SAP AG 2004. 39 . TEP12.
Alert Handling: Remove the Alert Cause 1. 40 . Select the alert 2. TEP12. Start the analysis method © SAP AG 2004.
Alert Handling: Example of an Analysis Method Analysis method: drilling down to the monitored component © SAP AG 2004. 41 . TEP12.
TEP12. 42 .Alert Handling: Complete Alerts Alert cause resolved: Complete the alert © SAP AG 2004.
Trace your daily administrative work Activate CPH (described later) Look for additional information (Performance analysis information. Best Practices..How or What… Checking thresholds is easy! But what is the right threshold? Which thresholds should be used? Use SAP performance transactions Ask some experts. Check all attribute groups used in your monitors: Are the SAP threshold settings appropriate? © SAP AG 2004. 43 . TEP12....
These interfaces are used by third party products to connect to SAP. An auto-reaction may be a notification of the person in charge or triggering an OS script. The connection might be cost intensive. but: SAP should react automatically and immediately. The customer is not willing to poll for alerts. SNMP could be a low cost bridge between SAP and the third party product. 44 . There is a third party alert tool already in action. alerts are raised only in case of severe problems. There are several interfaces available to read out CCMS monitoring data.Motivation Precondition: You have checked the thresholds! Problem: Now. How to connect SAP and the tool? Solution: Configure auto-reactions! They are triggered automatically in case of an alert. © SAP AG 2004. TEP12.
0 SAP instance SAPCM3X Shared Memory Segment Central Alert Notification Push SAP Web Application Server SAP instance SAPCCM4X Shared Memory Segment © SAP AG 2004.20 SAP5 SNMP Trap SAP Basis ≥ 3.Auto-Reactions Non-SAP component SAPCCMSR Shared Memory Segment SAPCCMSR Other SAP component Shared Memory Segment Push Central Monitoring SAP Web AS ≥ 6. TEP12. 45 .
maximum Definition of auto-reaction in the local system Often useful for triggering OS scripts © SAP AG 2004. Central method dispatcher SAP6 Time delay depending on batch availability in CEN Definition of auto-reaction in CEN only Often useful for notification: notification channels have to be configured in CEN only! Time delay 5 min.Local versus Central Auto-Reactions? Local auto-reactions Processed by the ABAP stack of the component No preconditions Central auto-reactions Processed by the ABAP stack of CEN Component is connected by usage of a CCMS agent. TEP12. 46 .
TEP12. Customize a copy of CCMS_OnAlert_Email.Steps to Implement Automatic E-Mail Notification Configuration of central e-mail notification (CEN only): Configure SAPCONNECT in client 000 for sending documents. © SAP AG 2004. an alert text is sent to the person in charge. Assign the method to all important MTE classes of the remote components. Result: In case of alerts. 47 .
Step 1: Configuring SAPConnect SAPOffice R/3 Application modules SAPscript SAPConnect SAPConnect: Configuration in transaction SCOT is described in great detail in the SAP documentation Adapter SMTP External communications Fax. TEP12. Internet © SAP AG 2004. 48 Other mail systems Other R/3 Systems . X.400.
TEP12.Step 1: Configuring SAPConnect SAPConnect node definition © SAP AG 2004. 49 .
TEP12.Step 2: Copying CCMS_OnAlert_Email © SAP AG 2004. 50 .
51 . TEP12.Step 3: Customizing the Method (1) 1. Central auto-reaction © SAP AG 2004. Local auto-reaction 2. Function module definition Where to execute? 2.
TEP12. 52 . Release as auto-reaction method © SAP AG 2004.Step 3: Customizing the Method (2) 3. Maintain parameters: ● Sender: User in client 000 ● Recipient: Can be a distribution list maintained in client 000 ● Recipient TypeID: SAP8 U – Internet mail R – R/3–R/3 mail … Office standard 4.
trigger method Z in CEN! CEN Central Alert Notification SAP Web Application Server J2EE SAPCCMSR Shared Memory Segment © SAP AG 2004.Step 4: Central Auto-Reaction Assignment Central auto-reaction assignment in CEN: If an alert is raised in system X for MTE Class Y. TEP12. 53 SAP instance SAPCCM4X Shared Memory Segment .
20/SP30 SAP Note 617547 © SAP AG 2004.Alternative: Notification via Alert Management CCMS email Sends a notification via SAPConnect Recipients are single users or a distribution list -Method CCMS_OnAlert_Email available as of SAP Basis 4. 54 . various configuration possibilities Method CCMS_Send_Alert_to_ALM available as of 6.6b SAP9 SAP Note 176492 Alert management Sends a notification to a central alert management Fixed or role based recipient assignment Escalation mechanism. TEP12.
55 .Sending SNMP Traps 3rd Party System Management Trap is sent to 3rd party Trapsend is triggered trapsend CEN Alert is pushed to CEN J2EE SAPCCMSR Shared Memory Segment © SAP AG 2004. TEP12.
SNMP Configuration Configuration of SNMP (CEN only): Copy SNMP executables to CEN executable directory. an SNMP trap is sent to your 3rd party tool. 56 . If required. configure your 3rd party tool! Result: In case of alerts. TEP12. Customize a copy of CCMS_OnAlert_SNMP_TRAP Assign the method to all important MTE classes of the remote components. © SAP AG 2004.
0 Portal CCMS Customizing Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH (Central Performance History) Fine-tuning © SAP AG 2004. 57 .CCMS Customizing EP 6. TEP12.
© SAP AG 2004. how long data should be stored before aggregating. Solution: Activate the Central Performance History! Customize.Motivation Problem: CCMS monitoring data is overwritten periodically. TEP12. which data should be stored centrally. Customize. No history reporting. 58 . because the data is kept in the Shared Memory: No long time storage.
TEP12.0 SAP instance Monitoring Segment © SAP AG 2004.20 SAP Basis ≥ 3.New Features at a Glance: CPH Non-SAP component Monitoring Segment Non-SAP-Basis component Monitoring Segment Central Monitoring Central Performance History SAP Web Application Server ≥ 4.0 SAP instance Monitoring Segment SAP Web AS ≥ 6. 59 .
60 . Is accessible from the Alert Monitor. Monitoring data slots are continuously overwritten. TEP12. © SAP AG 2004. and hourly monitoring data. Long-term performance history reporting (SLA reporting) is needed. Supports the export of reported data to OS level. Handles minute. Features and Advantages: Centrally collects monitoring data of the complete system landscape in a performant way. Offers configurable.New Features at a Glance: CPH Why does one need a CPH? The size of the monitoring segments is limited. Provides reorganization. scheduled reporting. quarter-hourly.
CPH Activation 3. Schedule periodic collection (and aggregation) job Monitoring Segment C PH 2. Define. how long an aggregate in a certain resolution should be stored © SAP AG 2004. Define. 61 . which data should be collected 1. TEP12.
TEP12.Defining Collection and Reorganization Schema Define. how long an aggregate in a certain resolution should be stored © SAP AG 2004. 62 .
TEP12. which data should be collected using RZ20 © SAP AG 2004.Data Selection via RZ20 Define. 63 .
Data Selection via RZ23N (Advanced Method) © SAP AG 2004. TEP12. 64 .
Data export © SAP AG 2004. Reporting CP H 2. 65 . TEP12. Data aggregation 2.CPH: Continuous Processing 1.
1970 31. TEP12.1970 Day aggregates with hour resolution Jan.1.1.1970 1. 1970 0:00 6:00 12:00 18:00 23:00 0:00 6:00 12:00 18:00 23:00 0:00 6:00 12:00 18:00 23:00 © SAP AG 2004.1970 31.1970 2. 1970 Feb.1.1.1.Data Aggregation: Example 1. 66 . 1970 Month aggregate with hour resolution Mar.
.. ...... Day Wanted in Report: Week aggr.... hour res........... Day aggr.... ... 67 ..... on the fly processing Week aggr....... aggr............ . hour res..... hour res.. Day aggr.............. hour res. ................ ...Advanced Online Reporting Using RZ23N Example: Available in DB: Day aggr... day resolution .. aggr... . weekly report ... Day ......... day resolution week 1 week 2 ...... hour res.......... TEP12. © SAP AG 2004.... ...
68 .Report Definition Screen © SAP AG 2004. TEP12.
Report Execution © SAP AG 2004. 69 . TEP12.
0 Portal CCMS Customizing Roadmap Registering other SAP Web AS Setting up CCMS monitors Customizing thresholds and notifications Activating CPH Fine-tuning © SAP AG 2004. 70 .CCMS Customizing EP 6. TEP12.
although only some are important (e. 71 . TEP12.g.ini Restart SAPCCMSR © SAP AG 2004. No way to set different thresholds for different file systems Dynamic monitors display always all monitored file systems.txt to SAPCCMSR’s config file sapccmsr.txt Enter MTE class and attribute group data Assign oscolfile. Problem: All file systems are in the same attribute group and MTE class. The process information is transferred to CEN by SAPCCMSR.Motivation Precondition: OS file systems are monitored by SAPOSCOL. database log destination). Enter file system information in a file oscolfile. Solution: SAPCCMSR filters important file systems and creates new attribute groups and MTE classes.
txt … # MonitorProcess proc NewClass NewGroup MonitorProcess *java* J2EE_CL J2EE_GR MonitorProcess *oracle* ORA_CL ORA_GR Java.exe $PROC *java* *oracle* $ monitors SAPOSCOL reads Dev_proc … Sapccmsr. 72 Oracle.Configuring SAPOSCOL Monitoring Java. TEP12.exe Oracle.ini SAPCCMSR Result J2EE_CL ORA_CL OsColFile G:\usr\sap\prfclog\sapccmsr\oscolfile.exe ORA_GR .exe J2EE_GR © SAP AG 2004.txt … reads Refers to Oscolfile.
73 .Example /oracle/C11/sapdataX /oracle/C11/saparch monitors SAPOsCol … Sapccmsr.ini SAPCCMSR Result reads OsColFile G:\usr\sap\prfclog\sapccmsr\oscolfile. TEP12.txt … # MonitorFilesystem <Name> <Pattern> [ <MTE Class> [<Group>]] MonitorFilesystem /oracle/C11/saparch ARCH_CL ARCH_GR ARCH_CL /oracle/C11/saparch ARCH_GR © SAP AG 2004.txt … Refers to Oscolfile.
TEP12.Transporting CCMS Customizing Overview of property variants RZ21: Variant Transport Variant name How to put data in a property variant is described in the next chapters! © SAP AG 2004. 74 Content of the change request .
This action might not be possible to undo. Are you sure you want to continue?