Describes how you test your SAPUI5 application on an ABAP server.
To test a SAPUI5 application that you have uploaded to an ABAP system, you can directly launch its public URL in a browser window.
You have the following options to launch a synchronized file, for example the index.html, on the ABAP server:
The launch option is only available if the file is accessible via URL, for example, if it is in the WebContent folder.
The URL of the selected file is opened in a browser window. The URL has the following pattern:
<protocol>://<host name>:<port number>/sap/bc/ui5_ui5/<namespace>/<application name>/index.html?sap-client=<client>&sap-ui-language=<language>&sap-ui-appcache=false
You can also start the SAPUI5 application as follows:
Select the SAPUI5 application-specific Internet Communication Framework (ICF) node in transaction SICF under sap/bc/ui5_ui5/<namespace>/<application name>, and choose Test Service from the context menu. This starts your index.html page automatically.
By default, the application files are stored in the browser cache for one year to speed up the performance in a productive environment. To get the latest changes you need to force your SAPUI5 start page to refresh, for example with CTRL + F5 on Windows systems. If the refresh does not work, clear your browser cache.
The following is an experimental feature which might change in future versions of SAPUI5: If you are in development mode and like to immediately get the latest changes without refreshing your SAPUI5 start page, you can add the experimental URL parameter sap-ui-xx-devmode to the SAPUI5 start page in order to force the browser to check whether there is a newer version of the application files available. When switching between development and productive modes, refresh the SAPUI5 start page. If the refresh does not help, clear your browser cache.
If you activate the application cache buster in the start page of the application in which the SAPUI5 bootstrap is located by setting data-sap-ui-appCacheBuster="true", the SAPUI5 application runtime handler on ABAP side supports the application cache buster, see Application Cache Buster. In this case, the ICM server cache on ABAP side as well as the browser cache is used and the application cache buster mechanism ensures that all those resources which are supported by the application cache buster mechanism are up to date.
The internal cache buster information for a SAPUI5 application becomes outdated every two hours and is then calculated automatically. As a consequence, the underlying server side cookies 'cachebuster_info' get recalculated without the need of manual acitivity.