Skip to end of metadata
Go to start of metadata

Pull Data Providers This means the SAP Solution Manager is asking for metric data’s. The different pull data provider types:

• ST_PI:

Solution Manager System calls ABAP function modules in the managed systems which are delivered as part of ST-PI plug-in. Scheduling: Scheduled in the Solution Manager (one extractor per managed system). One RFC call from the Solution Manager to the managed ABAP system which contains a list of all metrics that have to be collected. The metrics are then collected locally on the managed system by using function modules which are part of the ST-PI plug-in. The metrics are sent back in the same RFC call.

Examples:

1-Collect local metrics from the local CCMS of the ABAP system

2-ABAP Work Process information, ABAP Memory information

• ST:

Solution Manager calls ABAP function modules which collect information from the Solution Manager. Scheduling: Scheduled in the Solution Manager (exactly one extractor) One internal RFC in the Solution Manager which calls multiple function modules locally to retrieve metrics.

Examples:

1-Data from the CCDB (E2E Change Analysis)

2-Data from Early Watch Alerts (EWA)

• ST_BW:

Solution Manager calls ABAP function modules which collect information from the BW system of Solution Manager (internal or external). Scheduling: Scheduled in the Solution Manager (exactly one extractor). One RFC from the Solution Manager to the attached BW system (internal or external) to retrieve metrics from BW info cubes.

Examples:

1-Data from the info cubes for E2E Workload Analysis

2-Data from the info cubes for E2E Exception Analysis

• DB:

Solution Manager retrieves database metrics from the ADBC connections of DBACockpit Configuration. Scheduled in the Solution Manager (one extractor per database). One function module which connects to the database via the maintained ADBC connection to extract multiple DB specific metrics.

Examples:

1-Database backup status

2-Database tablespace usage

The configuration for all metrics collected by Pull data providers is stored in the directory tables of the Solution Manager.

GENERAL TROUBLESHOOTING

Necessary tools for analyzing problems with pull extractors:

  • Alerting Framework. To start it, proceed as follows:
  1. Start transaction sm_workcenter and select tab Solution Manager Administration.
  2. Select Infrastructure - Framework - Alerting Framework.
  • Managed Systems Configuration. To start it, proceed as follows:
  1. Start transaction solman_setup.
  2. Select Managed Systems Configuration, select the corresponding system, and choose Configure System.

Necessary information:

  • ID and name of the managed object
Checks for Pull Extractors

If there are gray metrics from one managed ABAP system, from a managed database or from the SAP Solution Manager system itself, you should check the data provider responsible for that object:

  1. Start Alerting Framework.
  2. Filter for the correct Extended Context Type.
    • If you have grey metrics from a managed ABAP system, filter for ST_PI. There should be one extractor per managed ABAP system.
    • If you have grey metrics SAP Solution Manager functions and indicators from the SAP Solution Manager system itself, filter for ST. There should be exactly one extractor.
    • If you have grey metrics from any database, filter for DBMS. There should be one extractor per managed database.
  3. Choose the extractor for the affected managed object, and if the status of the extractor is not green, check the message in the Extractor Log shown in the lower frame, and generally proceed according to the message text.
  4. If one of the following errors occured, proceed as follows:

    1. For Extended Context Type = ST_PI: If the message says Function Module <name>> not available in system <system ID>, then check whether the software component ST-PI in the managed ABAP system has the correct version. The correct versions are listed in  SAP note 1483508.
    2. For Extended Context Type = ST_PI: If there is an issue with the RFC connection to the backend (e.g. the user of the RFC connection is locked, or there is an authorization missing), then check the configuration of the affected managed system in the Managed Systems Configuration in the SOLMAN_SETUP. In step Connect managed system the RFC destinations necessary are created, additionally, you can check existing connections by choosing Test
    3. For Extended Context Type = ST_PI: If the message says PPMS Modelling is not valid. Check PPMS Keys im Extractor Log, reperat the configuration of the affected managed system in the Managed Systems Configuration in the transaction SOLMAN_SETUP.
    4. For Extended Context Type = ST_BW: If the message says Data is not available in BW (check data in RCA), then go to work center Root Cause Analysis, choose the affected managed system, and choose Workload Analysis. If no data is available for the system, reperat the configuration of the system in the Managed Systems Configuration in the SOLMAN_SETUP. If still not data is availabe for the system, check the Diagnostic Center for errors. It is located in the work center SAP Solution Manager Administation -> Infrastructure -> BI Reporting. Choose the reporting scenario System Reporting, and check the Self Checks.
    5. For Extended Context Type = DBMS: A possible cause for an error could be issues with the DBA Cockpit connection. For more information, check SAP note 1766109.
  • No labels