Reference: SAP System Checks

This section contains a reference of all SAP System Checks provided by Avantra.

ABAP_DD_DB

Watch ABAP data dictionary / database consistency

Description

Runs the ABAP data dictionary / database consistency check inside SAP and displays the results.

If there are no inconsistencies the check is Ok, otherwise a Warning will be reported.

Certain indexes may be excluded from the check by using ABAP_DD_DB_Exclude.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

ABAP_DD_DB_Exclude

BATCH_INPUT

Verify erroneous, long-running, and outdated batch input sessions

Description

The check consists of three sub-checks.

  • The SAP System is queried for batch input sessions older than BatchInputMaxAge days. The Check Result will be Warning if records are found. To turn this sub-check off, you may set BatchInputMaxAge to 0. The result of this sub-check is indicated with a message like: Number of batch input sessions older than 60 days: 85.

  • The SAP System is queried for running batch input sessions older that BatchInputMaxRunTime. The Check Result will be Warning, if records are found. You cannot turn this sub-check off. The result of this sub-check is indicated with a message, like: Number of batch input sessions in state processing older than 24 hours: 7.

  • The system is queried for erroneous batch input sessions of the previous day. If records are found, the Check Result will be Critical and a table with erroneous batch input sessions will be displayed. The result of this sub-check is indicated with a message, e.g.: No erroneous batch input sessions starting from 2010-02-16 07:00:00 found or

    Cli. Session name  St. User   Date/Time           Creation Program   TA.tot   TA.err
    ------------------------------------------------------------------------------------
    001  MY_SESSION    E   BATCH  2010-02-17 06:00:44 Z_MY_PROG          28       28

For all three sub-checks you may use BatchInputClientExclude to exclude clients, and BatchInputQIDExclude to exclude sessions by Queue-ID. By default client 000 and 066 are excluded.

BatchManStat

Verify BatchMan status (if present)

Description

The check verifies the status of BatchMan, a 3rd-party product of HONICO. (If installed in your ABAP SAP System.)

BatchManStat will first look if BatchMan is active; if so it will further check if the BatchMan master job is active. Additionally it will output the date and time of the last run of the master job. The check status is Ok if both, BatchMan itself and its master job are active. Otherwise the check status is Critical.

If you are not using BatchMan but the Avantra Agent has found it in your SAP System and the BatchManStat check is Critical you may want to disable the check completely.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Basic

Depends on

RFCConnect

Monitoring Parameters

n/a

BCS_OutboundErrors

Query for erroneous outbound Business Communication Services records (Daily Check)

Description

This check retrieves erroneous outbound business communication services records as displayed by SAP transaction SOST. BCS_OutboundErrors works exactly as the RealTime Monitoring check BCS_OutboundErrStat, except that the timespan is always to the previous Daily Check record. Please see BCS_OutboundErrStat for a description.

BCS_OutboundErrStat

Query for erroneous outbound business communication services records (RealTime Monitoring)

Description

This check retrieves erroneous outbound business communication services records as displayed by SAP transaction SOST. BCS_OutboundErrStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, BCS_OutboundErrStat checks in all clients except 000 and 066. You may change this behaviour using BcsOutboundClientMode, which can be set to Blacklist or Whitelist. The black or white listed clients are specified by BcsOutboundClientList parameter.

If the number of erroneous records in last BcsOutboundErrStatTimeSpan minutes is above configurable thresholds BcsOutboundErrStatNumWarn or BcsOutboundErrStatNumCrit, the status of the check is set to the corresponding status. This check is accompanied by Daily Check BCS_OutboundErrors, which checks erroneous records back to the previous Daily Check schedule.

Each client is checked separately against the thresholds. The client column of the result table is either colored with no color, meaning there are erroneous records but the number is below Warning and Critical thresholds, yellow, meaning the number of erroneous records are equal to or above the Warning threshold, or red, i.e. above the Critical threshold. The worst result per client will give the overall status of the check.

The amount of records being selected is limited by a maximum number of 500 per client.

