8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 1/8

An old dog tries new tricks - CCMS II / ADM107 - Addendum 1

Jim Spath Business CardCompany: Stanley Black & Decker

Posted on Feb. 19, 2008 02:58 AM in Application Server , Enterprise DataWarehousing/Business Warehouse , SAP Solution Manager , SAP NetWeaverPlatform

CPH - Central Performance HistoryDAY 1 | DAY 2 | ADDENDUM 1 | 2

I started this blog in November 2007, right after getting back to the office after taking theADM107 class. I intended to put what I learned into practice "soon" so I would not forget whatI learned. Well, it's now the middle of February 2008 and we have finally made time on thecalendar to get back to this.

This addendum (#1) will describe prerequisites we met, the agent configuration in our

sandbox system, show the results of the first few days with one monitoring agent, and talkabout the next steps.Life is relatively easy when you're in a class, with a focused instructor, classmates working onmore or less the same objective, a system or set of systems that have been tailored fresh outof the box, and a generally distraction free environment. Go back to the office and guesswhat? Priorities intrude, the system isn't as clean and stable as in the lab, and mostimportant, changes to even a sandbox system can interfere with developers projects andtimelines. The nice thing about using your own systems is that the date and time formats arewhat you expect, in your timezone.

Anyway, back to Chapter 1. Install the CCMS agents. Make sure they stay running.Our topology for baby step #1:

Central Performance History (CPH) will reside on our Solution Manager system. As of today,

this is a single node. Thus, no high availability, no path to production. When the system goesdown for maintenance, backups, etc., it's down.

We will install agents on R/3, BW and SCM systems, starting with R/3.So, which agents? Basis said we shall have " sapccmsr " and " sapccm4x ". So we shall.

Agent Health Check Fast forward past the agent install, which apparently went online in November:

The agents we have are from September 2007, so they are pretty fresh. The next step is to log into the SAP system to verify the agents are running.

Transaction RZ21 "Monitoring: Properties and Methods" is the starting place for configurationand verification steps. As in many cases, a few menu paths lead to the same place. Undertopology, pick "Agents for Remote Systems".

Subscribe

Print

Permalink

Share

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 2/8

Or, under "Technical Infrastructure", pick "Display Topology".

In class, we installed, configured, tested and used Windows agents. At work, we have UNIX,so the OS start up routines are different. In either case, the agent tests need to pass. Wefound one "ONLINE" and one "SHUTDOWN".

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 3/8

Being UNIX savvy, I checked and found only one daemon running:

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 4/8

If you look closely, the running daemon is "sapccmsr" while the reported shutdown agent isthe "sapccm4x" one. Don't ask me, I'm an engineer, not a topologist! After the Basis teamwent back to their desks and threw some runes, these were running:

Then, clicking on the "Monkey Wrench" icon as circled above showed successful connectionwhere it had not before.

Monitoring Configuration

Let's go to transaction RZ23N, "Central Performance History" (hooray) and select "AssignProcedure"

We picked generic table buffer hit ratio as the first element to track (big surprise - see my

blog on table buffer tuning ).

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 5/8

To verify that CPH is recording correct values, we can use a parallel test. Here are 2 shotsfrom the RZ20 monitoring tree drill down:

OK

BAD - the hit ratio has dropped. We shall see if this is noticeable with one-hour collection anddaily aggregation. It might be necessary to use 15-minute (quarter hour) intervals.

Pick one from Column A, one or more from Column B and one from Column C. This screenshot is bizarrely collapsed to below 600x400 size.

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 6/8

Here is verification that the background jobs are running:

The above is visible in RZ23N via "Collection/Reorganization Jobs".

Reporting This menu is accessed via RZ23N "Overview of Available Data" once the gears are turning.

Here is the CPH report grid in 2 dimensions, showing data have been collected over the pastseveral days. It works!

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 7/8

As noted, this is an ALV graphic directly created within CPH menus. I've altered the Y-Axisto include a maximum 100% (it was 101%) and a minimum 95%. I also selected one hourwhich showed up as red squares on multiple days. That's handy I guess.

I then brought the same data into Excel and created a scatter diagram. This is a little easieron my eyes.

Next Steps

8/6/2019 An Old Dog Tries New Tricks

http://slidepdf.com/reader/full/an-old-dog-tries-new-tricks 8/8

• Add more MTEs. We have a short list and a long list.

• Add other systems. The sandboxes are refreshed, so we should protect this work.

• Include specific dialog transactions to track. This is a primary goal to replace daily manualdata collection.

•

Increase the data cache to 40MB, per the book.• Figure out why the book says to update Op Modes, as it seems to work though we skipped

that step.

• Feedback analyses from these reports to the Basis and development teams as needed.

• Hook this into our enterprise monitoring system, whether through auto reaction or anotherprocess,

[All opinions expressed are mine. No opinions were harmed in writing this blog.]