bbb79990-0201-0010-cb9c-ee03abe3446f

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

1/74

SAP AG 2004, TEP12, 1

Course St ruc t ure

EP 6.0 PortalIntroduction to CCMS

EP Monitoring Infrastructure

Central Computer Monitoring System

Integration of SAP Solution Manager

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

2/74

SAP AG 2004, TEP12, 2

Course St ruc t ure

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

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

3/74

SAP AG 2004, TEP12, 3

At the conclusion of this unit, you will be able to:

Overv iew : Uni t Objec t ives

Describe fundamental concepts and terms of theCCMS monitoring infrastructure

Set up useful CCMS monitors

Customize thresholds and notifications

Activate the Central Performance History (CPH)

Run some further CCMS expert fine tuning

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

4/74

SAP AG 2004, TEP12, 4

CCMS Moni t or ing Arc h i t ec t ure Overv iew

SAPSolutionManager

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




Central Monitoring

SAPWeb AS 6.20

SAPCCMSR SAPCCMSR

SAPCCM3X SAPCCM4X


Push

Push

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

5/74

SAP AG 2004, TEP12, 5

Local Shared Memory SegmentsLocal Shared Memory Segments

DB

DB

MonitoringAttribute

3rd Party Product3rd Party Product

MonitoringAttribute

DataSupplier

DataSupplier

DataSupplier

DataSupplier

MonitoringAttribute

MonitoringAttribute

A P IA P I

AnalysisMethod

Auto-ReactionMethod

DataSupplier

DataSupplier

DataSupplier

DataSupplier

DataSupplier

DataSupplier

MonitoringAttribute

Data

Collection

Data

Storage

Admini-

stration

CCMS Mon i to r ing Arch i tec t u re Deta i l s

CCMS Alert Monitor Solution Manager

OS ABAP J2EE Non-SAP

OS

Data Display

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

6/74

SAP AG 2004, TEP12, 6

CCMS Ex per t Transac t ion RZ20

SAP Monitors:- Different predefined

views on the same data

- Immediately usablenon-changeabletemplate

SAP Monitor collections:- Immediately usable

non-changeable

template

Monitoring Segment

MonitoringAttribute

MonitoringAttribute

MonitoringAttribute

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

7/74

SAP AG 2004, TEP12, 7

CCMS Monit or : Term inology

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

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

8/74

SAP AG 2004, TEP12, 8

Thresholds and At t r ibut e Groups

Operating System

CPU

UtilizationUtilization

Operating System

CPU

UtilizationThreshold valuesgreen yellow

yellow red


yellow red

__

__

Properties

Va

riantX

Properties

VariantY

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

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

9/74

SAP AG 2004, TEP12, 9

How t o De te rm ine t he A t t r ibu te Group

1. Mark MTE

Choose Properties

Attribute group

name

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

10/74

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

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

11/74

SAP AG 2004, TEP12, 11

Met hods and MTE Classes

Methods canbe passed tolower levels

MTE class:

Container for similar MTEs with respect to method assignments

CPU

Utilization


yellow redMTE class "CPU_Utilization"

Method assignment for the group

__ __

Properties

V

ariantX

P

roperties

VariantY

Methods definablefor each node,

but no transportpossible!

Operating System Operating System

CPU

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

12/74

SAP AG 2004, TEP12, 12

How t o Det erm ine MTE Class and Met hods

1. Mark MTE

Choose Properties

MTE classname

Methods

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

13/74

SAP AG 2004, TEP12, 13

Overv iew : Business Sc enar io

The main JAVA supportability features are activated atcustomer site. The customer wants to use additionalCCMS functionality. To achieve this, you have to to set upand fine tune CCMS:

Register the complete SAP solution landscape

Set up central monitors for the complete SAP solutionlandscape

Customize thresholds

Customize an automatic notification procedure in case of analert

Activate CPH for collecting CCMS monitoring infrastructure

data for long time storage and analysis

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

14/74

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

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

15/74

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.

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

16/74

SAP AG 2004, TEP12, 16

CCMS Cus t om izing

CCMS Customizing

EP 6.0 Portal




Activating CPH

Fine-tuning

Roadmap

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

17/74

SAP AG 2004, TEP12, 17

Cent ra l Moni t or ing o f ABAP Com ponents

SAP Instance

RFC

RFC

RZ20

Shared Memory

Local Monitoring

Central Monitoring

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

18/74

SAP AG 2004, TEP12, 18

St eps to inc lude remot e SAP sys tem s

Create 2 RFC connections via SM59 from the centralmonitoring system to the remote SAP system:

