By Kevin Smith-Oracle on Jun 24, 2015
If you have configured WebCenter Content (WCC) to store your content in the database you are probably not expecting it to be storing any content on the file system. You may choose to go with a minimal file system to hold the vault and weblayout directories. You need to be aware that WCC will store content on the file system for two reasons:
- During the check in process WCC needs to store the native file in the vault directory so it is available for full-text indexing and for rendition processing. Any webviewable files are also stored on the file system after they are generated by the Inbound Refinery (IBR).
- Whenever a content item is retrieved, WCC will store the file on the file system after retrieving it from the database. The file system is used as a cache so that if the content item is retrieved again it can be retrieved from the file system instead of the database.
For #1 this can have an impact when you are either loading a large amount of content into WCC or rebuilding your full-text index. When doing a full-text index rebuild every file in WCC will be retrieved from the database and stored on the file system.
If you want the files on the file system removed after the content item has been indexed you can add this configuration setting:
If you want to keep the file system as small as possible you can also add these configuration settings to minimize the amount of files keep on the file system as a cache:
DatedCacheIntervalDays=1 FsCacheThreshold=0 FsMaximumFileCacheAge=0 FsMinimumFileCacheAge=0