Due to technical reasons the column Sender will be blank if the RFC user (see Avantra Agent is not in the same client as the BCS record.

BCS_OutboundWaitStat

Query for waiting outbound business communication services records

Description

This check retrieves waiting outbound business communication services records as displayed by SAP transaction SOST. BCS_OutboundWaitStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, BCS_OutboundWaitStat checks in all clients except 000 and 066. You may change this behaviour using BcsOutboundClientMode, which can be set to Blacklist or Whitelist. The black or white listed clients are specified by BcsOutboundClientList parameters.

If the number of waiting records is above configurable thresholds BcsOutboundWaitNumWarn and the wait time of these records exceed BcsOutboundWaitTimeWarn minutes, the status is set to Warning. If records are found, which exceed BcsOutboundWaitNumCrit in number and BcsOutboundWaitTimeWarn in time, the status is set to Critical.

Each client is checked separately against the thresholds. The client column of the result table is either colored in green, meaning there are waiting records but the wait time of each record is below BcsOutboundWaitTimeWarn. This can be normal behaviour, for instance, if waiting records are sent by a scheduled job. If the client column has no color at all, this means that there are waiting records above BcsOutboundWaitTimeWarn or BcsOutboundWaitTimeCrit but the number of them is below thresholds BcsOutboundWaitNumWarn or BcsOutboundWaitNumCrit. Yellow and red color mean that there are waiting records above the corresponding time and number thresholds.

Since different send methods may require different time thresholds, for instance, if outbound requests using FAX are only sent at a certain schedule, you may use exception parameter BcsOutboundWaitTimeExceptions to define special threholds. For syntax details, please see the documentation of this parameter. If an exception threshold is used for a record, a small info icon will be displayed beneath the waiting time.

The amount of records being selected is limited by a maximum number of 500 per client.

Due to technical reasons the column Sender will be blank if the RFC user (see Avantra Agent is not in the same client as the BCS record.

BW_PROCESSCHAINS

Verify status and runtime of process chains

Description

The check retrieves the status and the runtime of all Process Chain runs during the last day.

If one of the Process Chains terminates with status red, the check turns Critical. If on of the Process Chains exceeds the runtime thresholds, the check status turns to Critical or Warning, resp.

Certain Process Chains may be excluded from the check by using BWProcessChainsExclude, the Check Result for canceled (status X) Process Chains may be defined with BWProcessChainsCancelledStatus as well.

In order to run this check, the Avantra RFC User must be defined in the standard client of the SAP BI System.

BW_QUERYRUNTIME

Monitor SAP BI query runtimes

Description

The check lists queries within a SAP BI System that exceed a configurable runtime threshold.

In order to run this check, the Avantra RFC User must be defined in the standard client of the SAP BI System.

Further, statistics must be enabled: Proceed to transaction RSA1, choose Tools  BW statistics for InfoCubes. See also SAP Note 557870 - FAQ: BW Query Performance.

Reference Data
Managed Object

SAP Business Information Warehouse

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

BWQueryRuntimeCrit, BWQueryRuntimeWarn, BWQueryRuntimeExclude

DIALOGPERF

Verify dialog performance

Description

Reports the performance of dialog steps in an ABAP SAP System.

The check returns an alert if a certain ratio of the dialog steps runs longer than a configurable threshold (e.g. 1 second).

The ratio as well as the runtime threshold can be configured.

The results are listed during a time period of one day (as provided by the underlying SAP System; cannot be configured).

A minimum number of steps can be defined also.So, if there are less dialog steps in the monitoring period these values are not considered for the Check Result. This is to take into account that only a reasonably large number of data can provide some valuable statistics.

Example 1. Example of the DIALOGPERF daily check
Overview of dialog steps below 1 sec runtime, time range: 00-24 h
Minimum number of dialog steps (status is OK if below): 1000

Date: Thu Jan  6 2005
Status        Time  # Total   # >=1s   % >=1s    # <1s    % <1s
---------------------------------------------------------------
OK           00-06       10        0      0.0       10    100.0
WARNING      06-07     1326      146     11.0     1180     89.0
WARNING      07-08     2053      220     10.7     1833     89.3
WARNING      08-09     3322      338     10.2     2984     89.8
WARNING      09-10     3991      344      8.6     3647     91.4
WARNING      10-11     5368      369      6.9     4999     93.1
WARNING      11-12     3157      254      8.0     2903     92.0
OK           12-13     2465      116      4.7     2349     95.3
WARNING      13-14     2880      319     11.1     2561     88.9
WARNING      14-15     3934      294      7.5     3640     92.5
WARNING      15-16     5193      493      9.5     4700     90.5
WARNING      16-17     2302      278     12.1     2024     87.9
WARNING      17-18     1083       74      6.8     1009     93.2
OK           18-19       26        0      0.0       26    100.0
CRITICAL->OK 19-20        6        2     33.3        4     66.7
OK           21-24        4        0      0.0        4    100.0
---------------------------------------------------------------
TOTAL        00-24    37120     3247      8.7    33873     91.3

The leftmost column displays the status for a particular time period. The next column displays the time period, followed by the total number of dialog steps, the number of dialog steps running longer than DialogPerfRespTimeLimit, the ratio of those, the number of dialog steps running less or equal than DialogPerfRespTimeLimit, and the ration of those.

Due to the defined DialogPerfRespTimeLimit value, the period 19-20 is not considered Critical.

IDOCS

Verify IDOC reorganisation

Description

An overview of IDOCs status an the corresponding group is given for the previous Full Check Cycle.

If there are IDOCs in status group red the check returns a Warning. Additionally there is a Warning message if IDOCs older than a configurable threshold are found.

This way Avantra verifies if IDOCs are reorganized correctly.

IDOCSTAT

Watch for new IDOCs in status group red

Description

The number of modified IDOCs with a status in the status group red is monitored over a configurable period of time (default one hour). Warning and Critical thresholds may be defined.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Basic

Depends on

RFCConnect

Monitoring Parameters

IdocsGrpRedTimeSpan

JavaJobStat

Description

Monitors the status of jobs in the Java Scheduler which have run in the last 1 day (configurable by JavaJobsSelectRange). Shows a table of all jobs found, limited to 1000 entries.A job in status "Error" will turn the check to CRITICAL, a job in status "Cancelled" will turn it to WARNING.

Reference Data
Managed Object

SAP System with Java CI

Check Cycle

Basic

Depends on

J2EECONNECT

Monitoring Parameters

JavaJobsSelectRange

JavaJobStat

Description

Monitors the status of jobs in the Java Scheduler which have run in the last 60 minutes (configurable by JavaJobStatTimeSpan). Shows a table of all jobs found, limited to 1000 entries.A job in status "Error" will turn the check to CRITICAL, a job in status "Cancelled" will turn it to WARNING.

Reference Data
Managed Object

SAP System with Java CI

Check Cycle

Basic

Depends on

J2EECONNECT

Monitoring Parameters

JavaJobStatTimeSpan

JavaSSLCertificatesValidity

Verifies SSL certificates of Java systems

Description

JavaSSLCertificatesValidity checks if SSL certificats are valid, considering information of the Keystore Views configured in the NetWeaver keystore service.

If certificates are found which are about to expire, the check status will be Critical if the remaining valid period is equal to or below SSLCertificatesValidityCrit. If the remaining valid period of one or more certificates is above SSLCertificatesValidityCrit but equal to or below SSLCertificatesValidityWarn the check status will be Warning.

Expired certificates are reported for SSLCertificatesValidityIgnore days. After SSLCertificatesValidityIgnore days they will be ignored and no longer contribute to the check status, however, they are still reported in the check result output.

JOBS

Verify aborted SAP Jobs

Description

All aborted jobs within the last Full Check Cycle; are counted, unless excluded by the JobAbortExclude Monitoring Parameter or excluded by JobUsersExclude Monitoring Parameter.

If the number of aborted jobs exceeds JobsDailyCountWarn or JobsDailyCountCrit the check will return the corresponding check status.

JOBSTAT

Verify aborted and delayed SAP Jobs

Description

The JOBSTAT check consists of two sub-checks.

  • The number of aborted SAP jobs is detected over a configurable period of time (by default one hour). Warning and Critical thresholds may be defined, and there is also an option to exclude certain Jobs from being considered. The result is indicated with a message like

    OK - Number of aborted jobs in last 60 minutes: 1
    Aborted jobs are [#]: SLCA_LCK_SYNCHOWNERS [1]

    The result includes the names of aborted jobs and the number in square brackets.

  • The number of delayed jobs is detected over configurable periods of time.

    The status of this sub-check is Warning if JobDelayedCountWarn or more jobs are delayed for more than JobDelayedTimeWarn minutes. The status is Critical if JobDelayedCountCrit or more jobs are delayed for more than JobDelayedTimeCrit minutes.

    The result is indicated with a message like

    CRITICAL - Number of jobs being delayed for more than 2 minutes: 3, for more than 10 minutes: 2
    Delayed jobs are [h:mm]: /BDL/TASK_PROCESSOR [2:38], SAP_RSICFDLT [2:35|4:31],
    SAP_CCMS_MONI_BATCH_DP [10:05], SAP_COLLECTOR_FOR_NONE_R3_STAT [12:42]

    The result includes the names of delayed jobs and the delay time. If more than one job with the same name is delayed, the individual delay times are displayed in a list separated by |.

    The {monitoring-parameter} JobDelayedIncludeExpired controls if expired jobs, i.e. jobs with configured and expired _ Ç No start after# date are considered as delayed or not.

The JOBSTAT check might display jobs with a very long delay time, e.g. Delayed jobs are [h:mm]: SAP_COLLECTOR_FOR_PERFMONITOR [18213:13]. This is no error!

You will definitely find this orphaned job in your system, if you query for it the following way:

  1. Run SAP transaction Job overview (i.e. SM37).

  2. Query for the jobname, user name *, job status Released or Ready, and clear all job start condition from the selection.

  3. The job will then be displayed in the result list.

The delay time may be so long, that it is not displayed in the job overview table of SM37 for whatever reason.

In order to clean up, you will usually delete the orphaned job.

LOCKTABLE

Verify the lock table

Description

All entries within the lock table are analyzed for their age. If entries are older than the configurable thresholds a corresponding Warning or Critical alert is raised.

MII_Connect

Checks whether SAP MII (Manufacturing Integration and Intelligence) is up and running.

Reference Data
Managed Object

SAP System (Java, ABAP+Java)

Check Cycle

Basic

Depends on

J2EECONNECT

MII_DataServers

Check is SAP MII data server is available.

MII_Schedules

Check if SAP MII scheduler has overrun jobs.

MII_FailedTransactionStat

Check if SAP MII has failed transactions (RTM).

Description

A SAP MII transaction is considered as failed if the transaction STATUS is either Invalid, Failed, Terminated, or Exception.

MII_FailedTransactions

Check if SAP MII has failed transactions (daily check).

Description

A SAP MII transaction is considered as failed if the transaction STATUS is either Invalid, Failed, Terminated, or Exception.

MII_LongRunningTransactions

Check if SAP MII has long running transactions.

Description

A SAP MII long running transaction is a transaction which is currently running, and the current runtime is longer that a threshold.

MII_FailedMessageStat

MII_FailedMessages

Check for failed messages (daily check)

NumberRanges

Verifies the usage of Number Ranges in ABAP systems

Description

NumberRanges checks the Number Ranges of an ABAP system for its usage. It works similar to SAP standard report RSNUMHOT, however, the check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, NumberRanges checks in all clients except 066, so client 000 is included per default. You may change this behaviour using NumRangesClientMode, which can be set to Blacklist (default) or Whitelist. The black or white listed clients are specified by NumRangesClientList parameter.

Per default, all Number Ranges are checked against thresholds NumRangesUsageWarn and NumRangesUsageCrit. If the usage of a Number Range exceeds the corresponding threshold, the check result will be either Warning or Critical. Per default, rolling number ranges are included in the check as well. You may change this behavior by unchecking NumRangesRollingIntervals.

To even further individualise the check behavior, you can use exclude number ranges from being checked and you can as well instruct the check to use individual thresholds as defined in SAP transaction SNUM. To exclude Number Ranges, you list them in NumRangesExclude. Excludes always work on all clients. To use individual thresholds already defined in your SAP System, you use NumRangesUseObjectDef. If you want to define individual thresholds specifically, you use the advanced NumRangesUsageEx parameter.

Please see the reference of these Monitoring Parameters for further reference.

PI_AdapterEngine

Verify the PI Adapter Engines

Description

Checks the PI Adapter Engine on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 7.30)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_AdapterFramework

Verify all PI Java-based Adapter Engines

Description

Checks all PI Java-based Adapter Engines (central and non-central) of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 6.40 and < 7.30)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_AEMessages

Checks for erroneous PI Adapter Engine XML messages

Description

Checks for erroneous XML messages of the PI Adapter Engine as displayed by the Message Monitor of an SAP NetWeaver PI system. PI_AEMessages works exactly as the RealTime Monitoring check PI_AEMessagesStat, except that the timespan is always to the previous Daily Check record. Please see PI_AEMessagesStat for a description.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 7.30, PI-AEX 7.40 and above)

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

