1608474 - Recording end-to-end traces for root cause analysis

You want to know how to collect HTTP traces from java and ABAP side in order to analyse issues in Enterprise Portal as frontend for specific application connecting to the backend.

The benefits on using the procedure from this KBA is that you will get detailed information about:

• RFC connection
• Backend background processes
• Total ammount of time for connection / processing / waiting 
• Isolating and identifying performance bottlenecks

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Read more...

• Enterprise Portal 6.40 and newer releases.
• Solution Manager Diagnostics for Java installed and configured.

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver Application Server for Java 7.1 ; SAP NetWeaver Application Server for Java 7.2 ; SAP Solution Manager 7.0 ; SAP Solution Manager 7.1 ; SAP Solution Manager 7.2 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Application Server for Java 7.1 ; SAP enhancement package 1 for SAP Solution Manager 7.0 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Solman, Trace Analysis, End-To-End Analysis (E2E), Enterprise Portal, EP, endtoend , KBA , SV-PERF-EP , SAP Enterprise Portal related performance issues , EP-PIN-AI , Application Integration , EP-PIN-OBN , Object Based Navigation , How To