Show TOC

Step 2: BootstrapLocate this document in the navigation structure

Before we can do something with SAPUI5, we need to load and initialize it. This process of loading and initializing SAPUI5 is called bootstrapping. Once this bootstrapping is finished, we simply display an alert.

Figure 1: An alert "UI5 is ready" is displayed

You can view and download all files in the Explored app in the Demo Kit under Walkthrough - Step 2.


SAPUI5 is a JavaScript library that can either be loaded from the same Web server where the app resides, or from a different server. The code examples in this tutorial always show relative paths and assume that SAPUI5 is deployed locally in the resources folder of your Web server's root context.

If SAPUI5 is deployed somewhere else on the server or you want to use a different server, then you need to adjust the corresponding paths in the bootstrap (here: src="/resources/sap-ui-core.js") in this tutorial according to your own requirements. SAPUI5 can also be retrieved from the Content Delivery Network (CDN) at .

You can use this reference to the latest stable version of SAPUI5 for the tutorial or for testing purposes, but never use this for productive use. In an actual app, you always have to specify an SAPUI5 version explicitly.

For more information about the CDN, see Variant for Bootstrapping from Content Delivery Network.

In case you are using SAP Web IDE, you can right-click the project and select Start of the navigation path New Next navigation step Cloud Connectivity Configuration End of the navigation path to make the /resources… reference work. This creates the neo-app.json file, which configures a URL mapping for this path.

<!DOCTYPE html>
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta charset="utf-8">
         data-sap-ui-preload="async" >
         sap.ui.getCore().attachInit(function () {
             alert("UI5 is ready");
      <p>Hello World</p>
In this step, we load the SAPUI5 framework from our local webserver and initialize the core modules with the following configuration options:
  • The src attribute of the first <script> tag tells the browser where to find the SAPUI5 core library – it initializes the SAPUI5 runtime and loads additional resources, such as the libraries specified in the data-sap-ui-libs attribute.

  • The SAPUI5 controls support different themes, we choose sap_bluecrystal as our default theme.

  • We specify the required UI library sap.m containing the UI controls we need for this tutorial.

  • To make use of the most recent functionality of SAPUI5 we define the compatibility version as edge.

  • We configure the process of “bootstrapping” to run asynchronously.

    This means that the SAPUI5 resources can be loaded simultaneously in the background for performance reasons.

When all resources and libraries are loaded, the SAPUI5 runtime fires the global init event to signal that the library is ready. It is a good practice to listen for this event in order to trigger your application logic only after the event has been fired.

In the example above, we get a reference to the SAPUI5 core by calling sap.ui.getCore() and register an anonymous callback function for the init event by calling attachInit(…) on the core. In SAPUI5 these kinds of callback functions are often referred to as handlers, listener functions, or simply listeners. The core is a Singleton and can be accessed from anywhere in the code.

Our anonymous callback function is executed when the bootstrap of SAPUI5 is finished and displays a native JavaScript alert.

The sap-ui-core.js file contains a copy of jQuery, this means that you can use all jQuery features.