PIAEMessagesNumCrit, PIAEMessagesNumWarn, PIAEMessagesUseHttps RunDailyCheckOnWE

PI_AEMessagesStat

Checks for erroneous PI Adapter Engine XML messages

Description

Checks for erroneous XML messages of the PI Adapter Engine as displayed by the Message Monitor of an SAP NetWeaver PI system for the last PIAEMessagesStatTimeSpan minutes.

If the number of erroneous messages is above configurable threshold PIAEMessagesStatNumWarn the status is set to Warning. If the number of messages found exceeds PIAEMessagesStatNumCrit the status is set to Critical.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 7.30, PI-AEX 7.40 and above)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIAEMessagesStatTimeSpan, PIAEMessagesStatNumWarn, PIAEMessagesStatNumCrit, PIAEMessagesUseHttps, MediumCheckCycleTime

PI_BusinessProcessEngine

Verify the PI Business Process Engines

Description

Checks the PI Business Process Engines of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 6.40 and < 7.30)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_CACHE

Verify the status of the XI Runtime Cache

Description

Retrieves the status of the XI Runtime Cache as performed with transaction SXI_CACHE (Exchange Infrastructure  Configuration  XI Cache Refresh).

The check message and status corresponds to the status of the XI Cache, i.e. a red light will be displayed as Critical and yellow as warning and green as Ok.