Register the SAP system in CEN via RZ21 Technicalinfrastucture Create remote monitoring entry

Adapt monitors in RZ20 to include MTEs from the remote SAPsystem

One for data transfer; user type CPIC (or Communications)/System in the remote system

One for remote analysis, without user entry; mark Current user

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

19/74

SAP AG 2004, TEP12, 19

Set up RFC Connec t ions v i a SM59

RFC connection for data transfer

RFC connection for analysis

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

20/74

SAP AG 2004, TEP12, 20

Regist er ing ABA P Com ponent s in CEN

Choose "Save" to includethe remote SAP system

RFC connections for datatransfer and analysis

T70CLNT400_DATA

T70CLNT400_ANALYSIS

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

21/74

SAP AG 2004, TEP12, 21

Creat ing Syst em Groups

Transaction RZ21

Use right mouse button or iconsto create groups or to addsystems to groups

The groups can beused in rule-basedmonitor definitions!

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

22/74

SAP AG 2004, TEP12, 22

CCMS Cus t om izing

CCMS Customizing

EP 6.0 Portal




Activating CPH

Fine-tuning

Roadmap

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

23/74

SAP AG 2004, TEP12, 23

Mot iva t ion

Precondition: All important components are registered at CEN.

Problem: There is a lot of important informationvisible in CEN, but:

The information is distributed across severalmonitors.

A monitor shows a lot of less important data andalerts. 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.

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

24/74

SAP AG 2004, TEP12, 24

1. Activatemaintenance function

Creat ing an Ow n Moni t or Set (Par t 1)

Note: SAP monitorsand monitor sets

should not be changed!

2. Choose "create"

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

25/74

SAP AG 2004, TEP12, 25

5. Your new monitoringset is ready for use!

Creat ing an Ow n Moni t or Set (Par t 2)

3. "New monitor set"is selected

4. Enter name and visibility options.Do not use names beginning

with "SAP"!

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

26/74

SAP AG 2004, TEP12, 26

Def in ing Moni t ors (Par t 1)

2. Choose "Create"1. Mark your monitor set

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

27/74

SAP AG 2004, TEP12, 27

Def in ing Moni t ors (Par t 2)

Monitor name

Virtual node

Rule node with ruleparameters

Existing MTEs ofregistered systems

Add new node

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

28/74

SAP AG 2004, TEP12, 28

Ex ample : St a t ic Moni t o r

Static monitor for watching R/3 buffers

Simply mark thenodes of interest

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

29/74

SAP AG 2004, TEP12, 29

Overc o m ing t h e Rest r ic t ions of St a t ic Moni t o ring

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 remotesystems into the monitoring architecture

Idea:

Use arguments for pre-defined rules to specify whichnodes to display

The monitoring architecture checks the result of ruleseach time a monitor is called

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

30/74

SAP AG 2004, TEP12, 30

Rule: CCMS_GET_MTE_BY_CLASS

CCMS_GET_MTE_BY_CLASS determines MTEs by theirclass 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)

E l S t f O l l A i l bi l i t M i t

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

31/74

SAP AG 2004, TEP12, 31

Ex am ple: Set up o f an Overa l l Ava i labi l i t y Moni t or

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?

E l S t f O l l A i l bi l i t M i t

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

32/74

SAP AG 2004, TEP12, 32

Ex am ple: Set up o f an Overa l l Ava i labi l i t y Moni t or

Monit o r E amples

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

33/74

SAP AG 2004, TEP12, 33

Monit o r Ex amples

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:

[email protected]

CCMS Cus t om izing

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

34/74

SAP AG 2004, TEP12, 34

CCMS Cus t om izing

CCMS Customizing

EP 6.0 Portal




Activating CPH

Fine-tuning

Roadmap

Mot iva t ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

35/74

SAP AG 2004, TEP12, 35

Mot iva t ion

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.

Thr esho ld Custom izi ng U sing RZ20 (1 )

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

36/74

SAP AG 2004, TEP12, 36


1. Select the node 2. Choose Properties

SAP4


8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

37/74

SAP AG 2004, TEP12, 37

Name of the attribute

group

3. Choose Change

4. Customize threshold values


Aler t Handl ing: His t ory and Current View

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

38/74

SAP AG 2004, TEP12, 38

Aler t Handl ing: H is t ory and Current V iew

Current

Switch between views

History

Aler t Handl ing: Disp lay Aler t s

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

39/74

SAP AG 2004, TEP12, 39

Aler t Handl ing: Disp lay Aler t s

Double-clicking a node showsall corresponding alerts

Aler t Handl ing: Rem ove t he Aler t Cause

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

40/74

SAP AG 2004, TEP12, 40

