Introduction to CCMS EP 6.0 Portal EP Monitoring Infrastructure … · 2019. 11. 12. · ©SAP AG...
Transcript of Introduction to CCMS EP 6.0 Portal EP Monitoring Infrastructure … · 2019. 11. 12. · ©SAP AG...
-
© SAP AG 2004, TEP12, 1
Course Structure
EP 6.0 PortalIntroduction to CCMS
EP Monitoring Infrastructure
Central Computer Monitoring System
Integration of SAP Solution Manager
-
© SAP AG 2004, TEP12, 2
Course Structure
EP 6.0 PortalIntroductionStarting & Stopping J2EE and EPMonitoring, Logging & TracingSupport DeskConfiguration ManagementIncident and Problem ManagementChange ControlSoftware Change ManagementBackup & RecoveryOperations HandbookIntroduction to CCMSEP Monitoring InfrastructureComputing Center Management System Solution Manager
-
© SAP AG 2004, TEP12, 3
At the conclusion of this unit, you will be able to:
Overview: Unit Objectives
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, 4
CCMS Monitoring Architecture Overview
SAPSolution Manager
3rd PartyTools
Non-SAP ComponentNon-SAP Component
SAP InstanceSAP Instance SAP InstanceSAP Instance
SAP Web Application Server
Other SAP Components (EP6.0)Other SAP Components (EP6.0)
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Central Monitoring
SAP Web AS ≥ 6.20
SAPCCMSR SAPCCMSR
SAPCCM3X SAPCCM4X
SAP Web Application Server
Push
Push
-
© SAP AG 2004, TEP12, 5
Local Shared Memory SegmentsLocal Shared Memory Segments
DB
DB
Monitoring Attribute
3rd Party Product3rd Party Product
Monitoring Attribute
Data SupplierData
SupplierData
SupplierData
Supplier
Monitoring Attribute
Monitoring Attribute
A P IA P I
AnalysisMethod
Auto-ReactionMethod
Data SupplierData
SupplierData
SupplierData
SupplierData
SupplierData
Supplier
Monitoring Attribute
DataCollection
DataStorage
Admini-stration
CCMS Monitoring Architecture Details
CCMS Alert Monitor Solution Manager
OS ABAP J2EE Non-SAP
OS
Data Display
-
© SAP AG 2004, TEP12, 6
CCMS Expert Transaction RZ20
SAP Monitors:- Different predefined
views on the same data- Immediately usable
non-changeabletemplate
SAP Monitor collections:- Immediately usable
non-changeabletemplate
Monitoring Segment
MonitoringAttribute
MonitoringAttribute
MonitoringAttribute
-
© SAP AG 2004, TEP12, 7
CCMS Monitor: Terminology
All tree nodes
Represent one physical or logical objectSummarize alerts andpropagate them to higher nodes
Receive data and may create alertsUse data for analysisalerts
Monitoring Tree Elements
Monitoring Attributes
Monitoring Objects
View
-
© SAP AG 2004, TEP12, 8
Thresholds and Attribute Groups
Operating System
CPU
UtilizationUtilization
Operating System
CPU
UtilizationThreshold valuesgreen yellow
yellow red
UtilizationThreshold valuesgreen yellow
yellow red
__
__
Properties Variant X
Properties Variant Y
Attribute group "CPU_Utilization"
Thresholds can be setfor each performancemonitoring attribute,
but no transportpossible!
Attribute group:Container for similar MTEs with respect to MTE thresholds
Thresholds definable for the group
-
© SAP AG 2004, TEP12, 9
How to Determine the Attribute Group
1. Mark MTE
Choose “Properties”
Attribute groupname
-
© SAP AG 2004, TEP12, 10
MTE
MTE
Methods
MTE
MTE
Data collection methodAuto-reaction method
Analysis method
What collects the data?What is done in case of an alert?How to analyse an alert?
MTE
MTE
MTE
MTEMTE
-
© SAP AG 2004, TEP12, 11
Methods and MTE Classes
Methods can be passed to lower levels
MTE class:Container for similar MTEs with respect to method assignments
CPU
UtilizationUtilization
Threshold valuesgreen yellow
yellow redMTE class "CPU_Utilization"
Method assignment for the group
__ __
Properties Variant X
Properties Variant Y
Methods definablefor each node,
but no transportpossible!
Operating System Operating System
CPU
-
© SAP AG 2004, TEP12, 12
How to Determine MTE Class and Methods
1. Mark MTE
Choose “Properties”
MTE classname
Methods
-
© SAP AG 2004, TEP12, 13
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 landscapeSet up central monitors for the complete SAP solution landscapeCustomize thresholdsCustomize an automatic notification procedure in case of an alertActivate CPH for collecting CCMS monitoring infrastructure data for long time storage and analysis
-
© SAP AG 2004, TEP12, 14
CCMS
CCMS
EP 6.0 Portal
Setting up CCMS monitors
Roadmap
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH
Fine-tuning
-
© SAP AG 2004, TEP12, 15
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!
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.
-
© SAP AG 2004, TEP12, 16
CCMS Customizing
CCMS Customizing
EP 6.0 Portal
Setting up CCMS monitors
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH
Fine-tuning
Roadmap
-
© SAP AG 2004, TEP12, 17
Central Monitoring of ABAP Components
SAP Instance
RFC
RFC
RZ20
Shared Memory
Local Monitoring
Central Monitoring
-
© SAP AG 2004, TEP12, 18
Steps to include remote SAP systems
Create 2 RFC connections via SM59 from the centralmonitoring system to the remote SAP system:
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
One for data transfer; user type CPIC (or Communications)/System in the remote systemOne for remote analysis, without user entry; mark Current user
-
© SAP AG 2004, TEP12, 19
Setup RFC Connections via SM59
RFC connection for data transfer
RFC connection for analysis
-
© SAP AG 2004, TEP12, 20
Registering ABAP Components in CEN
Choose "Save" to include the remote SAP system
RFC connections for datatransfer and analysis
T70CLNT400_DATA
T70CLNT400_ANALYSIS
-
© SAP AG 2004, TEP12, 21
Creating System Groups
Transaction RZ21
Use right mouse button or icons to create groups or to addsystems to groups
The groups can beused in rule-basedmonitor definitions!
-
© SAP AG 2004, TEP12, 22
CCMS Customizing
CCMS Customizing
EP 6.0 Portal
Setting up CCMS monitors
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH
Fine-tuning
Roadmap
-
© SAP AG 2004, TEP12, 23
Motivation
Precondition: All important components are registered at CEN.
Problem: There is a lot of important informationvisible 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 crucialto YOUR business.
-
© SAP AG 2004, TEP12, 24
1. Activatemaintenance function
Creating an Own Monitor Set (Part 1)
Note: SAP monitorsand monitor sets
should not be changed!
2. Choose "create"
-
© SAP AG 2004, TEP12, 25
5. Your new monitoringset is ready for use!
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"!
-
© SAP AG 2004, TEP12, 26
Defining Monitors (Part 1)
2. Choose "Create"1. Mark your monitor set
-
© SAP AG 2004, TEP12, 27
Defining Monitors (Part 2)
Monitor name
Virtual node
Rule node with rule parameters
Existing MTEs of registered systems
Add new node
-
© SAP AG 2004, TEP12, 28
Example: Static Monitor
Static monitor for watching R/3 buffers
Simply mark thenodes of interest
-
© SAP AG 2004, TEP12, 29
Overcoming the Restrictions of Static Monitoring
Disadvantages of static monitors:Many nodes to select in large system landscapesOnly active components can be selectedMaintenance 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 displayThe monitoring architecture checks the result of rules each time a monitor is called
-
© SAP AG 2004, TEP12, 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: - R3System: any connectred SAP System, a system group,, or
- MTEClass: name of the MTE class that can be found inRZ20 (click on MTE Properties)
-
© SAP AG 2004, TEP12, 31
Example: Setup of an Overall Availability Monitor
How to create an overall availability monitor:Create a monitor setCreate 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 namesBe careful: what is the R3system?
-
© SAP AG 2004, TEP12, 32
Example: Setup of an Overall Availability Monitor
-
© SAP AG 2004, TEP12, 33
Monitor Examples
Some examples for highly useful monitors:AvailabilityComplete JAVA / EP related informationComplete 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:[email protected]
-
© SAP AG 2004, TEP12, 34
CCMS Customizing
CCMS Customizing
EP 6.0 Portal
Setting up CCMS monitors
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH
Fine-tuning
Roadmap
-
© SAP AG 2004, TEP12, 35
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 canbe transported to remote components.
Neglect alerts for unimportant MTEs. They are completedautomatically.
-
© SAP AG 2004, TEP12, 36
Threshold Customizing Using RZ20 (1)
1. Select the node 2. Choose “Properties”
SAP4
-
© SAP AG 2004, TEP12, 37
Name of the attributegroup
3. Choose “Change”
4. Customize threshold values
Threshold Customizing Using RZ20 (2)
-
© SAP AG 2004, TEP12, 38
Alert Handling: History and Current View
Current
Switch between views
History
-
© SAP AG 2004, TEP12, 39
Alert Handling: Display Alerts
Double-clicking a node showsall corresponding alerts
-
© SAP AG 2004, TEP12, 40
Alert Handling: Remove the Alert Cause
1. Select the alert 2. Start the analysis method
-
© SAP AG 2004, TEP12, 41
Alert Handling: Example of an Analysis Method
Analysis method: drilling down to the monitored component
-
© SAP AG 2004, TEP12, 42
Alert Handling: Complete Alerts
Alert cause resolved:Complete the alert
-
© SAP AG 2004, TEP12, 43
How or What…
Checking thresholds is easy! But what is the right threshold?
Which thresholds should be used? Use SAP performance transactionsAsk some experts...Trace your daily administrative workActivate CPH (described later) Look for additional information (Performanceanalysis information, Best Practices...
Check all attribute groups used in your monitors: Are theSAP threshold settings appropriate?
-
© SAP AG 2004, TEP12, 44
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 ortriggering an OS script.
There are several interfaces available to read out CCMS monitoringdata. These interfaces are used by third party products to connect toSAP. The connection might be cost intensive. SNMP could be a lowcost bridge between SAP and the third party product.
-
© SAP AG 2004, TEP12, 45
Auto-Reactions
SAP Basis ≥ 3.0 SAP Web Application Server
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Non-SAP component
SAP instance
Other SAPcomponent
SAP instance
Central Alert Notification
Central MonitoringSAP Web AS ≥ 6.20
SAPCM3X
SAPCCMSR
SAPCCM4X
SAPCCMSR
Push
Push
SAPCCM4X
SAPCCMSR
SNMPTrap
SAP5
-
© SAP AG 2004, TEP12, 46
Local versus Central Auto-Reactions?
Definition of auto-reaction in CEN only
Definition of auto-reaction in the local system
Often useful for notification:notification channels have to be configured in CEN only!
Often useful for triggering OS scripts
Time delay depending on batch availability in CEN
Time delay 5 min. maximum
Component is connected by usage of a CCMS agent.
Central method dispatcher
No preconditions
Processed by the ABAP stack of CEN
Processed by the ABAP stack of the component
Central auto-reactionsLocal auto-reactions
SAP6
-
© SAP AG 2004, TEP12, 47
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 remotecomponents.
Result:In case of alerts, an alert text is sent to the person in charge.
-
© SAP AG 2004, TEP12, 48
Step 1: Configuring SAPConnect
SAPConnect:Configuration in
transaction SCOT is described
in great detail in theSAP documentation
R/3Application
modules
SAPOffice
SAPConnect
External External communicationscommunications
Fax, X.400, InternetFax, X.400, InternetOtherOther
mail systemsmail systems Other R/3 Systems Other R/3 Systems
SAPscript
Adapter SMTP
-
© SAP AG 2004, TEP12, 49
Step 1: Configuring SAPConnect
SAPConnect node definition
-
© SAP AG 2004, TEP12, 50
Step 2: Copying CCMS_OnAlert_Email
-
© SAP AG 2004, TEP12, 51
Step 3: Customizing the Method (1)
2. Central auto-reaction
1. Function module definition
Where to execute?
2. Local auto-reaction
-
© SAP AG 2004, TEP12, 52
Step 3: Customizing the Method (2)
3. Maintain parameters:● Sender: User in client 000● Recipient: Can be a
distribution list maintainedin client 000
● Recipient TypeID:U – Internet mailR – R/3–R/3 mail… Office standard
4. Release as auto-reaction method
SAP8
-
© SAP AG 2004, TEP12, 53
Step 4: Central Auto-Reaction Assignment
SAP Web Application Server
Shared MemorySegment
SAP instance
Central Alert Notification
CEN
SAPCCM4XSAPCCM4XShared Memory
Segment
J2EESAPCCMSR
Central auto-reaction assignment in CEN:If an alert is raised in system X for MTE Class Y, trigger method Z in CEN!
-
© SAP AG 2004, TEP12, 54
Alternative: Notification via Alert Management
Method CCMS_Send_Alert_to_ALM
available as of 6.20/SP30
Method CCMS_OnAlert_Emailavailable as of SAP Basis 4.6b
SAP Note 617547SAP Note 176492
Escalation mechanism; various configuration possibilities
--
Fixed or role based recipient assignment
Recipients are single users or a distribution list
Sends a notification to a central alert management
Sends a notification via SAPConnect
Alert managementCCMS email
SAP9
-
© SAP AG 2004, TEP12, 55
Sending SNMP Traps
3rd Party System Management
CEN
Shared MemorySegment
J2EESAPCCMSR
Alert is pushed to CEN
trapsendTrapsend is triggered
Trap is sentto 3rd party
-
© SAP AG 2004, TEP12, 56
SNMP Configuration
Configuration of SNMP (CEN only):Copy SNMP executables to CEN executable directory.Customize a copy of CCMS_OnAlert_SNMP_TRAPAssign the method to all important MTE classes of theremote 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, 57
CCMS Customizing
CCMS Customizing
EP 6.0 Portal
Setting up CCMS monitors
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH (Central Performance History)
Fine-tuning
Roadmap
-
© SAP AG 2004, TEP12, 58
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 PerformanceHistory!
Customize, how long data should be stored beforeaggregating.
Customize, which data should be stored centrally.
-
© SAP AG 2004, TEP12, 59
New Features at a Glance: CPH
SAP Basis ≥ 3.0 SAP Web Application Server ≥ 4.0
Monitoring Segment
Monitoring Segment
Monitoring Segment
Monitoring Segment
Non-SAP component
SAP instance
Non-SAP-Basiscomponent
SAP instance
Central Monitoring
SAP Web AS ≥ 6.20
Central Performance History
-
© SAP AG 2004, TEP12, 60
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 landscapein 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, 61
CPH Activation
Monitoring Segment
C HP
3. Schedule periodic collection (and
aggregation) job
1. Define, how long an aggregate in a certain
resolution should be stored
2. Define, which data should be collected
-
© SAP AG 2004, TEP12, 62
Defining Collection and Reorganization Schema
Define, how long an aggregate in a certain resolution should
be stored
-
© SAP AG 2004, TEP12, 63
Data Selection via RZ20
Define, which data should be collected
using RZ20
-
© SAP AG 2004, TEP12, 64
Data Selection via RZ23N (Advanced Method)
-
© SAP AG 2004, TEP12, 65
CPH: Continuous Processing
C HP
2. Reporting1. Data aggregation
2. Data export
-
© SAP AG 2004, TEP12, 66
Month aggregate with hour resolution
Data Aggregation: Example
1.1.1970 2.1.1970 31.1.1970 1.1.1970 -31.1.1970
Jan. 1970
0:00 6:00 12:00 18:00 23:00
Feb. 1970
0:00 6:00 12:00 18:00 23:00
Mar. 1970
0:00 6:00 12:00 18:00 23:00
Day aggregates with hour resolution
-
© SAP AG 2004, TEP12, 67
Advanced Online Reporting Using RZ23N
Example:
hour res.
Day aggr.........................
hour res.
Day aggr.........................
hour res.
Day aggr.........................hour res.
Day aggr.........................
hour res.
Day aggr.........................
Available in DB: Wanted in Report:
Week aggr.
day resolution
Week aggr.
day resolution
weekly report
...
week 1week 2
...
on the flyprocessing
-
© SAP AG 2004, TEP12, 68
Report Definition Screen
-
© SAP AG 2004, TEP12, 69
Report Execution
-
© SAP AG 2004, TEP12, 70
CCMS Customizing
CCMS Customizing
EP 6.0 Portal
Setting up CCMS monitors
Customizing thresholds and notifications
Registering other SAP Web AS
Activating CPH
Fine-tuning
Roadmap
-
© SAP AG 2004, TEP12, 71
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 systemsDynamic 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
Restart SAPCCMSR
-
© SAP AG 2004, TEP12, 72
Configuring SAPOSCOL Monitoring
SAPCCMSR
SAPOSCOL
Java.exe Oracle.exe
Dev_proc
$PROC*java**oracle*$
Sapccmsr.ini…OsColFileG:\usr\sap\prfclog\sapccmsr\oscolfile.txt…
Oscolfile.txt …# MonitorProcess proc NewClass NewGroupMonitorProcess *java* J2EE_CL J2EE_GRMonitorProcess *oracle* ORA_CL ORA_GR
readsmonitors
reads Refers to
J2EE_CL
J2EE_GR
Java.exe
ORA_CL
ORA_GR
Oracle.exe
Result
-
© SAP AG 2004, TEP12, 73
Example
SAPCCMSR
SAPOsCol
/oracle/C11/sapdataX
Sapccmsr.ini…OsColFileG:\usr\sap\prfclog\sapccmsr\oscolfile.txt…
Oscolfile.txt …# MonitorFilesystem [ []]
MonitorFilesystem /oracle/C11/saparch ARCH_CL ARCH_GR
monitors
reads Refers to
ARCH_CL
ARCH_GR
Result
/oracle/C11/saparch
/oracle/C11/saparch
-
© SAP AG 2004, TEP12, 74
Transporting CCMS Customizing
Overview of property variantsRZ21: Variant Transport
Variant name
Content of thechange request
How to put data in aproperty variant
is described in thenext chapters!