The following table lists the check results:

  1. PI_CACHE check results

Check Status

Check Message

Ok

Cache contents are up-to-date

Warning

Cache update is in progress

Warning

Unknown state

Critical

Cache contents are obsolete

Critical

Cache contents are inconsistent

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI systems with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

RFCConnect

Monitoring Parameters

MediumCheckCycleTime

PI_CommChannels

Verify the PI Communication Channels

Description

Checks the status of PI communication channels. If a channel’s status is INACTIVE, UNKNOWN, or UNREGISTERED, Avantra will report a Warning check status. If a channel’s status is ERROR, Avantra will report a Critical check status. For the remaining possible status OK, Avantra’s check status will be Ok, of course. The overall check status of PI_CommChannels will be the worst status of all channels.

Please note that per default, all communication channels with status INACTIVE are excluded, so if you want to receive a Warning for the same, you first need to change Monitoring Parameter PICommChannelsExclude.

Furthermore, you can use Monitoring Parameters PICommChannelsErrsWarn and PICommChannelsErrsCrit to delay the time an error is reported as Warning or Critical state. Per default, an error will be reported immediately as Critical since PICommChannelsErrsCrit is set to 1. If you change the parameters, e.g. to PICommChannelsErrsWarn 2 and PICommChannelsErrsCrit 3, a channels check status will be still Ok after the first error is detected. If the error persists to the next check cycle, check status will be Warning. If it still persists to the third check cycle in sequence, check status will be Critical.

