Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
72:cms_prefetch [2018/10/08 13:24] – etea72:cms_prefetch [2020/08/25 07:29] – tssr
Line 8: Line 8:
 === Configuration of the CMS Prefetch === === Configuration of the CMS Prefetch ===
  
-The default configuration of the CMS prefetch is found in <font inherit/Courier New,Courier,monospace;;inherit;;inherit>''<Stages installation path>/stages /conf/config.xml''</font> file:+The default configuration of the CMS prefetch is found in <font inherit/Courier New,Courier,monospace;;inherit;;inherit>''<Stages installation path>/stages/conf/config.xml''</font> file:<code>
  
-<code> 
 <stages-config> <stages-config>
  <properties>  <properties>
Line 23: Line 22:
  <cms> ... </cms>  <cms> ... </cms>
 </stages-config> </stages-config>
 +
 </code> </code>
  
Line 36: Line 36:
 <code> <code>
 class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy
 +
 </code> </code>
  
Line 43: Line 44:
 <code> <code>
 class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy
 +
 </code> </code>
  
Line 64: Line 66:
  <cms> ... </cms>  <cms> ... </cms>
 </stages-config> </stages-config>
 +
 </code> </code>
  
Line 70: Line 73:
 Stages caches two different levels of information regarding files in external configuration management systems. It collects infomation about the folder structure of a CMS and the files contained within these folders. This information is then used for displaying document information such as the version or state of a file. Stages caches two different levels of information regarding files in external configuration management systems. It collects infomation about the folder structure of a CMS and the files contained within these folders. This information is then used for displaying document information such as the version or state of a file.
  
-These caches are - by default - persisted in the file system on the application server that runs Stages. However the administrator may configure these caches to be stored within a relational Database. This increases cache performance significantly.+These caches are persisted in the file system on the application server that runs Stages.
  
-The configuration of this is done in the Stages configuration file ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/conf/PKitCaching-customer.xml</font>''+To optimize the usage of memory on the application server, the administrator can configure the cache size.
  
-Each cache requires its own configuration and its own database. An example configuration for both MySQL and Oracle database servers can be found within the file.+**In Version VERSION and above**:
  
-//Note//: After changing the cache persistence settings, the Stages configuration has to be updated (''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><Stages installation path>/stages/bin/update.bat</font>'') and Stages has to be restarted.+The property "cms.prefetch.memorycache.max.documents" and "cms.structure-prefetch.memorycache.max.repositories" can be used to set the maximum amount of objects, which should be cached in memory for the documents-cache and the repository-cache.
  
 +**Since Version**:
  
 +For a more accurate adjustment, the cache size can now be configured in MB. The corresponding properties are
 +"cms.structure-prefetch.memory.cache.repositories.maxSizeInMB" and "cms.prefetch.memory.cache.documents.maxSizeInMB"