Unified Job Monitoring -Share your experiences with SAP Solution Manager 7.1

[Raghav_S]

Dear Forum members,

I woudl like to introduce myself as Raghav, S. I am in the development team responsible for building the unified job monitoring workcenter starting 7.1 SP10 (onwards).

Please post your feedback, current status wrt to setup, commmon issues in this area.

I will be more than glad to help you here.

Regards, Raghav

Development Manager

CLM - Solution manager team, Labs India.

[thorstenhenrici]

Hello,

apart from the afore mentioned problems, I would like to thank you for the work you are doing. The Job Monitoring application is very useful and very important for us, to fullfil several points our customers are demanding of us.

Best Regards,

Thorsten

[thorstenhenrici]

Hello Raghev,

we implemented unfied job monitoring on a larger scale by now, starting out with the monitoring of SAP Standard & Reorg Jobs.

Everything seemed quiet OK at the beginning, but over time display performance of the Monitoring UI decreased drastically (exceeding 5 Min. "per click" in the UI).

I pinned this down to the following (Oracle) SQL access:

  SELECT

  "CLIENT", "CONTEXT_ID", "TYPE_ID", "HASH_METRIC_PATH", "START_TIMESTAMP", "IS_CURRENT", "END_TIMESTAMP",

  "METRIC_PATH", "RATING_AGGREGATE", "VALUE_MIN", "VALUE_MAX", "VALUE_SUM", "VALUE_COUNT", "VALUE_LAST",

  "VALUE_DATA_TYPE", "VALUE_MAX_TIME", "LAST_TEXT"

FROM

  "MES_DB_AGGREGATE"

WHERE

  "CLIENT"=:A0 AND "CONTEXT_ID"=:A1 AND "TYPE_ID"=:A2 AND "IS_CURRENT"=:A3 OR "CLIENT"=:A4 AND

  "CONTEXT_ID"=:A5 AND "TYPE_ID"=:A6 AND "IS_CURRENT"=:A7 OR "CLIENT"=:A8 AND "CONTEXT_ID"=:A9 AND

  "TYPE_ID"=:A10 AND "IS_CURRENT"=:A11 OR "CLIENT"=:A12 AND "CONTEXT_ID"=:A13 AND "TYPE_ID"=:A14 AND

  "IS_CURRENT"=:A15 OR "CLIENT"=:A16 AND "CONTEXT_ID"=:A17 AND "TYPE_ID"=:A18 AND "IS_CURRENT"=:A19

The execution plan used for this SQL is:

0	SELECT STATEMENT
1	INLIST ITERATOR
2	TABLE ACCESS BY INDEX ROWID MES_DB_AGGREGATE
3	INDEX RANGE SCAN  MES_DB_AGGREGATECU

MES_DB_AGGREGATE in our case has over 5 million entries.

The parameterization of the DB incl. Memory and all should be OK.

The index range scan simply takes that long.

This might be, because the MES_DB_AGGREGATECU index has the lowest cardinality column (CLIENT) first.

Header 1	Header 2
COLUMN_NAME	NUM_DISTINCT
CLIENT	1
CONTEXT_ID	433
TYPE_ID	2192
IS_CURRENT	2

Could you have your team check on this, because with the situation as is, the Job Monitoring application seemingly becomes non-usable, as soon, as you start to scale up.

Best Regards,

Thorsten

[benu_mariantony2]

Dear Thorsten,

I would like to investigate this & assist you. What is your ST version?

BTW, I am from Job Monitoring development team.

Regards,

Benu

[thorstenhenrici]

Hello Benu,

ST version is ST 710 SP10.

I could open an incident in SAP Service Market Place to grant you access to the system.

Should I do so?

Thanks a lot for responding to this !!!

Cheers,

Thorsten

[former_member341695]

Hello Dear Raghav

We are very interested in the BW objects (DSO, Infocubes) that are populated following the activation of Job Monitoring.

As a matter of fact, we need to create some reporting on Job execution KPIs.

My questions are

Are there any standard reports available ? Where can we find them ?

How these BW objects behind Job Monitoring are activated and populated ? Is it sufficient to configure Job Monitoring ?

Is Job Monitoring able to monitor mass jobs of the ISU module ? Is this suitable for such a need ?

With my great thanks in advance for your precious help

regards

Ashkan

[Raghav_S]

Hello Ashkan,

Since SP10, we deliver standard BW reports for metrics collected from technical monitoring - job monitoring scenarios.

Please check in SOLMAN_WORKCENTER -> Technical monitoring -> Interactive reporting -> job monitoring scenarios. Here you find predefined Bex templates.

Reg "is Job Monitoring able to monitor mass jobs of the ISU module ? Is this suitable for such a need ?"

It should be possible to configure monitoring objects for these jobs (ABAP) in SP10. Did you check the Setup document? How many jobs needs to be monitored?

For the setup there are prerequisites mentioned in the note 1909902.

Let me know

Regards, Raghav

[former_member341695]

Dear Raghav

Many thanks for your reply

So i understand that standard BW reports on Job Monitoring KPIs are available from SP10.

My question if you please is actually the following:

We are on SP8. On this level, are the standard DSO and InfoCubes for job monitoring populated or not with values coming from the source system ?

If so, is this the role of the extraction framework to do so ? (data upload into BW infoproviders)

Generaly speaking, is "Job Monitoring" Function fully operationnal in SP8 (apart from BW standard reports delivered on SP10 as you mention) or should we upgrade to SP10 for using Job monitoring DSOs and Cubes ?

Many thanks again

[Raghav_S]

Hello Ashkan,

The Unified job Monitoring is only available from SP10. Are you referring to Job Management in SP08?

Regards, Raghav

[former_member341695]

Raghav

Actually yes

In SP08, in sm_workcenter, there is a workcenter named "Job Management". What are the differences between this and the upcoming "Unified Job Monitoring" ? Does "Job Management" have some DSO or infocubes behind it in SP08 ?

Besides, in RSA1, i can see the following infoCubes in the "SAP Solution Manager - Job Scheduling Management" info-area:

JSM Health Check Daily

JSM Health Check Hourly

JSM Health Check for BW Chain Monitor ?

...

Are these cubes related to "Job Management" in SP08 ?

Briefly speaking, what can we do with Job Management in SP08 from a reporting point of view ? Should we upgrade to SP10 for having more functionnalities in term of Job Monitoring and Job reporting ?

many thanks again

[Raghav_S]

We delivered unifified job monitoring in SP10 and then reporting for jobs monitored via this workcenter.  can you check this cube : 0SMJPMCMP

In SP08, Job management, you can look at BOops dashboard in solman_workcenter - >B P operations(new)