{monitoring-parameter} PICommChannelsExclude is used to exclude certain communication channels from being checked. You can exclude on all information provided by the check’s result table, i.e. _Party, Service, Channel, Activation State, and Channel State.

To use this check, you’ll have to make sure the action xi_af_channel_admin_display is assigned to the SAP Java user.

PI_CONNECT

Verify connectivity to PI/XI SAP Systems

Description

This check verifies if the basic infrastructure for PI/XI monitoring is up and running.

This check returns Critical when the SAP Runtime Workbench is not accessible using the Avantra J2EE user. This can be due to a lack of permissions of the user or due to an incompletely configured PI system.

Additionally PI_CONNECT serves as a master check for all other PI checks (except PI_CACHE), so if this check fails, all the other dependent checks will return Unknown.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI systems with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

AGENTALIVE

Monitoring Parameters

PIForceEnable

PI_IEMessages

Checks for erroneous PI Integration Engine XML messages

Description

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction SXMB_MONI. PI_IEMessages works exactly as the RealTime Monitoring check PI_IEMessagesStat, except that the timespan is always to the previous Daily Check record. Please see PI_IEMessagesStat for a description.

PI_IEMessagesStat

Checks for erroneous PI Integration Engine XML messages (RealTime Monitoring)

Description

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction SXMB_MONI when queried for XML messages in status group Errors for the last PIIEMessagesStatTimeSpan minutes.

PI_IEMessagesStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, PI_IEMessagesStat checks in all clients except 000 and 066. You may change this behaviour using PIIEMessagesClientMode, which can be set to Blacklist or Whitelist. The black or white listed clients are specified by PIIEMessagesClientList parameter.

If the number of erroneous messages is above configurable threshold PIIEMessagesStatNumWarn the status is set to Warning. If the number of messages found exceeds PIIEMessagesStatNumCrit the status is set to Critical.

Each client is checked separately against the thresholds. The client column of the result table hash either no color, meaning there are erroneous messages but the number for this client is still below PIIEMessagesStatNumWarn. Yellow and red color mean that the number of erroneous messages exceed the corresponding thresholds.

PI_IntegrationDirectory

Verify the PI Integration Directories

Description

Checks the PI Integration Directories of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI 2.0 or higher with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_IntegrationEngine

Verify the PI Integration Engines

Description

Checks the PI Integration Engines of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI 2.0 or higher with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_IntegrationRepository

Verify the PI Integration Repositories

Description

Checks the PI Integration Repositories of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI 2.0 or higher with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_J2SEAdapterEngine

VERIFY J2SE-based adapter engines

Description

Checks all J2SE-based adapter engines of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 6.40 and < 7.30)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_MappingRunTime

Verifys the PI Mapping Runtimes

Description

Checks the PI Mapping Runtimes of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_RuntimeWorkbench

Verify the PI Runtime Workbench

Description

Checks the PI Runtime Workbench of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI 2.0 or higher with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

PI_SystemLandscapeDir

Verify the PI System Landscape Directory

Description

Checks the PI System Landscape Directory of all PI Domains accessible on the current instance for availability.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude this features from contributing to the check status by PIExcludeSelftestFeatures.

Reference Data
Managed Object

SAP System (ABAP+Java PI/XI 2.0 or higher with kernel release ≥ 6.40)

Check Cycle

Medium

Depends on

PI_CONNECT

Monitoring Parameters

PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

QRFC_IN

Verify the number of queued records for all inbound qRFC queues

Description

Checks the number of queued records for all inbound qRFC queues as done with SAP qRFC Monitor (SAP transaction SMQ2 for inbound queues). If the number of waiting records is above the Warning or Critical threshold a corresponding alert is raised.

The queue state is not monitored with this check, but with QRFC_IN_ERRQ.

It is possible to exclude queues from being monitored by defining QRFCInQueueExclude.

QRFC_IN_ERRQ

Verify hanging or erroneous inbound qRFC queues

Description

Checks inbound qRFC queues as done with SAP qRFC Monitor (SAP transaction SMQ2 for inbound queues).

If the number of hanging or erroneous queues is equal to or above QRFCInQueueHangWarn but below QRFCInQueueHangCrit the check status will will be Warning. If the number of hanging or erroneous queues if higher than QRFCInQueueHangCrit, a critical alert is raised.

It is possible to exclude queues from being monitored by defining QRFCInQueueExclude.

QRFC_OUT

Verify the number of queued records for all outbound qRFC queues

Description

