Ep Portal Ccms

1
SAP AG 2002, Title of Presentation, Speaker Name 1

Cour se St r uc t ur e
Introduction
EP 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
2
At the conclusion of this unit, you will be able to:
Over vi ew : Uni t Obj ec t i ves
Describe fundamental concepts and terms of the
CCMS monitoring infrastructure
3
CCMS Moni t or i ng Ar c hi t ec t ur e Over vi ew
Solution
Manager
3
rd
Party
Tools
Non-SAP Component
Non-SAP Component
SAP Instance
SAP Instance
SAP Instance
SAP Instance
SAP Web Application Server
EP6.0
EP6.0
Shared Memory
Segment
Shared Memory
Segment
Shared Memory
Segment
Shared Memory
Segment
Central Monitoring
SAP
Web 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 system
to 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.
4
Local Shared Memory Segments
Local Shared Memory Segments
DB
DB
Monitoring
Attribute
3rd Party Product
3rd Party Product
Monitoring
Attribute
Data
Supplier
Data
Supplier
Data
Supplier
Data
Supplier
Monitoring
Attribute
Monitoring
Attribute
A P I
A P I
Analysis
Method
Auto-
Reaction
Method
Data
Supplier
Data
Supplier
Data
Supplier
Data
Supplier
Data
Supplier
Data
Supplier
Monitoring
Attribute
Data
Collection
Data
Storage
Admini-
stration
CCMS Moni t or i ng Ar c hi t ec t ur e Det ai 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 be
ABAP, 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 the
main memory of its host.
Data storage
The area of the main memory that contains the monitoring data from the data supplier is called a
monitoring segment. As the main memory data is always overwritten, monitoring segments can be
permanently 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 can
use the Solution Manager to display the data in a business process-oriented context. If the system
identifies 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 integrate
their own components using data suppliers that they have written themselves. Third-
party vendors and partners can export the monitoring data from the monitoring
segment using various interfaces.
5
Sol ut i on Manager 3.1
Ser vi c e Level Management
Periodic, long-term and cross-system reporting including
business processes based on SAP EarlyWatch Alert
Syst em Moni t or i ng
Real-time monitoring of business processes and system
components based on the CCMS infrastructure
Busi ness Pr oc ess and I nt er f ac e Moni t or i ng
Monitoring for core business processes
Covers all technical and business application-specific
functions required for a smooth and reliable flow of
business processes
Sol ut i on Moni t or i ng Sol ut i on Moni t or i ng Sol ut i on Moni t or i ng Sol ut i on Moni t or i ng
6
CCMS Ex per t Tr ansac t i on RZ20
SAP Monitors:
- Different predefined
views on the same data
- Immediately usable
non-changeable
template
SAP Monitor collections:
- Immediately usable
non-changeable
template
Monitoring Segment
Monitoring
Attribute
Monitoring
Attribute
Monitoring
Attribute
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 the
copied 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 the
collection there are several monitors (for example Entire System). There is only one
physical CCMS alert monitor. Speaking of a monitor in our context refers to a specific
part of the CCMS alert monitor. For example, the monitor Entire System shows the
complete SAP system, whereas the monitor Database represents only those parts
relating to database issues.
You can use the SAP monitors directly. Double-click on the monitor which shows that
part of the SAP system which is important for your administrative work.
Nevertheless, SAP monitors only display local monitoring data. If data coming from
remote 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
CCMS Moni t or : Ter mi nol ogy
All tree nodes
Represent one physical
or logical object
Summarize alerts and
propagate them to higher
nodes
Receive data and may
create alerts
Use data for analysis
alerts
Monitoring Tree Elements
Monitoring Attributes
Monitoring Objects
View
CCMS has an object-based monitoring architecture that simplifies the task of monitoring
a set of SAP systems. This monitoring architecture integrates information from the
entire SAP environment and uses this data stream to present an easy-to-manage
overview of the condition of the SAP systems and their environment. The information is
displayed 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 attributes
are the leaf nodes of the tree. They represent physical characteristics or messages
related 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 of
this MTE and all MTEs under the selected one. For example if you work with the monitor
Entire System and select the alerts of the top MTE (<SID>), you see the alerts
processed for the whole system.
The SAP system is delivered with all the tool assignments required to monitor your
system. However, you can maintain additional tool assignments and threshold
conditions.
8
Thr eshol ds and At t r i but e Gr oups
Operating System
CPU
Utilization
Utilization
Operating System
CPU
Utilization
Threshold values
green <-> yellow
yellow <-> red
Utilization
Threshold values
green <-> yellow
yellow <-> red
<hostX>_<SID>_<no>
<SID>
<hostY>_<SID>_<no>
P
r
o
p
e
r
t
i
e
s

V
a
r
i
a
n
t

X
P
r
o
p
e
r
t
i
e
s

V
a
r
i
a
n
t

