27.04.2013 Views

SAP Basis

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ADM100 Lesson: Properties Variants and Threshold Values<br />

– First create container for threshold values (properties variants)<br />

and activate<br />

– Then maintain threshold values for the MTEs in your own<br />

monitors<br />

Threshold values determine when the corresponding monitoring attribute<br />

should trigger a yellow or red alert: Green means that there are “no<br />

problems”, yellow means “warning”, red means “problem or error”, and<br />

white means “no data available”.<br />

The delivered threshold values must be adjusted to local requirements<br />

before they are used. This adjustment should be recorded in properties<br />

variants. This means that the settings can be transported to local systems.<br />

This is very important, since measured values are always interpreted in<br />

accordance with local threshold values. Explain again that a data collection<br />

method must be explicitly scheduled and started for some attributes. This<br />

explains some of the inactive or white attributes.<br />

Threshold values can be stored for a monitoring attribute. Threshold<br />

values determine when the monitoring attribute should trigger a yellow<br />

or a red alert, and when it should become green or yellow again. The<br />

CCMS Alert Monitoring Infrastructure is delivered preconfigured with<br />

threshold values recommended by <strong>SAP</strong>. You should, however, check the<br />

threshold values, at least for the monitoring attributes that you consider to<br />

be important and that you have included in your own monitors. In this<br />

way, you customize the CCMS Alert Monitor optimally to your system<br />

environment. Otherwise, alerts can be constantly or never triggered,<br />

depending on whether the threshold value is too low or too high for your<br />

system environment.<br />

Thresholdvaluesmustbestoredlocallyineverysystem.However,instead<br />

of maintaining the same threshold values in every system, we recommend<br />

that you maintain the values in the central monitoring system and then<br />

distribute them to the monitored <strong>SAP</strong> systems using the transport system.<br />

The prerequisite for transporting the threshold values to other <strong>SAP</strong><br />

systems is that you have stored them in properties variants.<br />

(Monitoring) properties variants not only allow the transport of sets of<br />

threshold values, but also different assessment of reported values based<br />

on the time (of day). For example, some or all monitored values can be<br />

interpreted differently during the day and during the night in this way<br />

connection to operation modes, RZ04).<br />

2003/Q3 © 2003 <strong>SAP</strong> AG. All rights reserved. 507

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!