Show TOC

Function documentationExtractor Framework Locate this document in the navigation structure

 

The Extractor Framework is the central infrastructure for SAP Solution Manager for data collection and distribution. It is used, for example, for interactive reporting and for end-to-end monitoring and the alerting infrastructure. In the extractor framework management, you can monitor the status of the extractors, identify the causes of errors, and resolve problems.

You use the extractor framework management, for example, in the following cases:

  • Data provided by extractors is not available in an application. You identify the cause of, for example, connection errors, and resolve them. You activate or release extractors, and set up inconsistent extractors again.

    Example Example

    In some scenarios, such as application log, portal activity report, or data volume management, the relevant extractors are inactive by default. You only activate an extractor when you actually use the scenario.

    End of the example.

  • To identify bottlenecks, monitor the performance of the extractors and their effect on systems. You identify potentially critical trends and patterns. You check, for example, the following:

    • How much data is collected?

    • How long does data collection take?

Features

  • The Status tab shows the status of the extractors, and the resource manager which started the extractors.

    • The Extractor Framework tab gives you an overview of the status of your extractors. By default, the status of the last 20 runs is shown. You can:

      • To identify extractors with errors, for example, you can filter the extractors by status in the extractor summary area.

      • To display error messages or information about extractor runs and their phases, select an extractor.

      • You can activate inactive extractors and release locked or inconsistent extractors.

        For further information, see Identify Extractor Errors.

      • You can change the configuration of an extractor.

        For more information, see Changing Extractor Configuration.

    • On the Resource Manager tab, you can:

      • Show the status and the next planned run of the resource manager. By default, the resource manager runs once a minute.

      • If, for example, no extractors are running, you can call the job log. You can check whether a resource restriction has been exceeded.

        The job log is only available when the resource manager is running.

        For more information, see Adjust Resource Restrictions for Extractors.

  • On the Configuration tab, you can:

    • In the RFC management, change the maximum number of RFC connections which can be open at the same time in a managed system.

      For more information, see Adjust Extractor Resource Restrictions.

    • You can specify logon groups, to only allow extractor runs for specified instances in the SAP Solution Manager system.

      For more information, see Specify Logon Group.

    • You can specify the number of worklist items for the resource manager.

      The field Number of Entries in the Worklist has the default value 50. The resource manager tries to process a maximum of 50 extractors consecutively, per run.

      To increase the performance of the extractor framework in large system landscapes, you can increase the number of entries in the worklist, until all extractors can be restarted.

      Caution Caution

      If the number of entries in the worklist is too high, the resource manager runtime increases, and can delay the next resource manager run.

      Only change this value in consultation with SAP support.

      End of the caution.

  • On the Performance tab, you can:

    • In the Extractor Framework tab, you can display how many data records the extractors have created and saved in the SAP NetWeaver BW, during a period.

      You can check which systems have a heavy load, and which extractors are causing it. You identify potentially critical trends and patterns. You identify the cause of a pattern, identify its extractor, and ensure that the performance data is from normal processes.

      The Runtime is the time which an extractor needs, to collect data. The mean write time is the average time that an extractor needs to save a data record in SAP NetWeaver BW.

    • In the Resource Manager tab, you can display the runtime and throughput of the resource managers in a period. You identify irregularities, to prevent problems or identify their cause.

      The Runtime is the time which the resource manager needs, to process the entries in the worklist.

      The Throughput is the percentage of extractors starteted by the resource manager (1=100 %). A low percentage indicates a bottleneck. You can try to reduce the resource restriction. For more information, see Adjust Resource Restrictions for Extractors.

  • In the Exceptions tab, you can access a graphical interface to the application log (transaction SLG1). A problem overview is displayed. To show error messages, select the problem. The ID of the entry in the worklist, which the resource manager could not start, is displayed.