Important Concepts

• About Introscope and metrics
• About SAP CC concepts

Inroscope

Metrics for SAP CC

A metric is a measurement of application performance. It is a performance indicator based on the CA Introscope (IS) technology. CA IS Enterprise Manager (EM) compiles or computes the performance metrics by reusing performance raw data reported by the local agents in SAP CC system instances or in the Java Virtual Machine (JVM) that executes an instance of an SAP CC system.

The metrics can be monitored and recorded both in CA IS Enterprise Manager (EM) and SAP Solution Manager.

Basic Metrics

Basic Metric	Description		Example
Average Response Time	Average treatment execution time in milliseconds or nanoseconds (the lower, the better)		Typically, this is the latency. See: Average Response Time (ms) basic metric Average Response Time (ns) metric (via the Message TCP technical interface)
Errors Per Interval	Number of exceptions thrown during the treatment executions per time interval (none, the better)
Responses Per Interval	Number of treatment executions per time interval, throughput (the higher, the better)		Typically, this is the throughput.
Stall Count	Number of treatments or executions started but that have not completed within a defined time threshold Notes If a treatment or an execution is counted as stalled, this does not mean that it is interrupted and will never be completed, but that its processing exceeded a configured time threshold. This is not a timeout that relates to an error. By default, the stall threshold is set to 30 seconds for each instance of the SAP CC Core Server systems in the system landscape. This is a global configuration in the CA IS Agent profiles.

Nanosecond Precision

SAP CC and CA Introscope (IS) provide nanosecond precision, but not necessarily nanosecond accuracy; they rely on the Java Virtual Machine (JVM) to provide the current value of the most precise available system timer, in nanoseconds. Its accuracy varies depending on the operating system and hardware of the machines hosting the SAP CC systems.

Metric Definition Origin

They are three metric definition origins:

Metric Definition Origin	Description
CA Introscope Agent for SAP	The metric is provided using the Introscope AutoProbe instrumentation based on standard probe build directives packaged with the Introscope (IS) Agent for SAP. The CA IS Agent or Java Bytecode Instrumentation Agent for monitored systems is delivered in a subcomponent of SAP Solution Manager; see central SAP Note 797147. Example 'Average Response Time (ms)' metric For more information about the manual installation or software maintenance of this agent in an SAP CC system landscape, see SAP Note 1453216.
CA Introscope Enterprise Manager for SAP	The metric is provided on the Introscope (IS) Enterprise Manager side using scripts. The scripts are part of the EM extensions for SAP. They are delivered in the Introscope Management Modules package; see SAP Note 1579474.
SAP Convergent Charging	The metric is provided by the SAP CC software product through JMX or generic custom tracers. Examples 'Instance Status' metric 'Warmed Partition Count' metric

About SAP CC Concepts

Be aware of the following concepts in SAP Convergent Charging.

Business	Technical
Master data (pricing catalog and customer master data like contracts) Business operations (charging, refilling, data provisioning, data mass configuration) Business processes and execution modes	Communications with front-end and back-end systems Intracommunications (interinstance communications) Data cache warm-ups Message queue management

Convergent Charging

See: Message TCP Communications and Logic Tree Computation

See also: Queue monitoring: messages and interinstance communications and Technical Transaction monitoring

Master Data Management

See: Warm-up monitoring: customer master data and Logic Tree Computation

Technical Interfaces

See: Message TCP Communications and Connection

See also: Queue monitoring: messages and interinstance communications

Mechanisms

Processing Queues and Assigned Threads

See: Queue monitoring: messages and interinstance communications

Data Cache Warm-Ups

See: Warm-up monitoring: customer master data

Internal Schedulers for Business or Technical Functions

See: Scheduler activity monitoring

Technical Transactions

See: Technical Transaction monitoring