SAP Library - Find your answers

he Central Performance History of the monitoring architecture allows you to save performance values of the monitoring architecture long-term, and to output these values in reports to compare the current performance data with its earlier development.

The system only collects values for the MTE classes that you have selected for this purpose. You do this by assigning MTE classes to Collection and Reorganization Schemata. These schemata contain information about how long, and in which resolution, performance values should be collected. To obtain an overview of this type of which data is collected in the Central Performance History, you required the collection and reorganization schemata that are assigned to the individual nodes.

The view displays the following information:

· Assigned collection and reorganization schema

· Resolution of the collected performance values

· Collection method (see Collecting and Reorganizing Performance Values)

· Time zone of the data collection (if explicitly specified)

Procedure

To activate the Central Performance History technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Collect./Reorg.Schema Assignment, or choose Display Assignments of the Central Performance History (). The alert tree now no longer displays the alert status and reported values, but the assigned Collection and Performance Schemata.

Displaying Central Performance History Reports

Use

You can output Central Performance History (CPH) reports in a number of different ways (see Scheduling and Executing a Report). One of the possibilities is direct output to the screen.

You can also display at any time reports that you have saved in the database. When you do this, the report is not executed again using the report definition, but rather the previously executed report is displayed, with the performance values from the original execution.

The displayed report is identical in both cases.

Procedure

1. You can display a report that is saved in the database from several functions:

¡ In the overview screen of the CPH (transaction RZ23N), choose, in the Reporting group box, the Report Browser pushbutton.

¡ On the screen for scheduling and executing reports (Central Performance History Report Execution), choose Goto® Report Browser.

2. In both cases, the Display Central Performance History Reports screen appears. On the left half of the screen, the system displays all executed reports, grouped by the name under which the reports are stored in the database:

<Date>,

,

By default, the name specified above is the name of the report definition; you can, however, also explicitly specify a name when Scheduling and Executing a Report under which the corresponding report execution is to be grouped in the Report Browser.

3. Expand the desired report definition and select the desired time point of the report execution by double clicking it. Choose the desired report on the right of the screen.

If you display a report directly on the screen, the report is output identically.

4. There are two display modes for displaying reports: one-dimensional and two-dimensional. Choose the Switch Display Mode pushbutton to switch between the two modes. The display modes have the following properties:

5. If you want to display the header data of the report, choose Report Details (see Displaying Report Properties).

Central Performance History of the Monitoring Architecture start page

Our development system is way out of sync, both configuration- and data-wise. We would like to refresh our development system from the production system. How can this be accomplished? What things we need to be aware of? I know we can restore the production system (PRD) from from tape to the development system (DEV,) but that will wipe out everything including transports, notes history, etc

The system copy guides can be found at http://service.sap.com/instguides*. Different backup/restore procedures exist for the different databases supported by SAP.

If you restore PRD over DEV, it will wipe out everything. You should therefore find a point in time in which development projects finish and are brought into production. You should only re-create DEV from a backup of PRD if both systems are more or less in sync or if your development teams agree that certain developments are lost.
* User authorization needed to access the service marketplace.

3.0D Basis 300
3.0E Basis 300
3.0F Basis 300
3.1H Basis 310
3.1I Basis 310
4.0B Basis 400
4.5B Basis 450
4.6C Basis 460
4.71 Basis 6.20
4.72 Basis 6.20
5.00 Basis 6.40 (ECC 5.0 - Enterprise Core components)
6.00 Basis 7.00 (ECC 6.0)
All of those have increased business functionality and interfaces to other systems (CRM, BW etc.)