7/29/2019 ep portal ccms
1/20
1
SAP AG 2002, Title of Presentation, Speaker Name 1
Course St ruct ure
IntroductionEP 6.0 Portal
Overview EP 6.0 Monitoring
Overview CCMS/ Solution Manager
Installing Monitoring Infrastructure
CCMS Customizing
How to support EP 6.0
Questions & Answers
7/29/2019 ep portal ccms
2/20
2
SAP AG 2002, Title of Presentation, Speaker Name 2
At the conclusion of this unit, you will be able to:
Overv iew: Uni t Object ives
Describe fundamental concepts and terms of theCCMS monitoring infrastructure
7/29/2019 ep portal ccms
3/20
3
SAP AG 2002, Title of Presentation, Speaker Name 3
CCMS Moni to r ing Arch i tec ture Overv iew
Solution
Manager
3rd Party
Tools
Non-SAP ComponentNon-SAP Component
SAP InstanceSAP Instance SAP InstanceSAP Instance
SAP Web Application Server
EP6.0EP6.0
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
Central Monitoring
SAPWeb AS 6.20
Agent Agent
Agent Agent
SAP Web Application Server
All components with SAP Basis or SAP Web Application Server can be monitored by
their own. In all components, detailed standard monitoring transactions are available.
However, in a complex landscape it is more helpful to get a central overview first
(availability, transaction specific response times ...) and to use the system specific
analysis transactions afterwards in case of trouble.
Components with SAP Basis or SAP Web Application Server can be directly included
into a central monitoring environment using the CCMS alert monitoring architecture.
Each component collects its own monitoring data using the infrastructure and stores
it locally in the main memory. This part of the main memory is called the monitoring
segment. You can configure the size of the monitoring segment.
The central monitoring system collects the monitoring data for the components and
displays it in various views. In this way, you have a central view of the entire system
landscape. If errors occur, you can jump directly from the central monitoring systemto the appropriate component to correct a problem in a detailed analysis. The central
monitoring system should be hosted on a system with high availability and a SAP
Basis as of release 4.6C or any SAP Web Application Server.
7/29/2019 ep portal ccms
4/20
4
SAP AG 2002, Title of Presentation, Speaker Name 4
Local Shared Memory SegmentsLocal Shared Memory Segments
DB
DB
MonitoringAttribute
3rd Party Product3rd Party Product
MonitoringAttribute
DataSupplier
DataSupplier
Data
Supplier
DataSupplier
MonitoringAttribute
MonitoringAttribute
A P IA P I
AnalysisMethod
Auto-
ReactionMethod
Data
Supplier
DataSupplier
Data
Supplier
DataSupplier
Data
Supplier
DataSupplier
MonitoringAttribute
DataCollection
DataStorage
Admini-stration
CCMS Monito r ing Arch i t ec t ure Deta i l s
CCMS Alert Monitor Solution Manager
OS ABAP J2EE Non-SAP
OS
Data Display
The CCMS Alert Monitoring Architecture consists of three layers:
Data collection
SAP components are monitored by special programs called data suppliers. Data suppliers can beABAP, C, or Java programs. SAP delivers over 100 data suppliers in ABAP alone. Each data
supplier checks its component at regular intervals and stores the collected monitoring data in themain memory of its host.
Data storage
The area of the main memory that contains the monitoring data from the data supplier is called amonitoring segment. As the main memory data is always overwritten, monitoring segments can bepermanently copied to database tables. You can then analyze the data later. The data collection
and storage parts must be present locally on every component to be centrally monitored.
Administration
Data from the monitoring segments are displayed and evaluated in the central monitoring system.
SAP provides an expert tool, the CCMS Alert Monitor (transaction RZ20). Alternatively, you canuse the Solution Manager to display the data in a business process-oriented context. If the systemidentifies a problem, it can execute an autoreaction, such as informing the responsible person.
The analysis method then helps the administrator to investigate the problem.
The CCMS Alert Monitoring Infrastructure can be extended. Customers can integratetheir own components using data suppliers that they have written themselves. Third-party vendors and partners can export the monitoring data from the monitoringsegment using various interfaces.
7/29/2019 ep portal ccms
5/20
5
SAP AG 2002, Title of Presentation, Speaker Name 5
Solut ion Manager 3.1
Service Level Management
Periodic, long-term and cross-system reporting including
business processes based on SAP EarlyWatch Alert
System Moni tor ing
Real-time monitoring of business processes and systemcomponents based on the CCMS infrastructure
Business Process and In t er face Moni tor ing
Monitoring for core business processes
Covers all technical and business application-specificfunctions required for a smooth and reliable flow ofbusiness processes
Solut ion Moni tor ingSolut ion Moni tor ingSolut ion Moni tor ingSolut ion Moni tor ing
7/29/2019 ep portal ccms
6/20
6
SAP AG 2002, Title of Presentation, Speaker Name 6
CCMS Exper t Transact ion RZ20
SAP Monitors:- Different predefined
views on the same data
- Immediately usablenon-changeable
template
SAP Monitor collections:- Immediately usable
non-changeabletemplate
Monitoring Segment
MonitoringAttribute
MonitoringAttribute
MonitoringAttribute
The CCMS alert monitor consists of two transactions:
The alert monitor itself is transaction RZ20.
Global customizing settings for the alert monitor are set in transaction RZ21. SAP delivers the alert monitor with a sample of useful monitor collections and monitors.
These monitors are stable copy templates and cannot be changed. But after copying thecopied monitor can be adapted to customer needs.
Enter transaction RZ20. The entrance screen shows the available monitor collections(for example SAP CCMS Monitor templates). Choose the plus icon. Under thecollection there are several monitors (for example Entire System). There is only onephysical CCMS alert monitor. Speaking of a monitor in our context refers to a specificpart of the CCMS alert monitor. For example, the monitor Entire Systemshows thecomplete SAP system, whereas the monitor Databaserepresents only those partsrelating to database issues.
You can use the SAP monitors directly. Double-click on the monitor which shows thatpart of the SAP system which is important for your administrative work.
Nevertheless, SAP monitors only display local monitoring data. If data coming fromremote systems should be displayed, you have to set up your own monitors.
Transaction RZ21 is for global customizing of the alert monitor. Remote systems,analysis and auto-reaction methods are defined there.
7/29/2019 ep portal ccms
7/20
7
SAP AG 2002, Title of Presentation, Speaker Name 7
CCMS Moni tor : Termi nology
All tree nodes
Represent one physicalor logical object
Summarize alerts andpropagate them to highernodes
Receive data and maycreate alerts
Use data for analysisalerts
Monitoring Tree Elements
Monitoring Attributes
Monitoring Objects
View
CCMS has an object-based monitoring architecture that simplifies the task of monitoringa set of SAP systems. This monitoring architecture integrates information from theentire SAP environment and uses this data stream to present an easy-to-manageoverview of the condition of the SAP systems and their environment. The information isdisplayed in a tree-based structure.
Any node in the tree is called a Monitoring Tree Element(MTE).
The information measured is combined with monitoring attributes. Monitoring attributesare the leaf nodes of the tree. They represent physical characteristics or messagesrelated to a monitoring object.
Monitoring attributes are bundled using monitoring objects at the second-lowest level.
For each monitoring attribute, alerts are displayed, if configurable threshold conditions
are met. To view alerts, select an MTE, and choose Display alerts. You see all alerts ofthis MTE and all MTEs under the selected one. For example if you work with the monitorEntire Systemand select the alerts of the top MTE (), you see the alertsprocessed for the whole system.
The SAP system is delivered with all the tool assignments required to monitor yoursystem. However, you can maintain additional tool assignments and thresholdconditions.
7/29/2019 ep portal ccms
8/20
8
SAP AG 2002, Title of Presentation, Speaker Name 8
Thresholds and At t r ibute Groups
Operating System
CPU
UtilizationUtilization
Operating System
CPU
UtilizationThreshold valuesgreen yellow
yellow red
UtilizationThreshold valuesgreen yellow
yellow red
__
__
Properties
Vari
antX
Properties
VariantY
Attribute group "CPU_Utilization"
Thresholds can be setfor each performance
monitoring attribute,but no transport
possible!
Attribute group:Container for similar MTEs with respect to MTE thresholds
Thresholds definable for the group
To enable full functionality of the CCMS alert monitoring infrastructure (for example mailnotification in case of an alert), you should check and adapt the SAP default thresholdsettings to your needs. Instead of checking all monitoring attributes, you should firstcheck the attributes of your monitors.
Threshold customizing is easy to perform in the CCMS.
For each performance monitoring attribute node comparison values (threshold values) are defined.
These values trigger an alert, when they are exceeded.
For log attributes you can define a threshold for triggering an alert. Moreover, you can redefine SAP
default settings using log attribute filters.
For single message attributes you can more or less only define, if an alert is raised or not.
Monitoring attributes with the same physical or logical content can be grouped togetherin attribute groups. The threshold values set can be either specific to a monitoring
attribute or valid for all the nodes in an attribute group. This grouping of monitoringattributes reduces the amount of work for customizing.
In this example, the attribute group CPU_Utilization is displayed, which includes oneattribute per SAP instance.
SAPs default threshold customizing is done via attribute groups. SAP stronglyrecommends to use the attribute group mechanism, because the settings can betransported into other SAP systems using SAPs transport mechanism.
7/29/2019 ep portal ccms
9/20
9
SAP AG 2002, Title of Presentation, Speaker Name 9
How to Determine the At t r ibut e Group
1. Mark MTE
Choose Properties
Attribute groupname
You can find out the assigned attribute group by selecting an MTE, and choosingProperties.
This procedure can be time-consuming for obtaining the assigned attribute groups of theMTEs of an entire monitor. You can use the technical view Info on MTEas analternative for this purpose. You can open this view by choosing Views Info on MTE.This view displays the attribute group to which the MTE belongs (for performance,status, and log attributes).
7/29/2019 ep portal ccms
10/20
10
SAP AG 2002, Title of Presentation, Speaker Name 10
MTE
MTE
Methods
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
MTE
MTE
MTEMTE
A method is a synonym for a program, a function module, a transaction, or a URL.Methods have to be defined in transaction RZ21.
There are three types of methods that can be assigned to monitoring attributes:Data collection methods report data to the corresponding monitoring attributes.
Auto-reaction methods are executed automatically, if the threshold conditions of the monitoringattributes are met (yellow or red alerts).
Analysis methods guide the administrator into a certain action to analyze the alert situation.
To check, which method is assigned to an MTE, open the CCMS alert monitor(transaction RZ20), choose the MTE, and choose Properties. Under the Methodstab,you can see the methods assigned to the MTE.
Example: The data collection method for the monitoring attribute UsersLoggedInis
CCMS_User_Collect. This alias stands for the report RSDSUSER, which determines,how many users are connected to a certain SAP instance. There is no auto-reactionmethod assigned to this MTE. The corresponding analysis method is calledCCMS_User_Analyse. This alias stands for the report RSUSR000 (technically thetransaction AL08).
7/29/2019 ep portal ccms
11/20
11
SAP AG 2002, Title of Presentation, Speaker Name 11
Methods and MTE Classes
Methods canbe passed tolower levels
MTE class:Container for similar MTEs with respect to method assignments
CPU
Utilization
UtilizationThreshold valuesgreen yellow
yellow redMTE class "CPU_Utilization"
Method assignment for the group
__ __
Properties
Va
riantX
Properties
VariantY
Methods definablefor each node,
but no transportpossible!
Operating System Operating System
CPU
After definition and release, the method can be assigned to an MTE. There are different
types of possible method assignments:
Methods can be assigned to individual MTEs.MTEs of the same physical content are logically grouped together in MTE classes. You can assign
methods directly to MTE classes. Doing so, the methods are assigned implicitely to all MTEs of theMTE class. Assigning methods to MTE classes can reduce customizing dramatically.
Methods can be assigned to upper levels of the monitoring tree and passed to lower levels.
Method assignment can be done on a per property variant level.
SAP's default methods are assigned to MTE classes, not to individual MTEs. SAPstrongly recommends to assign methods to MTE classes, because the settings can betransported into other SAP systems using SAP's transport mechanism.
Example: An SAP system consists of several SAP instances. Each SAP instance hasthe performance counter CPU_Utilization. Instead of setting up e-mail notification foreach SAP instance, you can specify for a complete MTE class that you want to benotified at daytime. If there is only batch processing over night, you can automaticallyremove the notification method from the property variant for night processing.
7/29/2019 ep portal ccms
12/20
12
SAP AG 2002, Title of Presentation, Speaker Name 12
How to Determ ine MTE Class and Methods
1. Mark MTE
Choose Properties
MTE classname
Methods
To check the methods and MTE class assigned to an MTE, open the CCMS alert monitor(transaction RZ20), choose the MTE, and click Properties.
Under the Methodstab, you can see the methods assigned to the MTE.
In the header data you find the assigned MTE class.
This procedure can be time-consuming for obtaining the assigned MTE classes of theMTEs of an entire monitor. You can use the technical view Info on MTEas an alternativefor this purpose. You can open this view by choosing Views Info on MTE. This viewdisplays the MTE class to which the MTE belongs and the short text assigned to the MTEclass as help (usually activated using the F1 key).
7/29/2019 ep portal ccms
13/20
13
SAP AG 2002, Title of Presentation, Speaker Name 13
Por ta l Moni tor ing Features and Tools
Portal Platform provides JARM (Java Application Responsetime Measurement)
SAT (Single Activity Tracing)
GRMG application
Monitoring features LogFile Monitoring
Availability Monitoring
GRMG Heartbeat
Central Configuration Store
Parameter Reporting into CCMS
SAPJ2EE 6.20 provides Jmonapi.jar
Logging API
LogViewer available in SAP J2EE 6.20
WebAS 6.20 provides CCMS
Solution Manager
7/29/2019 ep portal ccms
14/20
14
SAP AG 2002, Title of Presentation, Speaker Name 14
Log View er Types
3 Types of Log Viewers:
Online Log Viewer, included in the Visual Administrator
Online tool where all the logs written from the Engine and therunning applications are automatically registered
Customizing the properties, switch Log Monitoring on...
Standalone Log Viewer for central Log Viewing
Consists of Log Viewer Server and Log Viewer Client. Logs from aSystem Landscape can be viewed centrally in one Standalone LogViewer Client, if one Log Viewer Server runs on every host.
Command line Log Viewer8VDJHOYEDWGHOLYHUHGZLWK6WDQGDORQH/RJ9LHZHU8VDJHOYEDWGHOLYHUHGZLWK6WDQGDORQH/RJ9LHZHU8VDJHOYEDWGHOLYHUHGZLWK6WDQGDORQH/RJ9LHZHU8VDJHOYEDWGHOLYHUHGZLWK6WDQGDORQH/RJ9LHZHU
Only for viewing local logs on console
Can be switched on while deployment
Converts binary data into human readable data
7/29/2019 ep portal ccms
15/20
15
SAP AG 2002, Title of Presentation, Speaker Name 15
J2EE
630
Host I
Online
Log Viewer
1. Onl ine Log View er
Solution I: online Log Viewer of the J2EE engine No configuration effort: Log viewer runs out of the box
Each host must be accessible by application sharing tool
If the J2EE engine is down, no log files accessible
Application SharingClient (e.g. WTS)
J2EEJ2EE
630630
Host IIHost II
OnlineOnline
Log ViewerLog Viewer
SAProuterSAProuterSAProuterSAProuter
SAP SupportSAP Support
7/29/2019 ep portal ccms
16/20
16
SAP AG 2002, Title of Presentation, Speaker Name 16
2. Standalone Log View er
Solution II: Standalone Log Viewer Server through Application Sharing Single point of access for support teams (customer, SAP)
Log files accessible, even if the J2EE engine is down
Version of the Log server can be higher that the version of the J2EE engine:
latest support features are available without changing the application
Log Viewer protocol (P4)
J2EE
6.30
Host I
Log Viewer-Server
Log Viewer-
Server
J2EE
6.30
Host II
WTServer(e.g. togetherwith Solution
Manager)
Log Viewer-Client
SAProuterSAProuterSAProuterSAProuter
SAP SupportSAP Support
7/29/2019 ep portal ccms
17/20
17
SAP AG 2002, Title of Presentation, Speaker Name 17
Standalone Log View er vs. Onl ine Log View er
Standalone
Log Viewer Client
Online LogViewer
7/29/2019 ep portal ccms
18/20
18
SAP AG 2002, Title of Presentation, Speaker Name 18
Autom ated Logf i le Moni tor ing
SolutionManager
CCMS
CEN SAP J2EE EngineLoggingAPI
Each log written by the Logging API can bescanned automatically by SAPCCMSR:
1. J2EE writes ini templates intologmon directory
2. SAPCCMSR scans logmon directoryperiodically. In case of new entries,
agent adapts logfile monitoring.
logmonCCMSagent
filefile
7/29/2019 ep portal ccms
19/20
19
SAP AG 2002, Title of Presentation, Speaker Name 19
SolutionManager
GRMGInfrastructure
EP-GRMGApplication SAP J2EE Engine
CCMS
Central MonitoringSystem
SAP System
Other ComponentsGRMGApplication
SAP Web AS
LocalCCMS
GRMGApplication
HTTP-Request
HTTP-Response
Avai l abi l i t y Moni t or ing Using GRMG: Overview
From a central monitoring system, you can monitor selected components of an SAPsolution for their availability using GRMG, the Generic Request and Message Generator.
GRMG is suitable both for monitoring technical scenarios and web-based businessscenarios.
The GRMG availability monitoring uses the alert and display functions of the CCMSmonitoring architecture to provide heartbeat information. The communication protocolused is HTTP-Post.
GRMG monitoring works as follows:
1. An XML message request is sent to a target system by the GRMG infrastructure.
2. The GRMG application in the target system performs all the tests for the availability of the monitoredcomponents or business process steps. The results of these tests are collected in the GRMG application
and combined into a GRMG response.
3. The GRMG response is sent back to the GRMG infrastructure and displayed in the Alert Monitor asheartbeat information there.
7/29/2019 ep portal ccms
20/20
SAP AG 2002, Title of Presentation, Speaker Name 20
GRMG-Moni t or i n CCMS