Monitoring and Optimizing MAI Data Reporting Performance

Note Note

This section is part of the technical documentation of the E2E Monitoring and Alerting Infrastructure reporting scenario.

End of the note.

You can monitor three main performance-critical areas for interactive reporting data provision and processing:

Data Loader (writing the data into BW data store objects)
Mapping (Adjusting Data Structures to Save in BW)
Further processing in BW (write DSO data into InfoCubes)

Check Mapping Performance

Before saving in BW, the monitoring data structures are mapped. To monitor the performance of this process, start the alert monitor in the BW system of your SAP Solution Manager system.

Proceed as follows:

Start the alert monitor with transaction code rz20.
In the monitor collection SAP CCMS Technical Expert Monitors, start the monitor All Monitoring Contexts.
Expand the monitor tree along the following path: All Monitoring Contexts <instance name> CCMS BI REPORTING Runtimes CL_E2E_DPC_BI_MAPPING_TOTAL .
The performance node specifies the run time of the mapping. Check this node in all instances in your system. The run time should be well under a minute. 10 seconds is generally acceptable.
If the value is too large, check the following:
- Check the reorganizations, with the report SMBI_PN_SHOW_MESSAGES (see Troubleshooting Tools).
- In transaction sm37, check the log of job E2EREP_MAPPING_CLEANUP. Is it running regularly and inconspicuously?

If there is no indication of the cause of the error, reorganize the mapping tables manually. You can use different reorganization settings from those in the job. Proceed as follows:

Start transaction se38, and run the report E2EREP_MAPPING_CLEANUP.

It reorganizes the mapping tables. The default job settings are:

Option	Default values:
Delete obsolete data records	`X`
Days until data record becomes obsolete	`20`
Connect records for same metrics	`X`
Delete invalid gap records
Reduce Gap Records	`X`
Max Number of Gap Records	`10`
Adjust Gap Record Counter	`X`

Copy these settings, but reduce the value in the field Max. Number of Gap Records successively, and check whether the run time goes down.

If the performance is unsatisfactory but you can find no cause, your system hardware is probably inadequate for the system performance requirements. In this case, you have two options:
- Increase the capacity of the systems.
- Reduce the reporting system load by saving less metrics. Use the report SMREP_DPC2BW_EASY_CONFIG, which is described in the section Reducing the Number of Metrics Saved, below. Metrics which you no longer save in BW are still available in alerting.

Check the performance of writing in the InfoCubes

The monitoring metrics are first written into DataStore objects in BW. They are saved permanently in InfoCubes by two jobs whose run time also indicates the overall reporting performance:

The job CCMS_CPH_RAW_DATA_UPDATE writes the original data from DSO 0CCMBUFF into the InfoCubes, hourly.
The job CCMS_CPH_AGGR_DATA_UPDATE writes the original data from DSO 0CCMAGGR into the InfoCubes, hourly.

To check the run time of the job, in the SAP Solution Manager BW system, start the transaction sm37 with the job name. After a calibration phase which is always required when the jobs have not run for some time, the jobs should satisfy the following conditions:

The job CCMS_CPH_RAW_DATA_UPDATE should have a run time of well under an hour.
The job CCMS_CPH_AGGR_DATA_UPDATE should have a run time of well under a day, optimally under an hour.

If the performance is unsatisfactory, the hardware is probably inadequate for your requirements. In this case, you have two options:

Increase the performance of the systems, in particular, the database.
Reduce the reporting system load by saving less metrics. Use the report SMREP_DPC2BW_EASY_CONFIG, which is described in the section Reducing the Number of Metrics Saved, below.

Reduce the number of metrics saved

In the default configuration, nearly all monitoring metrics are saved in BW, but such a history is only required by a few metrics for interactive reporting and the delivered Dashboards and Dashboard Apps. You can deactivate this history for all other metrics, to reduce system load. Use the report SMREP_DPC2BW_EASY_CONFIG.

Caution Caution

For metrics whose history you deactivate with this tool, the Send Values to SAP NetWeaver Business Warehouse flag is still set in your attributes.

End of the caution.

This report specifies for which metrics history data is saved in BW. Metrics required by reporting are preselected.

Proceed as follows:

Start transaction se38, and run the report SMREP_DPC2BW_EASY_CONFIG.
You can specify in detail which metrics are saved in BW, in the next screen. The default setting is All Metrics are Written in BW. To reduce the number of metrics saved, choose Write Selected Metrics in BW.
Only those metrics are saved in BW which are required by delivered dashboards or interactive reporting reports. Only these metrics are then available for the Metric Monitor.
In the next group box, the metrics which are still saved in BW after this reduction, are displayed, grouped by subject area. You can further reduce the number of metrics to save, by deactivating more metrics, but reports or dashboards which use these metrics no longer get values. The values of these metrics can also no longer be displayed in the metric monitor.

Note
Further reduction of the amount of data is not normally required, because choosing Write Selected Metrics in BW already reduces the number of metrics in BW by an order of magnitude.

End of the note.
In the field Other Metric Types, you can explicitly specify the technical names of the metrics for which you still require history data in BW. The Send Values to SAP NetWeaver Business Warehouse flag must also be set in the metric attributes.

Caution Caution

Run the program again when you have installed or activated new monitoring content.

End of the caution.