!--a11y-->
Setting Up IT Performance
Reporting 
You can se IT Performance Reporting to centrally display the development over time of the most important monitoring data in your monitored systems, to identify potential problems early.
This section describes the steps you need to perform to be able to use IT Performance Reporting in the System Monitoring work center of Solution Manager.
From a technical point of view, the IT Performance Reporting reports are based on the following elements:
● CCMS monitoring infrastructure – most performance values are determined here and stored for a short time in the central monitoring system (CEN).
● Central Performance History (CPH) – the collected values are stored and reorganized here for the long-term. The CPH is on CEN.
● Business Intelligence – the collected values are stored here in turn, and you have all of the options of BI for data management and display available.
To be able to set up IT Performance Reporting, you require a runnable BI, in which the basic BI configuration has been performed (more information: SAP Note 979581):
● You must have defined a logical system name for the BI client in transaction SCC4. The logical system should have the format <SysID>CLNT<client>, for example SYSCLNT001, for System-ID = SYS and the client 001.
● The MYSELF source system for BI must exist and be active. Check this by calling transaction RSA1. When you call the transaction, this source system is created semi-automatically with the name <SysID>CLNT<client>, if it does not already exist. If the system asks if it should also replicate metadata, choose no.
● The technical BI Content must be activated. This is automatically done in the background by the system (job name BI_TCO_ACTIVATION), when you execute transaction RSA1 for the first time. Wait until this job has completed before continuing with the installation.
For your BI, you require at least release BI Content 7.0.3 Add-On SPS 8. For this BI Content release, you also need to import the corrections from the following SAP Notes (for later BI Content releases, this is no longer necessary):
● 1065835 (Reporting Suite )
● 1108944 (Statistics data extraction: no data for recent hours)
● 1119468 (Runtime error RPERF_ILLEGAL_STATEMENT)
● 1119686 (CCMS Reporting Suite scenario)
To set up IT Performance Reporting, you must have set up the central monitoring infrastructure in the BI source system (usually the system in which Solution Manager is running, referred to as CEN in the following). In particular, monitored systems must be known to the monitoring infrastructure; if this is not yet the case, you need to perform the following steps:
● Create the CSMREG User
You require a
communication user with particular, restricted authorizations in all monitored
ABAP systems for communication between CEN, the monitored systems, and CCMS
agents (see
Creating the CSMREG
User).
To create the user, start transaction RZ21, choose Technical Infrastructure ® Configure Central System ® Create CSMREG User, and enter any password for this user.
● Activate Background Dispatching
For the data collection of the monitoring infrastructure to work correctly, you must have activated background dispatching in client 000 of all monitored ABAP systems.
To do this, call transaction RZ21, and choose Technical Infrastructure ® Local Method Execution ® Activate Background Dispatching.
● Activate Central System Dispatching
In CEN, you also need to activate central system dispatching in client 000.
To do this, call transaction RZ21, and choose Technical Infrastructure ® Configure Central System ® Activate Central System Dispatching.
● Monitor Remote ABAP Systems
You must have
created RFC destinations from CEN for monitored ABAP systems and made these
known to the monitoring infrastructure. More information:
Monitoring Multiple
Systems. You also need to register the CCMS agent SAPCCM4X on the hosts of
the monitored ABAP instances with CEN (more information:
Installing an Agent on
an ABAP Instance).
● Monitor Remote Java Systems
You must have
registered monitored Java systems and DSR components with CEN using CCMS
agents. More information:
Installing an Agent on
a Java Instance (Java Standalone System) or
Installing an Agent on
a Java Instance (Double-Stack System).
● Monitor Database KPIs
So that performance values for the database can be collected for IT Performance Reporting, proceed as described in SAP Note 1068204.

The Monitoring Setup Guide provides a detailed description of setting up the monitoring infrastructure: The document is available at the Internet address service.sap.com/operationsNW70, in the Monitoring area.
For IT Performance Reports, you do not, however, need to set up availability monitoring with GRMG and CCMSPING, the process for which is also described in the Monitoring Setup Guide.
You only need to create your central monitoring system (CEN) as a source system in BI if your CEN is not the Solution Manager system.
...
1. In the BI system, start the Administrator Workbench (transaction RSA1).
2.
In the navigation
bar, choose the function area Modeling, and there the
Source
Systems area.
3.
In the subscreen on
the right, right-click the root node
Source
Systems, and choose
Create.
4.
Select the
Automatically Create SAP
System radio button, and
choose
(Apply).
5. Make the required entries for CEN in accordance with the instructions in Creating an SAP Source System. Use the naming convention <System-ID>CLNT<client>.
6. Right-click the source system that you have just created, and choose Activate.
To be able to perform the setup, the user requires a large number of different authorizations, which are combined in the following roles:
● In BI, the user requires the authorizations of the roles SAP_BW_CCMS_SETUP and SAP_PI_CCMS_SETUP.
● If you CEN is not the Solution Manager system, the user also requires the authorizations of the role SAP_PI_CCMS_SETUP in CEN.
For the following reports, values for monitored Java systems are only transferred if the corresponding Java system has release SAP NetWeaver 7.10:
● Instance Availability
● Java Sessions & Threads
● Java Garbage Collection
...
1. To perform the setup for IT Performance Reporting, choose Reporting in the navigation bar of the System Monitoring work center, choose the Setup entry, and follow the link Configure IT Performance Reporting.
2. The system automatically switches to the BI client. You may have to authenticate yourself, depending on the security settings used when the RFC destination from Solution Manager to BI was created.
3. You only need to enter the RFC destination of CEN from the BI system in the Logical Name of CEN input field if your central monitoring system is not the Solution Manager system. The existing source systems are displayed in the modeling area Source Systems of transaction RSA1.
4. By default, the statistics and monitoring data for all systems that are monitored by the monitoring infrastructure of CEN is transferred to the BI. You can use the Satellite Systems input field to restrict this selection by explicitly specifying the system IDs of the systems for which data is to be transferred to the BI.
5. The indicator Schedule Proc. Chains Directly specifies that you want the system to immediately start loading the data.Although the process chains associated with the activated content are always immediately created, the scheduling is only performed if you leave this indicator selected.
We recommend that you leave the indicator selected.

You can monitor the status of the process chains in transaction RSPC.
6.
Choose
(Execute) . The runtime of the setup can be several hours in
extreme cases.

If you have already performed the setup, and you choose the link Configure IT Performance Reporting, an input screen on which you can adjust the configuration settings appears. Use this, for example, to change the selection of monitored satellite systems.
We recommend that you do not change the technical settings in the group boxes Data Targets, Process Chains, ABAP Statistics: Settings, and ABAP Statistics: Extractor.
7. Once you have successfully completed the setup, IT Performance Reporting is available to you in the System Monitoring work centre of Solution Manager.
