Skip to Content

Debug Your SAPUI5 App with SAP Web IDE

0 %
Debug Your SAPUI5 App with SAP Web IDE

Debug Your SAPUI5 App with SAP Web IDE

Learn how to debug and test your web apps with the Google Chrome DevTools.

You will learn

  • How to do add breakpoints to your JavaScript code
  • How to log data to the console
  • How to use the Google Chrome DevTools

Step 1: Add a message page

Add a simple message page to let the users know you are still working on this app.

Replace the existing page in the file tutorial/ui/webapp/view/View1.view.xml with

<MessagePage showHeader="false"
  description="More content to come"
  text="Stay tuned!"
  icon="sap-icon://home" />
Log on to answer question
Step 2: Change the log level

Add the following line to the index.html file to change to log level.


The log level acts like a filter and hides all log messages below the defined severity.

Log on to answer question
Step 3: Write a log message to the console

Import the logger to the file tutorial/ui/webapp/controller/View1.controller.xml and add this onBeforeRendering as well. This Log object allows you to write messages to the console.

Replace line #2 and #3 with this snippet:

], function (Controller, Log) {

onBeforeRendering: function() {"A random log message");

The controller code should look like this now:

This onBeforeRendering method is called every time the View is rendered, before the Renderer is called and the HTML is placed in the DOM-Tree. It can be used to perform clean-up-tasks before re-rendering.

Log on to answer question
Step 4: Add a breakpoint

Add this onAfterRendering hook to the same file to place a breakpoint in your code. A breakpoint will cause your app to stop when the execution thread reaches it. This gives you the chance to inspect the state of you app.

onAfterRendering: function() {

This onAfterRendering method is called every time the View is rendered, after the HTML is placed in the DOM-Tree. It can be used to apply additional changes to the DOM after the Renderer has finished.

Log on to answer question
Step 5: Run the latest version

Running your application has several advantages over deploying it. Among others, it’s faster, doesn’t require a “build” step and won’t minify your JavaScript code base

  1. To run the UI module, right-click on the module and select Run and Run Configurations.

  2. In the dialog, select + and Run as Web Application to add a new run configuration for you app.

  3. Specify the path to your main file with ui/webapp/index.html and select Run on Cloud Foundry to choose the target environment. Confirm your input with Save and Run .

Log on to answer question
Step 6: Keep track of the progress in the console

You can see status messages during the start up of the module in the console of the Web IDE.


The initial start up might take a few minutes, but only for the very first time.
After that, your changes can be run almost instantly when you click the green run button next time.

You might be prompted for you SAP Cloud Platform credentials when you try to access the running app. Use the same credentials as for the SAP Cloud Platform cockpit here.


In case you run into the following service broker error:

Could not create the '<appname>' instance of the 'destination' service type for the 'dest_mta_sapui5training' resource.
CF-ServiceBrokerBadResponse(10001): Service broker error: Quota limit exceeded. Instance creation not allowed

Please refer to this community question and remove the existing service instances.

Log on to answer question
Step 7: Stop at the breakpoint

Open the Chrome DevTools (or the dev tools of your favorite browser) by clicking F12. Refresh the page to run the script one more time.

You should now see that the app reached the breakpoint (the dev tools automatically switched to the Sources tab).

Log on to answer question
Step 8: Check the log message

Click F8 to jump over the breakpoint and switch to the Console tab.
Now you should see your error message printed in red. Click on the small triangle on the left side to expand the error message.

Can you spot the line in which you invoked the error message?

Which libraries are loaded before sap.ui.layout? Hint: Scroll up in the console to find the answer.

Next Steps

Back to top