eXo Platform 4.0 Documentation > Administrator Guide > Configuration > Cache configuration

2.13.3. ECMS caches

eXo Platform provides a list of ECMS caches, including:

These ECMS caches are handled by various cache services and plugins in the configuration.properties file.


# == WCM Caches Configuration == #

# WCM Cache Configuration - Query Service
#  - Standalone (live time in seconds)
#  - Cluster (expiration in milliseconds)
wcm.cache.queryservice.maxnodes=5000
wcm.cache.queryservice.expirationtimeout=600000

# WCM Cache Configuration - Manage Drive
#  - Standalone (live time in seconds)
#  - Cluster (expiration in milliseconds)
wcm.cache.managedrive.maxnodes=5000
wcm.cache.managedrive.expirationtimeout=600000

# WCM Cache Configuration - Script Service
#  - Standalone (live time in seconds)
wcm.cache.scriptservice.capacity=300
wcm.cache.scriptservice.timetolive=86400

# WCM Cache Configuration - Templates Service
#  - Standalone (time to live in seconds)
wcm.cache.templateservice.capacity=3000
wcm.cache.templateservice.timetolive=86400

# WCM Cache Configuration - Initial Webcontent
#  - Standalone (time to live in seconds)
wcm.cache.webcontent.initialwebcontentplugin.capacity=300
wcm.cache.webcontent.initialwebcontentplugin.timetolive=86400

# WCM Cache Configuration - Fragment Cache Service (Markup Cache)
#  - Standalone (time to live in seconds)
wcm.cache.fragmentcacheservice.capacity=10000
wcm.cache.fragmentcacheservice.timetolive=30

# WCM Cache Configuration - PDF Viewer Service
#  - Standalone (time to live in seconds)
wcm.cache.pdfviewer.capacity=1000
wcm.cache.pdfviewer.timetolive=3600

# WCM Cache Configuration - SEO Cache
#  - Standalone (time to live in seconds)
wcm.cache.seoservice.capacity=1000
wcm.cache.seoservice.timetolive=3600

# WCM Cache Configuration - Javascript Cache
#  - Standalone (time to live in seconds)
cache.exo.ecms.javascript.maxSize=1000
cache.exo.ecms.javascript.liveTime=3600

The specific configuration of ECMS caches can be found in two files:

i. For WCMDriveCache, ScriptCache, FragmentCache, TemplateCache, InitialWebContentCache and PDFCache:

ii. For SEOCache:

WCMDriveCache

The WCMDriveCache caches visited drives of Sites Explorer by their names. When any users visit the cached drives, these drives will be directly retrieved from cache rather than the database.

ScriptCache

The ScriptCache caches the script objects. When there are any requests for cached scripts, these scripts are taken from cache rather than the database.

FragmentCache

The FragmentCache caches content of SCVs and CLVs. When any users call for these cached portlets, these portlets will be retrieved from cache rather than the database.

TemplateCache

The TemplateCache caches the list of document nodetypes. When any users call for the cached document nodetypes, data will be retrieved from cache rather than the database.

InitialWebContentCache

The InitialWebContentCache caches the artifact (node) that is necessary to deploy to a new portal. When the cached artifact is called, it will be read and returned from cache rather than the database.

PDFCache

The PDFCache caches the path to a specific page in a specific PDF file. In eXo Platform, when a user views an Office document or PDF file, the viewed page is extracted into a PDF file, and REST is used to return that file content to client browser. When the cached page is called, its data will be taken from cache (based on the page path) rather than the database.

SEOCache

The SEOCache caches the SEO metadata of all pages in all sites. When the SEO metadata of these cached pages are called, the created pages will be got based on the page path from cache rather than the database.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus