Generate the E2E trace
2. Unzip the SAP Client Plug-in to the client where you will be executing the problematic workflow
3. Close any open web browsers before launching the SAP Client Plug-in
4. Browse to the location where you unzipped the SAP Client Plug-in, then right click on plugin-starter-gui.exe and choose 'run as administrator'
5. Set the 'Application' option to Microsoft Internet Explorer and click Launch
6. Under the "Business Transaction Name" property choose a descriptive name that describes the workflow that you are capturing and set the 'Next Step TraceLevel' to High
7. Before you start your end to end trace, you should first queue up the browser to the beginning of the problematic workflow that you wish to trace. If you are using BW as a datasource, you should also enable SAP Passport support and create a trace session on BW prior to executing your BOE workflow.
8. When you are ready to begin your workflow, click the "Start Transaction" button then execute only the workflow you are trying to trace. Observe that the number of sent bytes/received bytes will increase if the trace is working.
- As a best practice, only record the problematic step in your workflow and avoid extraneous clicks or steps not directly involved with reproducing the problem
- If you are tracing a workflow containing multiple clicks, select new step in the SAP Client Plug-in between each step in your workflow
9. As soon as you have completed your workflow press the "Stop Transaction" button.
10. Click OK to close the SAP Client Plug-in window
Upload the E2E trace to Solution Manager
1. Logon to Solution Manager system using SAPGUI
2. Run transaction code SOLMAN_WORKCENTER
3. Click on Root Cause Analysis work center
4. Click End-to-End Analysis
5. Select the Business Objects Cluster system and Apache Tomcat Server system(s) involved with the recorded E2E workflow (CTRL click to multi-select) then push the Trace Analysis button to launch E2E Trace Analysis
6. Expand the Manual Upload section under Business Transactions. Click browse under Upload BusinessTransaction.xml. Upload the BusinessTransaction.xml from the logs folder on the client where you executed the SAP Client Plug-in. The BusinessTransaction.xml will be in a folder with the same name that you gave to your Business Transaction when recording the workflow
7. Next, select your Business Transaction to trigger the trace collection process. Notice that currently the state shows that the Server-side traces are missing
8. When prompted with the Trace collection confirmation dialog, select the option Select systems for trace collection dynamically
9. Once the trace collection is complete, check the state of the Business Transaction and confirm that Server-side traces are available then select the first step under Transaction Steps and click *Display *to analyze the end-to-end trace step.