Basics of End-to-End Workload Analysis

Passport and distributed statistics records

If multiple SAP components are involved in the processing of a user request, each component writes its data record. In the communication flow between the components, a unique identifier (a Globally Unique Identifier (GUID). also referred to as a passport) is included and stored in each record so that the single records can be subsequently merged across individual components. The first component of a transaction step generates this passport (technically speaking, this is a GUID that is used to uniquely identify the transaction step) and transfers it to the next component that is part of the transaction step. For performance reasons, only passport data is transferred in the communication flow during a transaction step; the actual statistical data is first saved locally by the respective components and then transferred asynchronously to the central monitoring system or SAP Solution Manager. Based on their passports, the statistics records involved in a transactional step can be identified and displayed. In SAP Help, this technology is also referred to as distributed statistics records (DRSs).

Functionality of Java statistics

Just like the SAP NetWeaver AS ABAP server, the NetWeaver AS Java server creates statistics records that include comparable key figures and characterizing parameters. They are also stored in the Java instance file system. You can display the data either in the central monitoring system or in SAP Solution Manager. In the former case, a process referred to as an agent transfers the data to the central monitoring system and displays it in the central workload monitor (Transaction ST03G) and the central single record display (Transaction STATTRACE). In these monitors, you can see data for both the Java instances and the ABAP server, provided the central monitoring system has been configured accordingly. If you use SAP Solution Manager, the Solution Manager Diagnostics (SMD) agent provided in SAP Solution Manager transfers the data to SAP Solution Manager. There, it is stored in the BW system and can be displayed along with ABAP server data.

Use of Java statistics

In contrast to SAP NetWeaver AS ABAP, the con tinuous use of statistics records in workload analyses of SAP NetWeaver AS Java is not mandatory. However, SAP stipulates the use of Wily lntroscope statistics in the context of SAP Solution Manager to support Java-based SAP solutions. If the statistical records are not regularly activated on AS Java, they are activated in a target-oriented manner for the analysis in the event of end -to-end runtime analysis. For detailed analysis, the statistics records are used on the ABAP instance, and the Wily Introscope trace on the Java instance. As an option, you can also activate the ABAP runtime analysis and SQL trace on the ABAP instance, and the Java logging and SQL trace on the Java instance.