Y
Attribute group "CPU_Utilization"
Thresholds can be set
for 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 mail
notification in case of an alert), you should check and adapt the SAP default threshold
settings to your needs. Instead of checking all monitoring attributes, you should first
check 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 together
in 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 monitoring
attributes reduces the amount of work for customizing.
In this example, the attribute group CPU_Utilization is displayed, which includes one
attribute per SAP instance.
SAPs default threshold customizing is done via attribute groups. SAP strongly
recommends to use the attribute group mechanism, because the settings can be
transported into other SAP systems using SAPs transport mechanism.
9
How t o Det er mi ne t he At t r i but e Gr oup
1. Mark MTE
Choose Properties
Attribute group
name
You can find out the assigned attribute group by selecting an MTE, and choosing
Properties.
This procedure can be time-consuming for obtaining the assigned attribute groups of the
MTEs of an entire monitor. You can use the technical view Info on MTE as an
alternative 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).
10
MTE
MTE
Met hods
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
MTE
MTE
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 monitoring
attributes 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 Methods tab,
you can see the methods assigned to the MTE.
Example: The data collection method for the monitoring attribute UsersLoggedIn is
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-reaction
method assigned to this MTE. The corresponding analysis method is called
CCMS_User_Analyse. This alias stands for the report RSUSR000 (technically the
transaction AL08).
11
Met hods and MTE Cl asses
Methods can
be passed to
lower levels
MTE class:
Container for similar MTEs with respect to method assignments
CPU
Utilization
Utilization
Threshold values
green <-> yellow
yellow <-> red
MTE class "CPU_Utilization"
Method assignment for the group
<hostX>_<SID>_<no>
<hostY>_<SID>_<no>
P
r
o
p
e
r
t
i
e
s

V
a
r
i
a
n
t

X
P
r
o
p
e
r
t
i
e
s

V
a
r
i
a
n
t

Y
Methods definable
for each node,
but no transport
possible!
<SID>
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 the
MTE 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. SAP
strongly recommends to assign methods to MTE classes, because the settings can be
transported into other SAP systems using SAP's transport mechanism.
Example: An SAP system consists of several SAP instances. Each SAP instance has
the performance counter CPU_Utilization. Instead of setting up e-mail notification for
each SAP instance, you can specify for a complete MTE class that you want to be
notified at daytime. If there is only batch processing over night, you can automatically
remove the notification method from the property variant for night processing.
12
How t o Det er mi ne MTE Cl ass and Met hods
1. Mark MTE
Choose Properties
MTE class
name
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 Methods tab, 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 the
MTEs of an entire monitor. You can use the technical view Info on MTE as an alternative
for this purpose. You can open this view by choosing Views Info on MTE. This view
displays the MTE class to which the MTE belongs and the short text assigned to the MTE
class as help (usually activated using the F1 key).
13
Por t al Moni t or i ng Feat ur es and Tool s
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
14
Log Vi ew 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 the
running 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 a
System Landscape can be viewed centrally in one Standalone Log
Viewer Client, if one Log Viewer Server runs on every host.
Command line Log Viewer
Usage: lv.bat, delivered with Standalone Log Viewer Usage: lv.bat, delivered with Standalone Log Viewer Usage: lv.bat, delivered with Standalone Log Viewer Usage: lv.bat, delivered with Standalone Log Viewer
Only for viewing local logs on console
Can be switched on while deployment
Converts binary data into human readable data
15
J2EE
630
Host I
Online
Log Viewer
1. Onl i ne Log Vi ew 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 Sharing
Client (e.g. WTS)
J2EE J2EE
630 630
Host II Host II
Online Online
Log Viewer Log Viewer
SAPr out er SAPr out er SAPr out er SAPr out er
SAP Support SAP Support
16
2. St andal one Log Vi ew 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. together
with Solution
Manager)
Log Viewer-
Client
SAPr out er SAPr out er SAPr out er SAPr out er
SAP Support SAP Support
17
St andal one Log Vi ew er vs. Onl i ne Log Vi ew er
Standalone
Log Viewer Client
Online Log
Viewer
18
Aut omat ed Logf i l e Moni t or i ng
Solution
Manager
CCMS
CEN
SAP J2EE Engine
Logging
API
Each log written by the Logging API can be
scanned automatically by SAPCCMSR:
1. J2EE writes ini templates into
logmon directory
2. SAPCCMSR scans logmon directory
periodically. In case of new entries,
agent adapts logfile monitoring.
logmon
CCMS
agent
file
file
19
Solution
Manager
GRMG
Infrastructure
EP-GRMG
Application
SAP J2EE Engine
CCMS
Central Monitoring
System
SAP System
Other Components
GRMG
Application
SAP Web AS
Local
CCMS
GRMG
Application
HTTP-
Request
HTTP-
Response
Avai l abi l i t y Moni t or i ng Usi ng GRMG: Over vi ew
From a central monitoring system, you can monitor selected components of an SAP
solution for their availability using GRMG, the Generic Request and Message Generator.
GRMG is suitable both for monitoring technical scenarios and web-based business
scenarios.
The GRMG availability monitoring uses the alert and display functions of the CCMS
monitoring architecture to provide heartbeat information. The communication protocol
used 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 monitored
components 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 as
heartbeat information there.
20
GRMG-Moni t or i n CCMS

Ep Portal Ccms

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ep Portal Ccms

Uploaded by

Copyright:

Available Formats

1

SAP AG 2002, Title of Presentation, Speaker Name 1

You might also like