Checks the number of queued records for all outbound qRFC queues as done with SAP qRFC Monitor (SAP transaction SMQ1 for outbound queues). If the number of waiting records is above the Warning or Critical threshold a corresponding alert is raised.

The queue state is not monitored with this check, but with QRFC_OUT_ERRQ.

It is possible to exclude queues from being monitored by defining QRFCOutQueueExclude.

QRFC_OUT_ERRQ

Verify hanging or erroneous outbound qRFC queues

Description

Checks outbound qRFC queues as done with SAP qRFC Monitor (SAP transaction SMQ1 for outbound queues).

If the number of hanging or erroneous queues is equal to or above QRFCOutQueueHangWarn but below QRFCOutQueueHangCrit the check status will will be Warning. If the number of hanging or erroneous queues if higher than QRFCOutQueueHangCrit, a critical alert is raised.

It is possible to exclude queues from being monitored by defining QRFCOutQueueExclude.

SHORTDUMPS

Verify the number of short dumps

Description

This check consist of two sub-checks:

ShortDumpStat

Verify the number of short dumps (RealTime Monitoring)

Description

The check verifies the number of short dumps over a configurable period of time (default one hour).

If Warning or Critical thresholds are exceeded, a corresponding Warning or Critical Check Result is returned.

You can define a list of short dumps that shall be excluded from this check by using ShortDumpExclude, e.g. you may want to suppress TIME_OUT short dumps which may happen once a user maximum dialog idle time has been exceeded.

SLT_Status

The status of the connection to the replication source and target is evaluated

Description

One check of this type is created per SLT configuration - SLT_Status_<Configuration_name>. In case the connection to the replication source or (and) replication target is broken, then the check result is CRITICAL. Otherwise - OK. If the connection is inactive, the check result is UNKNOWN with text “Configuration <configuration name> is not inactive”

Reference Data
Managed Object

SAP System (ABAP with DMIS 2011 >= SP5)

Check Cycle

Basic

Depends on

RFCConnect

Monitoring Parameters

None

SLT_UnprocRecs

Evaluates a number of unprocessed records for replicated tables

Description

The check retrieves a number of unprocessed records for the tables to be replicated. The separate check entry is created for each SLT configuration available in SLT system - SLT_UnprocRecs_<configuration_name>. Within the check, the unprocessed records amount is received for each replicated table. Currently any number of unprocessed records for some table causes the check result CRITICAL. In case the configuration is inactive, the check result is UNKNOWN with the message “Configuration <configuration name> is not inactive”. With parameter SLTUnprocRecordsClient it is possible to override the client number a check data extraction is performed from.

Reference Data
Managed Object

SAP System (ABAP with DMIS 2011 >= SP5)

Check Cycle

Basic

Depends on

RFCConnect

Monitoring Parameters

SLTUnprocRecordsClient

SLT_IUCJobs

Evaluates a number of /1LT/IUC_* jobs finished within the specified period.

Description

The check get the number of SLT jobs finished within periods of time, defined with parameters SLTIucJobsMinutesWarn and SLTIucJobsMinutesCrit. If there was no jobs finished within SLTIucJobsMinutesCrit period, the check result is CRITICAL. If there was no jobs finished within SLTIucJobsMinutesWarn period, the check result is WARNING. Currently only the finished jobs are taken into account, active jobs are not selected.

SPOOL

Verify output requests

Description

This check consist of two sub-checks:

SPOOLSTAT

Verify output requests (RealTime Monitoring)

Description

This check consists of two sub-checks:

SSLCertificatesValidity

Verifies SSL certificates of ABAP systems

Description

SSLCertificatesValidity checks if SSL certificats are valid, just the same way as transaction STRUST or the report SSF_ALERT_CERTEXPIRE would do.

The output of the check is similar to report SSF_ALERT_CERTEXPIRE. If certificates are found, which are about to expire, the check status will be Critical if the remaining valid period is equal to or below SSLCertificatesValidityCrit. If the remaining valid period of one or more certificates is above SSLCertificatesValidityCrit but equal to or below SSLCertificatesValidityWarn the check status will be Warning.

Expired certificates are reported for SSLCertificatesValidityIgnore days. After SSLCertificatesValidityIgnore days they will be ignored and no longer contribute to the check status, however, they are still reported in the check result output.

SXMB_Messages

Checks for erroneous PI Integration Engine XML messages

Description

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction SXMB_MONI. SXMB_Messages works exactly as the RealTime Monitoring check SXMB_MessagesStat, except that the timespan is always to the previous Daily Check record. Please see SXMB_MessagesStat for a description.

SXMB_MessagesStat

Checks for erroneous PI Integration Engine XML messages (RealTime Monitoring)

Description

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction SXMB_MONI when queried for XML messages in status group Errors for the last SXMBMessagesStatTimeSpan minutes.

SXMB_MessagesStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, SXMB_MessagesStat checks in all clients except 000 and 066. You may change this behaviour using SXMBMessagesClientMode, which can be set to Blacklist or Whitelist. The black or white listed clients are specified by SXMBMessagesClientList parameter.

