Wednesday Jun 24, 2015

Keeping Your WebCenter Content File System Clean

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:

  1. 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).
  2. 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:


Wednesday Sep 19, 2012

When is the default storage rule not really the default storage rule?

In 11g WebCenter Content (WCC) introduced dispersion rules in the vault and weblayout directory paths to better distribute content across the directories. The dispersion rule was based on dRevClassID. The only problem with this is that dRevClassID did not remain the same when you copied content from one WCC instance to another using Archiver like in a contribution-consumption scenario. This could cause problems because the web-viewable path would not be the same between the contribution and consumption instances.

In the PS5 ( release of WCC they addressed this by configuring the File Store Provider (FSP) so that all new content would use a storage rule with a dispersion rule based on dDocName, which would stay the same when content was copied to another WCC instance. To support migration from older versions of WCC they left the default storage rule unchanged and created a new storage rule called DispByContentId and made that the default storage rule for all new content.

I only stumbled upon this a while back when I was trying to change the FSP configuration so that all content used a webless storage rule. I changed the default storage rule, restarted WCC, and checked in a new content item. To my surprise the new content was not created as webless. I struggled with this for a while until I noticed there were multiple storage rules defined in the FSP configuration. When I looked at the default value for the xStorageRule field in Configuration Manager, sure enough it was no longer default, but was now DispByContentId.

Once I updated the DispByContentId storage rule to webless and restarted WCC all my new content was now created using the webless storage rule, just like I wanted.

I noticed when I was creating this blog post that the default storage rule is also listed on the File Store Provider Information page, but I guess I didn't see that when I originally did this.

Friday May 20, 2011

More on File Store Provider

In PS4 ( you can now fully edit the FSP storage rule using the web interface instead of having to edit the hda files. I think this was actually added in a patch for PS3 ( This makes it easier to manage FSP storage rules.

When I was researching the FSP behavior I found this in the Admin User's Guide.

4.3.2 FileStoreProvider Upgrade

The FileStoreProvider component is installed, enabled, and upgraded by default for a new Oracle Content Server instance (with no documents in it). The upgrade includes creation of metadata fields with default values for the file store system (DefaultFileStore). Earlier versions of the Oracle Content Server software did not automatically upgrade the file store system, and sites could choose to not use the file store system, to not upgrade to use FileStoreProvider, and to uninstall the FileStoreProvider component and metadata fields. If you do not want to upgrade FileStoreProvider from your current settings, prior to installation you must enter the configuration variable FsAutoConfigure=false in the Additional Configuration Variables field on the General Configuration page of the Oracle Content Server Admin Server page.

I'm not exactly sure how you get to the Admin Server before you actually do the install. That would be quite a trick if you could do it. What I think they mean is that you need to add it to the config.cfg file that exists before you start the install, or actually before you create the WebLogic domain or add UCM to an existing domain. I have not tried this myself, but I would suspect that you would add it to the following file:


The other place you might want to try adding it is to the config.cfg that is created in the ucm/cs/config directory AFTER you add UCM to a WebLogic domain, but BEFORE you start it for the first time. I suspect that the FSP upgrade is done as part of the initial start up of UCM.

You would do this if you were installing a new 11g UCM instance and wanted it to work that same way as a 10g instance that was not using  the FSP.

Wednesday Feb 09, 2011

Changes to File Store Provider in UCM PS3

In the recent PS3 release of UCM ( there are some significant changes to the File Store Provider (FSP) configuration. For new PS3 installs (not upgrades from PS2) the FSP default storage rule includes a dispersion rule that will change the web-layout and vault paths by adding dispersion directories to the paths to limit the number of files in the vault and web-layout directories. What that means is that if you install a new PS3 UCM instance and migrate content in from a previous version of UCM the web URL will change. That is a critical problem for web sites and just general document management. Read the rest of this post where I describe the issue in detaill and provide instructions for how to modify a PS3 instance to use the old format for the web-layout path.[Read More]

Kevin Smith is a Technical Director in Oracle Consulting's WebCenter practice. He has been working with content management products since 2004 when he joined Stellent.


« July 2016