Fiori缓存

缓存是为了提高运行速度用的,SAP也准备了丰富了缓存机制,正常情况下我们是不需要做任何缓存的手工清除工作,但遇到一些奇怪的问题时,不妨尝试一下,问题说不定就会自己消失。

整体来说SAP有下面几种Cache:
Fiori缓存

  1. 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
  2. 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.命名空间/UI2/的所有服务都是相关,如/UI2/PAGE_BUILDER、/UI2/INTEROP和/UI2/START_UP,它实际指的是数据库表/UI2/CACHE,该表存储了服务请求的响应,用于后续的快速检索。
    Metadata
    Transaction: /IWFND/CACHE_CLEANUP. This clears the OData metadata cache.
  3. Backend Server
    Matadata
    Transaction: /IWBEP/CACHE_CLEANUP. This clears the OData metadata cache.

使用Cache Buster,会在fiori应用被调用时在FES和浏览器缓存中生成token。如果再次调用同一个fiori应用,FLP首先会检查FES中的token与浏览器缓存中的token是否一致。当FES发生了更新的情况下,FES会产生新的token,导致FES的token与浏览器缓存中的token不一致,因此FLP会从FES重新获取内容;如果FES没有更新,FES的token与浏览器缓存中的token一致,FLP会从浏览器缓存中获取相应的resource。

在使用Task list初始化launchpad过程中的这一步就是这个目的:
Fiori缓存

参考:https://blogs.sap.com/2015/06/16/sap-fiori-cache-management/