Passport

The passport allows the creation of Distributed Statistics Records (DSRs) and of performance traces across component boundaries.

If statistics records are written beyond component boundaries, the passport is sent together with the communication between the components. Among other things, it contains a GUID that is generated with a new Logical Unit of Work (LUW) and which is used when calling other components within the LUW. By evaluating the DSRs globally, you can collect and analyze all of the data for a LUW. The passport contains a trace flag with which performance trace information can be written for every component involved in a LUW for exactly this LUW. 

The passport corresponds to the certificate subrecord (cert subrecord) of the DSR and contains the following fields:

• TransID/GUID
• TraceFlag
• Initial SysID/ComponentID
• Initial ServiceType
• Initial Action
• Initial ActionType
• Initial UserID

  These fields are only filled when the passport is created. All subsequent components leave these fields unchanged.

• PreSysID/PreComponentID with the ID of the previous system or previous component

The figure below shows how the passport is forwarded and linked to the relevant statistics records:

1. The passport is created in the component in which a LUW is initiated. In this example, this is the J2EE Engine. The J2EE Engine sends the passport to the ABAP Engine and writes a Call subrecord.
2. The ABAP Engine receives the passport and stores its data as a certificate subrecord. It calls another component, for which a call subrecord is written.
3. The passport is transferred to another component during the RFC call and the certificate subrecord is written in turn into the statistics there.
4. The complete statistics records are transferred to the central SAP monitoring system (CEN) by agents and displayed.