Show TOC

Procedure documentationConfiguring Collection of Single Exceptions

 

You can collect single exceptions for ABAP systems, non-ABAP systems, and web services. You can specify which log stores to collect in the central exceptions store per technical system. For each log store, you can define filters to limit the collection to business-critical exceptions and avoid excess data volume. You can save log stores, categories, and filters as a template to simplify the configuration of additional systems.

For example, exception management supports collection of the following types of technical, single exceptions for ABAP systems:

  • Application log errors

  • Runtime errors (dumps)

  • Job errors

  • System log errors

  • Update errors

  • Web service exceptions

The exceptions store can provide data to the central Alert Inbox and other MAI-based applications. For ABAP systems, you can activate MAI-based monitoring directly in the exception management configuration.

Note Note

If required, you can add generic 3rd party log stores to exception management. If there is no existing log store that corresponds to the format of the 3rd party log store, you may need to contact SAP support for assistance with setting up the required metamodel.

End of the note.

Procedure

  1. In SAP Solution Manager Configuration, perform the Exception Management scenario.

    The relevant data extractors are scheduled for the selected scope.

  2. In the Exception Management application, you can make settings for self-monitoring. You can administer the exception management extractors. You can activate and deactivate extractors, and display the extractor log and detailed information about each extractor. The log shows when the extractors last sent exceptions from the managed systems, the quantity of data, and whether there were any problems.

More Information

Extractor Framework.