Name: Applying Debugging Tools - SAP Customer Data Cloud
Uploaded: 2023-4-18
Duration: 276 s
Description: In this video, we will go over several debugging tools you can use with SAP Customer Data Cloud.We'll cover the Fiddler Web Debugger, the Charles Webb Debugger, the server response log and the Web SDK Debug UI. You can view the documentation on the SAP Help Portal for more details:Debugging Tools | SAP Help Portal

Share feedback

Planned maintenance of Practice Systems

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div>In this video, we will go over several debugging tools you can use with SAP Customer Data Cloud. We'll cover the Fiddler Web Debugger, the Charles Webb Debugger, the server response log and the Web SDK Debug UI. You can view the documentation on the SAP Help Portal for more details:<a href="https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD/8b8d6fffe113457094a17701f63e3d6a/41505ffc70b21014bbc5a10ce4041860.html?q=fiddler%20web%20debugger" rel="nofollow noopener noreferrer" target="_blank">Debugging Tools | SAP Help Portal</a> </div>

Applying Debugging Tools - SAP Customer Data Cloud

In this video, we will go over several  debugging tools you can use with  SAP Customer Data Cloud.  We'll cover the Fiddler Web Debugger,  the Charles Webb Debugger,  the server response log  and the Web SDK Debug UI.  First, let's look at the Fiddler Web Debugger.  The Fiddler Web Debugger is a  third-party application that proxies and  logs HTTP traffic between your  computer and the Internet.  This allows for inspecting both  incoming and outgoing HTTP traffic.  It allows for viewing the data in the  body of HTTP requests and the  response to and capturing requests  that don't appear as web documents,  like those made by the JavaScript SDK.   Now let's look at the Fiddler Web Debugger itself.  When you first open it on the left-hand side,  there’s a listing of captured HTTP traffic.  This listing shows the protocol,  host, and URL that make up the  HTTP request.  Double-click on any line in this list to  display the request and response  details for that line.  The response will appear on the  right-hand side of the application.   Next, let's look at the Charles Webb debugger.  The Charles Web debugger is  also a third-party application  that proxies and logs HTTP traffic  between your computer and the Internet.  In many ways, the Charles Webb Debugger  is the Mac equivalent of the Fiddler Web Debugger.  It allows for inspecting HTTP traffic,  both incoming and outgoing.  It also allows for viewing the data  in the body of the HTTP requests  and the response to and capturing  requests that don't appear as web documents like those made by the JavaScript SDK.   Now, let's look at the Charles web debugger.  When you first open it, the sequence of  HTTP traffic captured appears at  the top half of the program.  This listing shows the HTTP method,  the host, and the path of the HTTP request.  Double-click on any line of this list to  display the request and response  details for that line,  which will appear at the bottom of the application.   Now let's review the server response log.  If you're using one of the REST SDKs,  then you will be able to get additional  details about errors through the  SDKs server response log.  The log method on the response  object will return those details.  Let’s take a look at a few examples.  Here is a PHP SDK example.  This example shows if you were  deploying with the Java SDK.  And here we have the dotnet SDK, as well.  Finally, let's look at the Web SDK debugger UI.  During development, you may  want to know what calls and what  responses are taking place in the background.  The Debug UI allows you to see  what API calls and responses  are taking place under the hood when  you’re developing Customer Data Solutions  with the Web SDK.  Also, you may encounter an error  during the registration process and  want to know if Customer Data Cloud  provided an error code  or a more technical message.  So, you’ll also see the error codes and  technical messages you get  in the Customer Identity processes.  To view this within the browser,  SAP Customer Data Cloud has a widget available within the Web SDK.  To use the debug UI,  go to the browser’s console on a  Customer Identity enabled web page and execute the gigya.showDebugUI() function.  You’ll see a widget at the top of the  web page which will log all API calls  made to Customer Data Cloud  along with the responses.  Here is a quick demo of the debug UI widget.  Go to the browser’s console  and execute the  gigya.showDebugUI() Javascript function,  hit Enter.  A widget pops up at the top of the web page.  On the Debug UI widget,  you can see the API key of the site,  all the Web SDK method calls,  and the JavaScript events fired as part of  the Customer Identity process.  Thank you for watching.