If the number of erroneous messages is above configurable threshold SXMBMessagesStatNumWarn the status is set to Warning. If the number of messages found exceeds SXMBMessagesStatNumCrit the status is set to Critical.

Each client is checked separately against the thresholds. The client column of the result table hash either no color, meaning there are erroneous messages but the number for this client is still below SXMBMessagesStatNumWarn. Yellow and red color mean that the number of erroneous messages exceed the corresponding thresholds.

SystemAlive

Verify if a SAP System is alive

Description

The check verifies if the minimum requirements for the technical operation of a SAP System are fulfilled from a monitoring perspective.

These requirements depend on the nature of the SAP System, but basically there has to be a minimum number of SAP Instances available, i.e. they have to be detected and the corresponding connect checks have to succeed. If one of the required SAP Instances is not available SystemAlive will report an error message.

The following list describes the conditions that have to be fulfilled for the SystemAlive check to be Ok:

ABAP only with classical Central SAP Instance
ABAP only with Abap_Scs SAP Instance
Java only SAP System
ABAP+Java (double stack) SAP Instance

Although the SystemAlive may report Ok, your system may face e.g. performance problems if one or multiple SAP Instances are not available. So you should seriously consider all check results.

The Monitoring Parameter SysAliveIncompleteTimeCrit plays an important role once it comes to a cluster switch. If a cluster does switch, one of the required SAP Instances may vanish until the cluster switch has finished finally. To cover these situations the SystemAlive check first turns to Warning. If the SAP Instances does not come up withinSysAliveIncompleteTimeCrit minutes, the check turns to Critical.

Example 2. Example SystemAlive Ok
  • Classical Central SAP Instance with double-stack and Database instance on the same host.

    Database server is basel
    DBCONNECT check is OK for C11
    Central instance is basel_C11_00
    ABAP central services instance is basel_C11_00
    J2EE central services instance is basel_C11_01
    RFCCONNECT check is OK for basel_C11_00
    J2EECONNECT check is OK for basel_C11_00
    ASCS_MSGSRV check is OK for basel_C11_00
    SCS_MSGSRV check is OK for basel_C11_01
  • Java-only system, all components on a single host

    Database server is colmar
    DBCONNECT check is OK for P01
    Central instance is colmar_P01_01
    J2EE central services instance is colmar_P01_02
    J2EECONNECT check is OK for colmar_P01_01
    SCS_MSGSRV check is OK for colmar_P01_02
Example 3. Example SystemAlive not Ok
  • No active instances found.

    No active instances found since 00:05 [hh:mm]

    Status is Warning or Critical depending on SysAliveIncompleteTimeCrit

  • System is incomplete. This happens if there are instances available but Avantra can no longer determine the type of the SAP System. The status again depends on the time expired and on the SysAliveIncompleteTimeCrit setting

    The system is incompletely monitored since 00:05 [hh:mm].
    Not all components of a fully operational system have been found.

TMS_Imports

Checks for transport requests with not Ok import return code (Daily Check)

Description

Checks the return code of imported transport requests and works exactly like the RealTime Monitoring check TMS_ImportStat, except that the timespan is always to the previous Daily Check record. Please see TMS_ImportStat for a description. Please note that TMS_Imports uses its own Monitoring Parameters TMSImportReturnCodeCrit and TMSImportReturnCodeWarn.

TMS_ImportStat

Checks for transport requests with not Ok import return code (RealTime Monitoring)

Description

Checks the return code of imported transport requests of last TMSImportStatTimeSpan minutes. If one or more imports finished with return code ≥ 8, the check status will be Critical. If no import with return code ≥ 8, but one or more ≥ 4 are found, the check status will be Warning. Otherwise the check status will be Ok.

This default behaviour can be changed by Monitoring Parameters TMSImportStatReturnCodeCrit and TMSImportStatReturnCodeWarn. For example, you might not want to have warning return codes to contribute to the check result. To do this, you simply change Monitoring Parameter TMSImportStatReturnCodeWarn from the default value 4 to off. Or you might not want to have erroneous return codes starting from 8 be reported as critical result for development or quality assurance systems, but as warning. To achieve this, you would change TMSImportStatReturnCodeCrit from 8 to off and TMSImportStatReturnCodeWarn from 4 to 8. See more examples in table below.

Table 1. Monitoring Parameters Examples for TMS_ImportStat
Return Codes and Check Status Monitoring Parameters setting

Warning RC 4 → Warning, Error RC ≥ 8 → Critical (Default)

TMSImportStatReturnCodeWarn 4, TMSImportStatReturnCodeCrit 8 (Default)

Warning RC 4 ignored → Ok, Error RC ≥ 8 → Critical

TMSImportStatReturnCodeWarn off, TMSImportStatReturnCodeCrit 8

Warning RC 4 ignored → Ok, Error RC ≥ 8 → Warning

TMSImportStatReturnCodeWarn 8, TMSImportStatReturnCodeCrit off

