Course Structure. Introduction to CCMS. EP 6.0 Portal. EP Monitoring Infrastructure. Central Computer Monitoring System

Course Structure EP 6.0 Portal Introduction to CCMS EP Monitoring Infrastructure Central Computer Monitoring System Integration of SAP Solution Manager SAP AG 2004, TEP12, 1

Course Structure EP 6.0 Portal Introduction 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

CCMS Monitoring Architecture Overview Non-SAP Component Shared Memory Segment SAPCCMSR Push Other SAP Components (EP6.0) SAPCCMSR Shared Memory Segment SAP Solution Manager Central Monitoring SAP Web AS 6.20 3 rd Party Tools SAP Web Application Server SAP Instance Shared Memory Segment SAPCCM3X Push SAP Web Application Server SAPCCM4X SAP Instance Shared Memory Segment SAP AG 2004, TEP12, 4

CCMS Monitoring Architecture Details Analysis Method 3rd 3rd Party Party Product Product CCMS Alert Monitor Solution Manager Administration Auto- Reaction Method A P II Data Display Data Storage Monitoring Attribute Monitoring Attribute Monitoring Attribute Local Local Shared Shared Memory Memory Segments Segments Monitoring Attribute Monitoring Attribute DB Data Collection Data Data Supplier Supplier DB Data Data Supplier Supplier Data Data Supplier Supplier Data Data Supplier Supplier Data Data Supplier Supplier OS ABAP J2EE Non- SAP SAP AG 2004, TEP12, 5

CCMS Expert Transaction RZ20 SAP Monitor collections: - Immediately usable non-changeable template SAP Monitors: - Different predefined views on the same data - Immediately usable non-changeable template Monitoring Attribute Monitoring Attribute Monitoring Attribute SAP AG 2004, TEP12, 6 Monitoring Segment

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, 7

Thresholds and Attribute Groups <SID> <hostx>_<sid>_<no> Operating System <hosty>_<sid>_<no> Operating System Thresholds can be set for each performance monitoring attribute, but no transport possible! CPU CPU Utilization Utilization Attribute group "CPU_Utilization" Thresholds definable for the group Utilization Utilization Threshold Threshold values values green green <-> <-> yellow yellow yellow yellow <-> <-> red red Properties Variant X Properties Variant Y Attribute group: Container for similar MTEs with respect to MTE thresholds SAP AG 2004, TEP12, 8

How to Determine the Attribute Group Choose Properties 1. Mark MTE Attribute group name SAP AG 2004, TEP12, 9

Methods 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? SAP AG 2004, TEP12, 10

Methods and MTE Classes <SID> Methods can be passed to lower levels <hostx>_<sid>_<no> Operating System <hosty>_<sid>_<no> Operating System Methods definable for each node, but no transport possible! CPU CPU Utilization MTE class "CPU_Utilization" Method assignment for the group Utilization Threshold values green <-> yellow yellow <-> red Properties Variant X Properties Variant Y MTE class: Container for similar MTEs with respect to method assignments SAP AG 2004, TEP12, 11

How to Determine MTE Class and Methods 1. Mark MTE Choose Properties MTE class name Methods SAP AG 2004, TEP12, 12

Overview: Business Scenario The main JAVA supportability features are activated at customer site. The customer wants to use additional CCMS functionality. To achieve this, 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, TEP12, 13

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, 14

Roadmap Precondition: JSTF features are installed and ready for use. Problem: SAP Support is satisfied, but not the customer! No central monitoring of the complete system landscape (besides EP). RZ20 is full of alerts. No useful monitors, no alerting, no notification. Solution: Setup central CCMS monitoring! SAP AG 2004, TEP12, 15 Register complete system landscape at CEN. Create your own monitors. Check thresholds and configure auto-reactions. Activate Central Performance History for long term CCMS data storage. Do some valuable fine tuning.

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, TEP12, 16

Central Monitoring of ABAP Components Central Monitoring SAP Instance Local Monitoring RFC RZ20 Shared Memory RFC SAP AG 2004, TEP12, 17

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, 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, TEP12, 18

Setup RFC Connections via SM59 RFC connection for data transfer RFC connection for analysis SAP AG 2004, TEP12, 19

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, TEP12, 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

Motivation Precondition: All important components are registered at CEN. Problem: There is a lot of important information visible in CEN, but: The information is distributed across several monitors. A monitor shows a lot of less important data and alerts. Important data is not obvious. No monitoring data of remote components is displayed. Solution: Create your own monitors! Create your own monitor sets. Create your own monitors that show only data crucial to YOUR business. SAP AG 2004, TEP12, 23

Creating an Own Monitor Set (Part 1) 1. Activate maintenance function 2. Choose "create" Note: SAP monitors and monitor sets should not be changed! SAP AG 2004, TEP12, 24

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. Your new monitoring set is ready for use! SAP AG 2004, TEP12, 25

Defining Monitors (Part 1) 1. Mark your monitor set 2. Choose "Create" SAP AG 2004, TEP12, 26

Defining Monitors (Part 2) Add new node Monitor name Virtual node Rule node with rule parameters Existing MTEs of registered systems SAP AG 2004, TEP12, 27

