(Optional) End to end tracing enables an application developer or end user to trace a request that is sent from the client to the back-end. This spans the entire landscape where you can derive a correlation of traces at the client, server and back-end.
These correlated traces help in performance analysis and are centrally monitored on SAP Solution Manager. These are displayed as reports where you can extract information on failure of delivering a request, time taken for a request to reach a component and so on.
On the client side, the client framework enables an application developer to switch on the trace for messages. The client traces the request at predefined points and all these transactions/requests are recorded in a Business Transaction XML. Additionally, the client maintains a unique identifier in the HTTP header called the SAP Passport that is used to correlate traces across various components. This Business Transaction XML can later be uploaded to the SAP Solution Manager which is a central location to correlate all logging information.
The necessary condition for any client application to use the end to end tracing feature is that the application should be registered with SUP through the related registration mechanism as applicable for the respective device platform to acquire an application connection ID. This application connection ID should be included in every communication with the server. This application connection ID is also used by the administrator to enable end to end tracing for the respective client application.