2024 Update Rollup 1

Configuring CAS CachePermanent link for this heading

For performance reasons each Fabasoft Folio Kernel instance has a CAS cache by default. When requesting a content, the Fabasoft Folio Kernel first tries to read the content from the CAS cache. If the content identified by a hash can be found in the CAS cache the content can be used directly from the cache and the Fabasoft Folio MMC Service is not required for reading.

The path of the CAS cache directory can be configured via the environment option CASCACHEDIR (e.g. HKEY_CURRENT_USER\Software\Fabasoft\Environment\CASCACHEDIR in a Microsoft Windows environment).

By default, all CAS areas of all Fabasoft Folio MMC Services are treated as a separate data pool in the cache. In case that several Fabasoft Folio MMC Services are using the same data pool the configuration can be adopted to combine the areas also within the cache. Therefore configure the property Shared Cache Name (CAS) (COOSYSTEM@1.1:dareasharedname) in the MMC Service Areas aggregate of the Fabasoft Folio MMC Services. Areas with the same shared cache name are treated as one CAS data pool.

In order to prevent an unlimited growth of the CAS cache the Fabasoft Folio Kernel calls periodically a cleanup routine for the CAS cache. Information about the cleanup can be found in the event log. The maximum size and the time interval of the recurring cleanup process can be configured via the environment options CASCACHEMAXMB and CASCACHECLEANUPINTERVAL, respectively. It is also possible to call the cleanup mechanism directly via the action COOSYSTEM@1.1:CleanupCASCache. When doing so the environment option CASCACHECLEANUPINTERVAL is ignored.

The CAS cache can be disabled via the environment option ENABLECASCACHEDIR.