Example: Static Monitor Static monitor for watching R/3 buffers Simply mark the nodes of interest SAP AG 2004, TEP12, 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, TEP12, 29

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: - R3System: any connectred SAP System, a system group, <ALL>, or <CURRENT> - MTEClass: name of the MTE class that can be found in RZ20 (click on MTE Properties) SAP AG 2004, TEP12, 30

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, TEP12, 31

SAP AG 2004, TEP12, 32 Example: Setup of an Overall Availability Monitor

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, please feel free to send the XML monitor definition to: ccms@sap.com SAP AG 2004, TEP12, 33

Motivation 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 SAP4

Threshold Customizing Using RZ20 (2) 3. Choose Change Name of the attribute group 4. Customize threshold values SAP AG 2004, TEP12, 37

Alert Handling: History and Current View Switch between views Current History SAP AG 2004, TEP12, 38

Alert Handling: Display Alerts Double-clicking a node shows all corresponding alerts SAP AG 2004, TEP12, 39

Alert Handling: Remove the Alert Cause 1. Select the alert 2. Start the analysis method SAP AG 2004, TEP12, 40

Alert Handling: Example of an Analysis Method Analysis method: drilling down to the monitored component SAP AG 2004, TEP12, 41

Alert Handling: Complete Alerts Alert cause resolved: Complete the alert SAP AG 2004, TEP12, 42

