Pular para o conteúdo principal

Webcenter Content - Cache Configuration for JdbcFileStore configuration

The configuration values below, control the temporarily cached files keep in FileCache table.


FsCacheThreshold
  • Specifies the maximum cache size, in megabytes (default=100)
  • Once the threshold is met, Content Server starts deleting files that are older than the minimum age, as specified by the FsMinimumFileCacheAge parameter


FsMaximumFileCacheAge
  • The age at which files are deleted, expressed in days. The default is 365 days


FsMinimumFileCacheAge
  • The minimum age at which cached files can be deleted
  • This parameter is used in conjunction with the FsCacheThreshold parameter to determine when to delete cached files


FsCleanUpCacheDuringIndexing
  • This parameter activates vault cache cleaning, while FsCacheThreshold, FsMaximumFileCacheAge and FsMinimumFileCacheAge are controling its behaviour. 
  • Expect, when this is enabled on a system that currently has a large number of files in the FileCache table, the first cycle will take a long time to complete.

How to Configure:

In Administration Console:

Select Administration --> Admin Server --> General Configuration

In the "Additional Configuration Variables" pane add the following to the config.cfg:


I'm using values:

FsCleanUpCacheDuringIndexing=true
FsCacheThreshold=50
FsMinimumFileCacheAge=3
FsMaximumFileCacheAge=6


Reference: Managing a File Store System

Marcadores:

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Assign Backup Policy for Boot and Block Volumes - OCI

To get Availability Domain oci iam availability-domain list  #!/bin/bash OCI_AD="hQsi:SA-SAOPAULO-1-AD-1" OCI_COMPARTMENT="ocid1.compartment.oc1..aaaaaaaavgyjpoffz5qliieawamjaksfb6juxejurtduclqjkvv66ookcxja" #Get Silver policy ocid funct_get_policy(){ OCI_POL_OCID=$(oci bv volume-backup-policy list | jq -r '.data[] | select(."display-name"|contains("silver"))' | jq -r '.id') } funct_boot_vol (){ #Create a file with all boot volume ocid oci bv boot-volume list --availability-domain ${OCI_AD} -c  ${OCI_COMPARTMENT} | jq -r '.data[].id' > boot-vol.txt while IFS="" read -r p || [ -n "$p" ] do   printf 'Seeting backup policy for %s\n' "$p"   oci bv volume-backup-policy-assignment create  --asset-id  $p  --policy-id ${OCI_POL_OCID} done < boot-vol.txt } funct_block_vol (){ #Create a file with all block volume ocid oci bv volume list  -c ${OCI_COMPARTMENT} | jq -r '.data[].id' ...
Postar um comentário
Leia mais

Oracle Data Modeler and SQL Developer: change user interface (GUI) language

Oracle Data Modeler and Oracle SQL Developer does not allow to change the user interface language in “Options” or somewhere else in the GUI. This applies to the versions: Oracle SQL Developer Data Modeler - Version All and later (18.2.0 in my case) Oracle SQL Developer - Version 3.2 and later However, it’s possible switch to other language, changing datamodeler\ide\bin\ide.conf configuration file. The following lines should be added to the file for support English: AddVMOption -Duser.language=en AddVMOption -Duser.country=US Restart application! SQL Developer and Data Modeler supports the following languages: French(fr), German(de), Italian(it), Spanish(es), Brazilian Portuguese(pt BR), Japanese(ja), Korean(ko), Simplified Chinese(zh CN), Traditional Chinese(zh TW).
Postar um comentário
Leia mais