Aler t Handl ing: Rem ove t he Aler t Cause

1. Select the alert 2. Start the analysis method

Aler t Handl ing: Ex am ple o f an Analys is Method

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

41/74

SAP AG 2004, TEP12, 41

g p y

Analysis method: drilling down to the monitored component

Aler t Handl ing: Com plet e Aler ts

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

42/74

SAP AG 2004, TEP12, 42

g p

Alert cause resolved:Complete the alert

How or What

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

43/74

SAP AG 2004, TEP12, 43

Checking thresholds is easy! But what is the rightthreshold?

Which thresholds should be used?

Use SAP performance transactions

Ask some experts...

Trace your daily administrative work Activate CPH (described later)

Look for additional information (Performanceanalysis information, Best Practices...

Check all attribute groups used in your monitors: Are theSAP threshold settings appropriate?

Mot iva t ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

44/74

SAP AG 2004, TEP12, 44

Precondition: You have checked the thresholds!

Problem: Now, alerts are raised only in case ofsevere 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 automaticallyin 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 toSAP. The connection might be cost intensive. SNMP could be a low

cost bridge between SAP and the third party product.

Auto-React ions

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

45/74

SAP AG 2004, TEP12, 45

SAP Basis 3.0 SAP Web Application Server





Non-SAP component

SAP instance

Other SAPcomponent

SAP instance

Central AlertNotification

Central Monitoring

SAPWeb AS 6.20

SAPCM3X

SAPCCMSR

SAPCCM4X

SAPCCMSR

Push

Push

SAPCCM4X

SAPCCMSR

SNMPTrap

SAP5

Loc al versus Cent ra l Aut o-Reac t ions?

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

46/74

SAP AG 2004, TEP12, 46

Definition of auto-reaction inCEN only

Definition of auto-reaction inthe local system

Often useful for notification:notification channels have tobe configured in CEN only!

Often useful for triggering OSscripts

Time delay depending on batchavailability in CEN

Time delay 5 min. maximum

Component is connected byusage of a CCMS agent.

Central method dispatcher

No preconditions

Processed by the ABAP stackof CEN

Processed by the ABAP stackof the component

Central auto-reactionsLocal auto-reactions

SAP6

St eps to Im p lement Aut omat ic E-Mai l Not i f i c a t ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

47/74

SAP AG 2004, TEP12, 47

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.

St ep 1: Conf igur ing SAPConnec t

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

48/74

SAP AG 2004, TEP12, 48

SAPConnect:Configuration in

transaction SCOT

is describedin great detail in theSAP documentation

R/3Application

modules

SAPOffice

SAPConnect

ExternalExternal

communicationscommunications

Fax, X.400, InternetFax, X.400, InternetOtherOther

mail systemsmail systems Other R/3 SystemsOther R/3 Systems

SAPscript

Adapter SMTP

St ep 1: Conf igur ing SAPConnec t

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

49/74

SAP AG 2004, TEP12, 49

SAPConnect node definition

Step 2: Copying CCMS_OnAle rt _Em ai l

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

50/74

SAP AG 2004, TEP12, 50

St ep 3: Cust om izing t he Met hod (1)

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

51/74

SAP AG 2004, TEP12, 51

2. Central auto-reaction

1. Function module definition

Where to execute?

2. Local auto-reaction

St ep 3: Cust om izing t he Met hod (2)

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

52/74

SAP AG 2004, TEP12, 52

3. Maintain parameters: Sender: User in client 000 Recipient: Can be a

distribution list maintainedin client 000

Recipient TypeID:U Internet mailR R/3R/3 mail Office standard

4. Release asauto-reaction method

SAP8

St ep 4: Cent ra l Aut o-Reac t ion Assignm ent

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

53/74

SAP AG 2004, TEP12, 53


Shared Memory

Segment

SAP instance

Central AlertNotification

CEN

SAPCCM4XSAPCCM4XShared Memory

Segment

J2EE

SAPCCMSR

Central auto-reaction assignment in CEN:

If an alert is raised in system X for MTE Class Y, trigger method Z in CEN!

Al t e rna t ive : Not i f i c a t ion v ia A le r t Management

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

54/74

SAP AG 2004, TEP12, 54

MethodCCMS_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 recipientassignment

Recipients are single users or adistribution list

Sends a notification to a centralalert management

Sends a notification viaSAPConnect

Alert managementCCMS email

SAP9

Send ing SNMP Traps

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

55/74

SAP AG 2004, TEP12, 55

3rd Party System Management

CEN


J2EE

SAPCCMSR

Alert is pushedto CEN

trapsendTrapsend is

triggered

Trap is sentto 3rd party

SNMP Conf i gurat ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

56/74

SAP AG 2004, TEP12, 56

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 theremote components.

If required, configure your 3rd party tool!

Result:

In case of alerts, an SNMP trap is sent to your 3rd partytool.

CCMS Cus t om izing

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

57/74

SAP AG 2004, TEP12, 57

CCMS Customizing

EP 6.0 Portal




Activating CPH (Central Performance History)

Fine-tuning

Roadmap

Mot iva t ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

58/74

SAP AG 2004, TEP12, 58

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.

New Feat ures at a Glanc e: CPH

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

59/74

SAP AG 2004, TEP12, 59

SAP Basis 3.0 SAP Web Application Server 4.0

MonitoringSegment

MonitoringSegment

MonitoringSegment

MonitoringSegment

Non-SAP component

SAP instance

Non-SAP-Basiscomponent

SAP instance

Central Monitoring

SAP

Web AS 6.20

CentralPerformance

History

New Feat ures at a Glanc e: CPH

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

60/74

SAP AG 2004, TEP12, 60

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.

CPH Act iva t ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

61/74

SAP AG 2004, TEP12, 61

MonitoringSegment

C H

3. Schedule periodiccollection (and

aggregation) job

1. Define, how long anaggregate in a certain

resolution should be stored

2. Define, which datashould be collected

Def in ing Col lec t ion and Reorganizat ion Sc hem a

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

62/74

SAP AG 2004, TEP12, 62

Define, how long an aggregatein a certain resolution shouldbe stored

Dat a Selec t ion v ia RZ20

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

63/74

SAP AG 2004, TEP12, 63

Define, which data

should be collectedusing RZ20

Dat a Selec t ion v ia RZ23N (Advanced Met hod)

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

64/74

SAP AG 2004, TEP12, 64

CPH: Cont inuous Proc essing

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

65/74

SAP AG 2004, TEP12, 65

C H

2. Reporting1. Data aggregation

2. Data export

Dat a Aggregat ion: Ex am ple

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

66/74

SAP AG 2004, TEP12, 66

Month aggregatewith hourresolution

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 aggregateswith hourresolution

Advanced On line Report i ng Us ing RZ23N

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

67/74

SAP AG 2004, TEP12, 67

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

Repor t Def in i t ion Sc reen

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

68/74

SAP AG 2004, TEP12, 68

Repor t Ex ec ut ion

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

69/74

SAP AG 2004, TEP12, 69

CCMS Cus t om izing

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

70/74

SAP AG 2004, TEP12, 70

CCMS Customizing

EP 6.0 Portal




Activating CPH

Fine-tuning

Roadmap

Mot iva t ion

Precondition: OS file systems are monitored by SAPOSCOL The

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

71/74

SAP AG 2004, TEP12, 71

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 attributegroup and MTE class.

No way to set different thresholds for different filesystems

Dynamic monitors display always all monitoredfile systems, although only some are important(e.g. database log destination).

Solution: SAPCCMSR filters important file systems and creates newattribute groups and MTE classes.

Enter file system information in a file oscolfile.txt

Enter MTE class and attribute group data

Assign oscolfile.txt to SAPCCMSRs config file sapccmsr.ini

Restart SAPCCMSR

Conf igu r ing SAPOSCOL Mon it or i ng

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

72/74

SAP AG 2004, TEP12, 72

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 NewGroup

MonitorProcess *java* J2EE_CL J2EE_GRMonitorProcess *oracle* ORA_CL ORA_GR

reads

monitors

readsRefers to

J2EE_CL

J2EE_GR

Java.exe

ORA_CL

ORA_GR

Oracle.exe

Result

Example

/oracle/C11/sapdataX /oracle/C11/saparch

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

73/74

SAP AG 2004, TEP12, 73

SAPCCMSR

SAPOsCol

p

Sapccmsr.ini

OsColFileG:\usr\sap\prfclog\sapccmsr\oscolfile.txt

Oscolfile.txt # MonitorFilesystem [ []]MonitorFilesystem /oracle/C11/saparch ARCH_CLARCH_GR

monitors

readsRefers to

ARCH_CL

ARCH_GR

Result

p

/oracle/C11/saparch

Transport ing CCMS Cust om izing

Overview of property variants

8/4/2019 bbb79990-0201-0010-cb9c-ee03abe3446f

74/74

SAP AG 2004, TEP12, 74

Overview of property variantsRZ21: Variant Transport

Variant name

Content of thechange request

How to put data in aproperty variant

is described in thenext chapters!

Documents

bbb79990-0201-0010-cb9c-ee03abe3446f