Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
72:cms_prefetch [2018/07/17 13:19] – created bkkr | 72:cms_prefetch [2020/08/25 13:16] – tssr | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Configure the Stages Server | + | [[: |
- | ====== CMS Prefetch Configuration | + | ====== CMS Prefetch Configuration ====== |
The CMS prefetch is a Stages system service. It ensures that Stages displays up to date information of documents that are managed by an external configuration management system (CMS). Therefore the CMS prefetch is scheduled periodically to retrieve the latest revision information for all documents of active projects. | The CMS prefetch is a Stages system service. It ensures that Stages displays up to date information of documents that are managed by an external configuration management system (CMS). Therefore the CMS prefetch is scheduled periodically to retrieve the latest revision information for all documents of active projects. | ||
Line 8: | Line 8: | ||
=== Configuration of the CMS Prefetch === | === Configuration of the CMS Prefetch === | ||
- | The default configuration of the CMS prefetch is found in '' | + | The default configuration of the CMS prefetch is found in <font inherit/ |
- | <code> | + | <stages-config> |
- | <pkit-config> | + | |
< | < | ||
Line 22: | Line 21: | ||
</ | </ | ||
< | < | ||
- | </pkit-config> | + | </stages-config> |
</ | </ | ||
A more detailed description of these properties can be found in the following table: | A more detailed description of these properties can be found in the following table: | ||
- | ^Property ^Description| | + | TBD |
- | |cms.prefetch.activated| \\ In case no configuration management system is configured the prefetch service can be completely deactivated. | + | |
- | \\ Default | + | === Strategies === |
- | | | + | |
- | |cms.cache.refreshIntervalInMinutes| \\ A new prefetch run will be started after this period of time. (In case of a too short interval it will be delayed until the previous run has finished) \\ | + | |
- | \\ Default = 60 \\ | + | The following |
- | | | + | |
- | |cms.cache. lastAccessIntervalForActiveProjectsInDays| \\ The prefetch | + | |
- | \\ Default = 4 \\ | + | //Classic all documents available// |
- | | | + | < |
- | |cms.prefetch.sleepMillisBetweenDocuments| \\ In case the prefetch service produces too much CPU load on the Stages server or on the CMS, it can be forced to pause for some time. This will of course lead to longer running prefetches. \\ | + | class=de.methodpark.pkit.cms.prefetch.ClassicAllDocumentsStrategy |
- | \\ Default = 0 \\ | + | </ |
- | | | + | |
- | |cms.prefetch.workersCount| \\ In case the prefetch does not finish its work within the specified referesh interval, the amount of worker threads utilized by the prefetch can be increased. This will lead to additional CPU load and load on the CMS. \\ | + | |
- | \\ Default = 1 \\ | + | This strategy ignores the maxParallelTasks properties. (cms.prefetch.maxParallelTasks.< |
- | | | + | |
- | |cms.prefetch.strategy.class| \\ Specifies | + | |
- | \\ Default: | + | //Prefetch by CMS type strategy// |
- | | | + | < |
- | |cms.prefetch.maxParallelTasks.< | + | class=de.methodpark.pkit.cms.prefetch.PrefetchByCMSTypeStrategy |
+ | |||
+ | </ | ||
+ | |||
+ | This strategy allows more detailed configuration on the distribution of prefetches dependent on the type of CMS the document is hosted. | ||
+ | |||
+ | cms.prefetch.maxParallelTasks. | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | | ||
+ | < | ||
+ | < | ||
+ | | ||
+ | |||
+ | < | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | </ | ||
+ | |||
+ | </ | ||
- | \\ Default | + | === Cache Persistence === |
- | | | + | |
- | |cms.prefetch.initialStart.hourOfDay| \\ In case this property exists in PKitConfig.xml, | + | |
- | \\ Default: <not set; start immediately> | + | 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 persisted in the file system on the application server that runs Stages. |
- | | | + | |
- | \\ | + | The cache size has a fixed size but will be configurable from Version 7.4.6.1, 7.5.2.1 and above. |