The purpose of this page is to explain how to generate an HTTP trace log for EPM client tools using the Fiddler utility.
To troubleshoot client side EPM Add-In issues, a Fiddler trace log can be used to help analyze the communications between the web services used in your EPM products. Fiddler is a third-party web tracing tool created and distributed by the company Telerik.
Fiddler can trace web traffic activity (HTTP requests and responses). The utility can be used to get information on:
- The client web requests and web server responses
- The amount of time dedicated to server-side and client-side processing
- The content of any errors returned from the application or web server
NOTE: Fiddler is an HTTP proxy and may not work with some VPN software. For highly secure sites or production environments permission may be required from your IT Department to install or run this software.
The following guide will instruct you to obtain and install the product, and then how to generate a trace file using it.
Where to get the Fiddler utility
The tool is quite small (~730Kb), and can be downloaded from the following web site link: http://fiddler2.com/get-fiddler
Fiddler2 is the most compatible version, and is the version we recommend unless you have been specifically advised to use any other version. Other versions are available corresponding to the Microsoft .NET Framework version you have installed on the client machine.
The installation only requires a few simple configuration steps:-
- Double-click the 'Fiddler2setup.exe' file (or 'Fiddler4setup.exe' if advised to use this version).
- You may be prompted to allow the installer to make changes on your machine. To install the tool you must choose 'Yes'.
- The Fiddler license agreement popup appears. If you agree with the Terms and Conditions of usage then click 'I agree' to install the product.
- Select a destination folder for the Fiddler application files (by default this is your 'Program Files' folder). Only 2.4Mb of space is used by the application.
- Click 'Install' to install the Fiddler files. The installer will report progress in the 'Details' section of the installer screen.
Once installed, the application will attempt to open the Fiddler web page where it will check that you have installed the latest version. Once the check is complete, if you are connected to the internet, then you will see the "Update was successful" page. You can use the 'Learn More' button on this page to find out more about the tool.
The installer will have created a shortcut in your 'All Programs' list (in the Windows Start menu) in order to launch the tool.
Where to run the Fiddler tool
We are looking to capture web traffic communication between the client and server. It is usually run on the client machine.
If the EPM product client is installed on a Citrix server, then this is where the Fiddler tool will need to be installed.
Output produced by Fiddler
The Capture function ('F12' key) can be used to start and stop the debugging process in Fiddler once the tool is installed.
With the capture process running you should recreate your incident, and then stop the capture (by toggling the function or pressing the F12 key again) once the steps have been completed.
Fiddler produces a trace file of the session that has a ".SAZ" file extension. The trace file can be saved and attached to the case for Development inspection.
When tracing is stopped the trace log is written to the following default location on the client machine:
C:\Users\<user name>\My Documents\Fiddler2\Captures\
Fiddler options for capturing HTTPS sessions
To capture HTTPS session you must set 'Capture HTTPS CONNECTs'. You can find this option from Tools->Fiddler Options menu under HTTPS tab. Please ensure that you check the option 'Decrypt HTTPS traffic' as well.
Fiddler developers have created a series of YouTube videos to guide you through how to use the tool.
These are available from this web page: http://www.youtube.com/user/TelerikInc
Related SAP Notes/KBAs
SAP KBA 1766704 - How to use Fiddler to collect HTTP and/or HTTPS traces?
SAP KBA 1909019 - How to troubleshoot connectivity issues between BI and BPC data sources with Fiddler
SAP Note 1709467 - Troubleshooting BPC ODBO / XMLA issues