SAP Fiori - Cache Management

[masa_139]

This is a collaborative document to share lessons learned contents for SAP Fiori Cache Management topics in the community SAP Fiori.

Please feel free to insert the link of your document or blog by selecting the edit button from Actions.

1. Manual Cache clearing is not required.

If you do discover a bug kindly create an incident.  SAP Support Team will investigate your issue. It might be that SAP has to provide a note containing the fix, the important thing though is that SAP can reproduce your issue so that SAP can localize the error. To this end please do not invalidate the UI2 Caches! By this collaboration SAP is certain of eliminating all cache errors and reducing customer TCO further. Thank you very much.

2362875 - UI2 Caches and their synchronization with the database

2. Understanding the cache management

Caches are located in each layer (Client, Frontend Server and Backend Server)

3. Client

• Browser - No action is required. Please setup the Cache Buster.
  • If clearing caches is required, you can manually clear the browser cache.
• Fiori Client - No action is required.
  • When an app is updated on the server, Fiori Client automatically purges the existing cache and pulls the update from the server.
    
  • If clearing caches is required, you can manually clear the cache in the Setting -> Clear Cache. http://help.sap.com/fiori-client

4. Frontend Server

• Cache Buster
  • Cache Buster for SAP Fiori - SAP Fiori Launchpad - SAP Library
• ICM
  • Transaction: SMICM  Menu, Goto -> HTTP Plug-in -> Server Cache -> Invalidate Globally
  • ICM Server Cache - Internet Communication Manager (ICM) - SAP NetWeaver - SAP Library
• UI2
  • Please refer to SAP note 2362875 - UI2 Caches and their synchronisation with the database
    
• Metadata
  • Transaction: /IWFND/CACHE_CLEANUP. This clears the OData metadata cache.

5. Backend Server

• Matadata
  • Transaction: /IWBEP/CACHE_CLEANUP. This clears the OData metadata cache.