How or What Checking thresholds is easy! But what is the right threshold? Which thresholds should be used? Use SAP performance transactions Asksomeexperts... Trace your daily administrative work Activate CPH (described later) Look for additional information (Performance analysis information, Best Practices... Check all attribute groups used in your monitors: Are the SAP threshold settings appropriate? SAP AG 2004, TEP12, 43

Motivation Precondition: You have checked the thresholds! Problem: Now, alerts are raised only in case of severe problems, but: SAP should react automatically and immediately. The customer is not willing to poll for alerts. There is a third party alert tool already in action. How to connect SAP and the tool? Solution: Configure auto-reactions! They are triggered automatically in case of an alert. An auto-reaction may be a notification of the person in charge or triggering an OS script. There are several interfaces available to read out CCMS monitoring data. These interfaces are used by third party products to connect to SAP. The connection might be cost intensive. SNMP could be a low cost bridge between SAP and the third party product. SAP AG 2004, TEP12, 44

Auto-Reactions Non-SAP component Shared Memory Segment SAPCCMSR Push SAPCCMSR Other SAP component Shared Memory Segment SAP5 SNMP Trap Central Monitoring SAP Web AS 6.20 Central Alert Notification SAP Basis 3.0 SAP instance Shared Memory Segment SAPCM3X Push SAP Web Application Server SAPCCM4X SAP instance Shared Memory Segment SAP AG 2004, TEP12, 45

Local versus Central Auto-Reactions? Local auto-reactions Processed by the ABAP stack of the component No preconditions Time delay 5 min. maximum Definition of auto-reaction in the local system Often useful for triggering OS scripts Central auto-reactions Processed by the ABAP stack of CEN Component is connected by usage of a CCMS agent. Central method dispatcher 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! SAP6 SAP AG 2004, TEP12, 46

Steps to Implement Automatic E-Mail Notification Configuration of central e-mail notification (CEN only): Configure SAPCONNECT in client 000 for sending documents. Customize a copy of CCMS_OnAlert_Email. Assign the method to all important MTE classes of the remote components. Result: In case of alerts, an alert text is sent to the person in charge. SAP AG 2004, TEP12, 47

Step 1: Configuring SAPConnect SAPOffice SAPConnect R/3 Application modules SAPscript SAPConnect: Configuration in transaction SCOT is described in great detail in the SAP documentation Adapter SMTP External communications Fax, X.400, Internet Other mail systems Other R/3 Systems SAP AG 2004, TEP12, 48

Step 1: Configuring SAPConnect SAPConnect node definition SAP AG 2004, TEP12, 49

SAP AG 2004, TEP12, 50 Step 2: Copying CCMS_OnAlert_Email

Step 3: Customizing the Method (1) 1. Function module definition Where to execute? 2. Local auto-reaction 2. Central auto-reaction SAP AG 2004, TEP12, 51

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: U Internet mail R R/3 R/3 mail Office standard SAP8 4. Release as auto-reaction method SAP AG 2004, TEP12, 52

Step 4: Central Auto-Reaction Assignment Central auto-reaction assignment in CEN: If an alert is raised in system X for MTE Class Y, trigger method Z in CEN! CEN Central Alert Notification SAP Web Application Server J2EE Shared Memory Segment SAPCCMSR SAPCCM4X SAP instance Shared Memory Segment SAP AG 2004, TEP12, 53

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.6b SAP Note 176492 SAP9 Alert management Sends a notification to a central alert management Fixed or role based recipient assignment Escalation mechanism; various configuration possibilities Method CCMS_Send_Alert_to_ALM available as of 6.20/SP30 SAP Note 617547 SAP AG 2004, TEP12, 54

Sending SNMP Traps 3rd Party System Management Trap is sent to 3 rd party Trapsend is triggered trapsend CEN Alert is pushed to CEN SAPCCMSR Shared Memory Segment J2EE SAP AG 2004, TEP12, 55

SNMP Configuration Configuration of SNMP (CEN only): Copy SNMP executables to CEN executable directory. Customize a copy of CCMS_OnAlert_SNMP_TRAP Assign the method to all important MTE classes of the remote components. If required, configure your 3rd party tool! Result: In case of alerts, an SNMP trap is sent to your 3rd party tool. SAP AG 2004, TEP12, 56

CCMS Customizing EP 6.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, TEP12, 57

Motivation Problem: CCMS monitoring data is overwritten periodically, because the data is kept in the Shared Memory: No long time storage. No history reporting. Solution: Activate the Central Performance History! Customize, how long data should be stored before aggregating. Customize, which data should be stored centrally. SAP AG 2004, TEP12, 58

New Features at a Glance: CPH Non-SAP component Monitoring Segment Non-SAP-Basis component Monitoring Segment Central Monitoring SAP Web AS 6.20 Central Performance History SAP Basis 3.0 SAP Web Application Server 4.0 SAP instance Monitoring Segment SAP instance Monitoring Segment SAP AG 2004, TEP12, 59

New Features at a Glance: CPH Why does one need a CPH? The size of the monitoring segments is limited. Monitoring data slots are continuously overwritten. Long-term performance history reporting (SLA reporting) is needed. Features and Advantages: Centrally collects monitoring data of the complete system landscape in a performant way. Handles minute, quarter-hourly, and hourly monitoring data. Provides reorganization. Is accessible from the Alert Monitor. Offers configurable, scheduled reporting. Supports the export of reported data to OS level. SAP AG 2004, TEP12, 60

CPH Activation 3. Schedule periodic collection (and aggregation) job Monitoring Segment C PH 2. Define, which data should be collected 1. Define, how long an aggregate in a certain resolution should be stored SAP AG 2004, TEP12, 61

Defining Collection and Reorganization Schema Define, how long an aggregate in a certain resolution should be stored SAP AG 2004, TEP12, 62

Data Selection via RZ20 Define, which data should be collected using RZ20 SAP AG 2004, TEP12, 63

SAP AG 2004, TEP12, 64 Data Selection via RZ23N (Advanced Method)

CPH: Continuous Processing 1. Data aggregation 2. Reporting C P H 2. Data export SAP AG 2004, TEP12, 65

Data Aggregation: Example 1.1.1970 2.1.1970 31.1.1970 1.1.1970-31.1.1970 Day aggregates with hour resolution Month aggregate with hour resolution Jan. 1970 Feb. 1970 Mar. 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, TEP12, 66

Advanced Online Reporting Using RZ23N Example: Available in DB: Wanted in Report: Day aggr. Day aggr....... hour res. hour res....... hour Day res. aggr. hour res.... Day aggr. Day aggr. hour res. Week aggr. day resolution Week aggr. day resolution on the fly processing weekly report... week 1 week 2... SAP AG 2004, TEP12, 67

SAP AG 2004, TEP12, 68 Report Definition Screen

SAP AG 2004, TEP12, 69 Report Execution

Motivation Precondition: OS file systems are monitored by SAPOSCOL. The process information is transferred to CEN by SAPCCMSR. Problem: All file systems are in the same attribute group and MTE class. No way to set different thresholds for different file systems Dynamic monitors display always all monitored file systems, although only some are important (e.g. database log destination). Solution: SAPCCMSR filters important file systems and creates new attribute groups and MTE classes. Enter file system information in a file oscolfile.txt Enter MTE class and attribute group data Assign oscolfile.txt to SAPCCMSR s config file sapccmsr.ini SAP AG 2004, TEP12, 71 Restart SAPCCMSR

Configuring SAPOSCOL Monitoring Java.exe Oracle.exe monitors SAPOSCOL reads Dev_proc $PROC *java* *oracle* $ Sapccmsr.ini OsColFile G:\usr\sap\prfclog\sapccmsr\oscolfile.txt SAPCCMSR reads Refers to J2EE_CL Result ORA_CL Oscolfile.txt # MonitorProcess proc NewClass NewGroup MonitorProcess *java* J2EE_CL J2EE_GR MonitorProcess *oracle* ORA_CL ORA_GR Java.exe Oracle.exe J2EE_GR ORA_GR SAP AG 2004, TEP12, 72

Example /oracle/c11/sapdatax /oracle/c11/saparch monitors SAPOsCol Sapccmsr.ini OsColFile G:\usr\sap\prfclog\sapccmsr\oscolfile.txt SAPCCMSR reads Refers to Result ARCH_CL /oracle/c11/saparch Oscolfile.txt # MonitorFilesystem <Name> <Pattern> [ <MTE Class> [<Group>]] MonitorFilesystem /oracle/c11/saparch ARCH_CL ARCH_GR SAP AG 2004, TEP12, 73 ARCH_GR

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! Content of the change request SAP AG 2004, TEP12, 74