All Warning and Error RC ignored → Ok (not recommended)

TMSImportStatReturnCodeWarn off, TMSImportStatReturnCodeCrit off

This check is accompanied by Daily Check TMS_Imports, which checks transport request imports back to the previous Daily Check schedule.

TMS_UserCompliance

Checks transport requests on user compliance

Description

Checks transport requests on the general compliance rule that owner and importer of a transport request are different users. If transport requests are found with the owner of the transport request equal to the user importing it, the Check Result will show the corresponding transport requests and the status will be Warning.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Daily

Depends on

FULLCHECK

TRFC_IN

Verify age of incoming transactional RFC records

Description

Displays an overview of all incoming tRFC records (see SAP transaction SM58) and displays the amount of records and the date / time of the oldest record for each different tRFC state.

The check will return a Warning if there are incoming tRFC records older than a configurable period of time (default one day).

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

TRFCAgeWarn

TRFC_OUT

Verify age of outgoing transactional RFC records

Description

Displays an overview of all outgoing tRFC records (see SAP transaction SM58) and displays the amount of records and the date / time of the oldest record for each different tRFC state.

The check will return a Warning if there are outgoing tRFC records older than a configurable period of time (default one day).

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

TRFCAgeWarn

TRFCOutStat

Verify the status of outgoing tRFC records

Description

Checks the status of outgoing transactional RFC records (see SAP transaction SM58) over a configurable period of time (default one hour). If the sum of records with status CPICERR, SYSFAIL or SYSLOAD is greater than the Warning or Critical threshold a corresponding alert is raised.

UPDATEQUEUE

Verify update queue for unprocessed records

Description

If the number of unprocessed update records older than UpdateQueueAgeCrit seconds exceeds UpdateQueueCountCrit the check turns Critical.

Otherwise, if the number of unprocessed update records older than UpdateQueueAgeWarn seconds exceeds UpdateQueueCountWarn the check turns Warning. Otherwise the check is Ok.

UPDATERECERR

Watch for erroneous update requests

Description

All erroneous or unprocessed update requests within the Full Check Cycle are reported as Warning messages.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Daily

Depends on

FULLCHECK

Monitoring Parameters

n/a

UpdateRecErrStat

Watch for erroneous update requests (RealTime Monitoring)

Description

SThe number of erroneous update records is checked during a configurable period of time (default one hour). Warning and Critical thresholds may be defined.

UpdateStat

Verify the updater is running

Description

If the SAP System's global update switch as displayed in transaction SM13 is deactivated, the check turns Critical. The reason why the updating has been deactivated is reported in the check message.

Reference Data
Managed Object

SAP System (ABAP, ABAP+Java)

Check Cycle

Basic

Depends on

RFCConnect

Monitoring Parameters

n/a

USER_PWD_AUDIT

Verify passwords of standard users

Description

Checks SAP standard users SAP*, DDIC, SAPCPIC, TMSADM and EARLYWATCH for well known standard passwords.

If the basis release of your SAP system is 7.00 onwards, the results of the original SAP report RSUSR003 is reported using the advanced check result format including tabular details for each checked user.

For SAP basis release 7.00 it depends on the patch level of the report RSUSR003. If recent SAP notes are not applied, Avantra Agent falls back to a simpler check procedure producing plain text output only.

The table displayed corresponds to the one displayed by RSUSR003, except that a new column Excluded is added to show which users have been excluded by Monitoring Parameter UserPWDAuditExclude.

If the Password Status of one or more users is reported in red color by RSUSR003, the check result will be Critical. If a user with red color Password Status is locked, USER_PWD_AUDIT will return a Warning status and the user is marked in yellow color in the result table.

Furthermore the lock status is checked. If one of the standard users is locked due to unsuccessful login attempts, by default a Warning is raised. This behaviour can be controlled by Monitoring Parameter UserPWDAuditFailedLogonSeverity: if this parameter is set to Critical a user locked due to unsuccessful login attempts will be reported as Critical.

If UserPWDAuditFailedLogonSeverity is set to OK (not recommended), a user locked due to unsuccessful login attempts will not contribute to the check result.

For SAP systems prior to 7.00 the check result will use an text table presentation and the following check logic which does not depend on RSUSR003. If a users password is set to a well known standard password, the check will return a Warning status, unless the user is excluded by parameter UserPWDAuditExclude.

This check additionally verifies if the users exist in each client. If the user SAP* does not exist, the check will return a Warning status (unless the profile parameter login/no_automatic_user_sapstar is set to 1) since login with password pass may still be possible.

The user does not exist message is suppressed for user EARLYWATCH for all clients other than 066.

WORKLOAD

Verify SAP System workload

Description

The average dialog response time of the SAP System during the last Full Check Cycle is reported and compared with the Warning (default 1000 ms) and Critical (default 2000 ms) thresholds. If responses times are higher than the defined thresholds, the check will return the corresponding Check Result.

Only transactions with at least DialogPerfMinStepCount steps are considered.