Ansicht
Dokumentation
SOLMAN_SLR_CPH - Configure Central Performance History
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
The Central Performance History (CPH) is configured to collect the desired indicators, by assigning the indicators to a collection and reorganization schema. In a collection and reorganization schema, you specify how long performance values are saved in which expansion of the CPH. The data collection and reorganization of the performance values are carried out as background jobs.
The first time the CPH is configured for Service Level Reporting purposes, an adjusted schema must be set up if necessary.
Choose 1 x a minute as the measuring interval. The measurement data must be stored on expansion level "Minutes Per Day" for at least eight days (= EWA cycle + 1 day). SAP recommends that the data is stored for 8 to 14 days. From the viewpoint of Service Level Reporting, it is not necessary to carry out a reorganization for data aggregation purposes. Therefore choose "Deletion after 14 days" as the reorganization interval if possible. If you require an aggregation on higher aggregation levels (hours, days, weeks, and so on), the minimum retention period must be guaranteed. Subsequent reorganizations on higher aggregation levels and longer deletion intervals are possible, but not for the continued usage of the Service Level Reporting. These specifications correspond to schema Solution Manager Availability.
You have installed CCMSPing.
Set up a collection and reorganization schema if you do not want to use schema Solution Manager Availability- Choose Maintain Schema.
- On the screen that appears, in the menu, choose Edit → Screen for Enhanced Configuration.
- Name the schema.
- Specify the collection and reorganization parameters in the CPH measured values duration maintenance panel, for example:
Measurement interval: 1x per minute.
Reorganization: No Aggregation. Delete after 14 days.
=======================================================================
Minutes 1/4 Hour Hour Day
Daily Aggregate 14 0 0 0
Monthly Aggregate 0 0 0 0
Quarterly Aggregate 0 0 0 0
Yearly Aggregate 0 0 0 0
Weekly Aggregate 0 0 0 0
X-day Aggregate 0 0 0 0
X = 0
=======================================================================
- Save and navigate back to the initial transaction.
- Choose Assign Schema.
- Different systems have different MTE classes. First of all, the MTE classes of the local system are displayed. To add the MTE classes of other systems to the list, select the required systems and choose MTE - Classes from System.
- The MTE classes of the selected systems also appear in the list of MTE classes.
- Select the SID of the system in whose CCMS the availability data of the system that is to be monitored is reported.
- Assign the required MTE classes of the availability indicators to your collection and reorganization schema. You cal also select more than one system and MTE class. The following MTE classes are possible indicators:
MTE Class ,,,,Availability Type
Availability_SysPercent_ABAP ,,System availability ABAP stack*
Availability_SysPercent ,,System availability ABAP stack
Availability_SysPercent_JAVA ,,System availability JAVA stack*
Availability_InstPercent ,,Instance availability
Availability_RFCPercent ,,Instance logon availability
Availability_GroupPercent ,,Logon group availability
- (*)only for JAVA or ABAP/JAVA double stack monitoring.
Other MTEs are not supported by Service Level Reporting.
- Choose Assign Schema.
You can check which background jobs the system has started by proceeding as follows:
- In the menu, choose Goto → Background Jobs.
- Carry out Setup Service Level Reporting.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 5500 Date: 20240523 Time: 170654 sap01-206 ( 82 ms )
