Skip to Content
Technical Articles

SAP Fiori – Performance

SAP Fiori and the Fiori Launchpad have thousands of role-based apps for different SAP solutions, such as SAP S/4 HANA, SAP Simple Finance, and the SAP Business Suites.  The goal is to apply the SAP Fiori UX to provide a personalized, responsive, and simple user experience.

With the goal highlighted above, there are known performance tweaks that one can do to help improve the runtime or display of a Fiori app in the Fiori Launchpad (FLP).

Fiori performance is an important topic in every implementation.  A few simple tricks and tips help you to improve SAP Fiori’s performance.

 

Cache Buster for SAP Fiori

2362875 – UI2 Caches and their synchronization with the database

Clears the OData metadata cache.

Transaction: /IWFND/CACHE_CLEANUP. This clears the OData metadata cache.

Activate the Cache Buster

►On the front-end server, start transaction SICF.

►Activate the following SICF service:/sap/bc/ui2/flp

 

Invalidate Client Caches

You can use a program on the front-end server to invalidate resources of SAP Fiori apps in client caches. This is only required if resources that are not included in the application index are updated as part of a patch.

►Start transaction SE38.

►Execute report /UI2/INVALIDATE_CLIENT_CACHES.

►Select the users for whom you want to invalidate the cache:

 

Apply the latest Support Package

Performance improvements have been included in the latest support packages for each app. Double-check that you have applied the latest support packages.

 

HTTP/2 feature can improve your Fiori/SAPUI5 solution performance

The above diagram explains that under HTTP/2, the browser can send multiple resource requests in parallel inside one TCP connection. This improvement brings less waiting time, quicker response and users get a better user experience from your solution.

HTTP vs HTTP/2

►HTTP is the communication protocol between the browser and the webserver. The browser sends one resource request to a web server and then the webserver returns the requested resource to a browser. So, in general, one request for one resource, static content (image, JavaScript, CSS, and audio/video…etc.) gets to cache in user’s computer disc to shorten waiting time when opening a web page, because one round-trip can only request a file.

►HTTP/2 (AKA h2 or HTTP 2.0) is the second major version of HTTP communication protocol. The protocol got approved in 2015 by IETF (Internet Engineering Task Force), and is widely adopted by all major websites and browsers (IE, Firefox, Chrome, Safari,…). You can check RFC 7540 for more detailed information. The new version brings many improvements compared to its previous version, and one new feature call ‘Multiplexing’ helps browser sending multiple resource requests in parallel inside a single HTTP/2 connection

How to enable HTTP/2 in NetWeaver Gateway and Web Dispatcher?

NetWeaver Gateway version 7.51, Web Dispatcher 7.49 both support HTTP/2

add profile parameter icm/HTTP/support_http2=true to the system profile.

There is a prerequisite for running communication under HTTP/2, it must be HTTPS with at least TLS 1.2 encryption. Although IETF RFC 7540, it doesn’t mention that HTTP/2 has to run under HTTPS but the reality is that all browser vendors make it only work when communication is in encryption mode. Apart from the above, if you want to use TLS 1.1 or higher, COMMONCRYPTOLIB version 8.4.31 or higher is required.

 

Fiori Performance:

Understanding the overall architecture of the solution is key to identify performance issues because, in the Fiori architecture, your browser is directly accessing the back-end via each Fiori tile. Each tile on the Fiori Launchpad (FLP) is making numerous calls to (and receiving) data from the server, which can cause latency issues.

Note that when referring to the backend in the S/4HANA model we are talking about the integration between 3 main components:

  • Web Dispatcher
  • Front End Server
  • Backend Server

Depending on the network configurations of these servers, network performance issues may arise.

 

General Rule of Thumb on Performance:

  • The more tiles you have on your FLP, the longer it will take to load
  • To lessen any latency issues, only add the tiles you need
  • It is recommended that you do not exceed 7X7 (49 tiles) per FLP group, also notice the more catalogs you have assigned, the longer it is going to take to load the home screen
  • Go through the Design Thinking workshop at the early stages of the project in order to build “Personas” which will later help you define the required business roles
/
1 Comment
You must be Logged on to comment or reply to a post.