10.3.1 System Requirements
The following technical prerequisites need to be fulfilled to use the Batch Input Monitoring functionality:
• Managed system has an SAP Basis ≥ 4.6C
• ST-A/PI01M is installed on the managed system
• SPS23 is installed on the SAP Solution Manager system
10.3.2 Available Key Figures
The following key figures are available:
Name Analysis
Transaction
Description
Sessions in specified status(es)
SM35 Number of sessions in the defined status(es)
Errors per session SM35 Number of errors that occurred when the queue was processed.
Transactions processed per session
SM35 Number of transactions in the defined status(es)
Transactions in specified status(es)
SM35 Number of transactions processed in the evaluated sessions
Job cancellation SM37 For every session, one background job for processing is created when background processing is chosen. If enabled, the monitor checks whether the job was canceled.
10.3.3 Configuration on Monitoring Object Level
Select the key figures you want to monitor and specify the period for the data collection as described in chapter Setup Procedure. In tab “Detail Info” maintain the selection criteria for the monitoring object.
The following selection criteria are available:
o Session Name (mandatory, wildcards possible):
Enter the name of the session or the group of the sessions that should be monitored (the information required can be found in transaction SM35 of the monitored system).
o Creating Program (optional, wildcards possible):
Name of the program that created the session (information about the creating program can also be found in transaction SM35).
o Created by (optional, wildcards possible):
Enter the name of the user who created the session.
o Max. Session Age (optional, integer in days):
Define the age of sessions to be taken into account when data is collected. Via this parameter you can avoid the alerting on old batch input session.
o Max. Alert Age (optional, integer in days, default 14 days):
Define how long the data collection history should be kept for the monitoring object. If not set or set to more than 14 days it is automatically restricted to 14 days.
10.3.4 Key Figure “Sessions in Specified Status(es)”
This key figure monitors the number of sessions that fulfill the configured selection criteria. The following selection criteria (in addition to those on monitoring object level) are available:
o Status(es) (mandatory):
Define the statuses of the sessions that should be considered for monitoring. The following statuses are possible:
o C Being created o E Incorrect
o F Processed o N New
o R In Processing o S In background o ‘Collector mode’ (mandatory):
Define how the data collector should evaluate the data. The following collector modes are possible:
o ALL: This collector type evaluates the total number of all batch input sessions listed in SM35 that fulfill the configured selection criteria, regardless of whether a session has already been alerted on or not. How far into the past sessions are monitored is determined by the configuration of
parameter 'Maximum Session Age' on monitoring object level.
o DELTA: This collector type keeps a data collection history to determine whether a session has already been alerted on. Only sessions that have not yet been alerted on are considered during the data collection. The length of the history of the data collection is restricted by parameter ‘Maximum Alert Age’ on monitoring object level.
o ‘Unit’ (mandatory):
Define whether the total number of sessions or the percentage of sessions should be monitored. The following entries are possible:
o Number: The number of sessions matching the selection criteria is taken into account for rating the alert.
o Percentage: The percentage in comparison to all found sessions is taken into account.
Define the threshold values for yellow and red alerts. There are two sets of threshold values: One for monitoring if too few sessions have been found by the data collection (‘if less than’) and on for monitoring if too many sessions have been found by the data collection.
You can configure both sets of threshold values or only one set. If both sets are configured each alert evaluation results in two alerts: One for ‘too few’ and one for ‘too many’.
An alert is created if these threshold values are exceeded (‘if more than’) or if the measured value falls below these values (‘if less than’).
This key figure can be used to check if specific sessions are “hanging” in a defined status e.g. being created and are not processed for long period of time which can lead to performance problems. Other possible use-cases are:
o Trigger an alert if there is at least one session in status not processed (E).
o The data collector runs on an hourly basis. At least 10 sessions should be processed successfully (status F=Processed and R=in Process) each hour.
At least 90% of the sessions found should be in status 'processed'.
10.3.5 Key Figure “Errors per Session”
This key figure monitors the number of errors per session that fulfills the selection criteria configured for the monitoring object. These errors usually indicate transactions whose processing cannot be finished. For the key figure, the following additional selection criterion is available:
o Unit (mandatory):
Define whether the total number of errors or the percentage of errors should be monitored. The following entries are possible:
• Number: The number of errors matching the selection criteria is taken into account for rating the alert.
• Percentage: The percentage of errors in comparison to all transactions defined per session is taken into account.
Define the thresholds for yellow and red alerts (‘if more than’). An alert is triggered if these thresholds are exceeded. Observe that, though technically possible, it does not make sense to configure thresholds for the
‘if less than’ set for this key figure.
10.3.6 Key Figure “Transactions Processed per Session”
This key figure monitors the number of processed transactions per batch input sessions that fulfill the selection criteria configured for the monitoring object. Every batch input session consists of at least one transaction with several screens to be processed. If the processing of these screens and transactions fails, the number of processed transactions is smaller than if the processing was successful. Thus monitoring the number of processed transactions allows detecting problems in the processing of batch input sessions.
There are no additional selection criteria available for this key figure.
Define the threshold values for yellow and red alerts. There are two sets of threshold values: One for
monitoring if too few transactions have been found by the data collection (‘if less than’) and on for monitoring if too many transactions have been found by the data collection.
You can configure both sets of threshold values or only one set. If both sets are configured each alert evaluation results in two alerts: One for ‘too few’ and one for ‘too many’.
An alert is created if these threshold values are exceeded (‘if more than’) or if the measured value falls below these values (‘if less than’).
10.3.7 Key Figure “Transactions in Specified Status(es)”
This key figure monitors the number of transactions per batch input sessions that fulfill the configured selection criteria. The following selection criteria (in addition to those on monitoring object level) are available:
o Status(es) (mandatory, multiple entries possible):
Define the status of the transactions you would like to monitor. The following statuses are possible:
o D Deleted o E Erroneous o F Finished o P To process o Collector Type (mandatory):
Define how the data collector should evaluate the data. The following collector types are possible:
o ALL: This collector type evaluates the total number of all batch input sessions listed in SM35 that fulfill the configured selection criteria, regardless of whether a session has already been alerted on or not. How far into the past sessions are monitored is determined by the configuration of
parameter 'Maximum Session Age' on monitoring object level.
o DELTA: This collector type keeps a data collection history to determine whether a session has already been alerted on. Only sessions that have not yet been alerted on are considered during the data collection. The length of the history of the data collection is restricted by parameter ‘Maximum Alert Age’ on monitoring object level.
o Unit (mandatory):
Define whether the total number of transactions or the percentage of transactions should be monitored.
The following entries are possible:
o Number: The number of transactions matching the selection criteria is taken into account for rating the alert.
o Percentage: The percentage of transactions relative to all transactions of the found sessions is taken into account for rating the alert.
Define the threshold values for yellow and red alerts. There are two sets of threshold values: One for
monitoring if too few transactions have been found by the data collection (‘if less than’) and on for monitoring if too many transactions have been found by the data collection.
You can configure both sets of threshold values or only one set. If both sets are configured each alert evaluation results in two alerts: One for ‘too few’ and one for ‘too many’.
An alert is created if these threshold values are exceeded (‘if more than’) or if the measured value falls below these values (‘if less than’).
10.3.8 Key Figure “Job cancellation”
This key figure monitors whether the background job responsible for the processing of those batch input sessions that fulfill the selection criteria configured on monitoring object level has cancelled. When a batch input session is processed in background a corresponding background job is scheduled. If this job fails, the running session cannot be processed and its status is sometimes not updated.
There are no additional selection criteria available for this key figure. All selection criteria have to be maintained on monitoring object level.
Specify which status the alert should have in case the respective background job cancels.
10.3.9 “Detail Info” Lists
The “Detail Info” list for this monitoring object differs for each which key figure:
For the key figures monitoring the sessions and transactions within the sessions, the “Detail Info” list displays all sessions that contributed to the alert.
For key figure “Job cancellation” the “Detail Info” list displays the job log for the cancelled background job.
You can also configure transaction SM35 as analysis tool for this application monitor. In case of assigning this monitor to an interface step, make sure to choose the correct target system call option (sender or receiver) for the transaction call.
11 Monitoring of PI Message Processing
11.1 Background Information
The message flow via SAP PI can be very complex, passing different components (such as adapter engines with the module processor and messaging system, integration engines with their pipeline processing
including Java & ABAP proxies, business process engine etc.) and using different adapter types (such as File-, JMS-, IDoc-, RNIF-adapters etc.).
Messages sent to SAP PI can come from various sources in the sender system and can use several different interface techniques. Depending on the interface technique used either the message is sent to the
Integration Server directly or the Java based Adapter Engine receives the message from the sending system and converts it into an XML format. The XML message is then forwarded to the ABAP based Integration Server where messages processed or forwarded to the Business Process Engine (e.g. for merging of messages). From the Integration Server the message is sent to the receiver system. Depending on the document type expected by the receiver system, the message may again pass via the Adapter Engine.
This complexity makes it difficult to track and monitor the flow of a specific message across SAP PI.