DefaultFileStore Settings Empty Storage Rule

4-38 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

4.3.2.1 DefaultFileStore Settings

An Oracle Content Server system containing no documents and with the FileStoreProvider component automatically upgraded uses these DefaultFileStore settings. ■ Vault Path: env.VaultDirdDocTypedDocAccountdispersiondIDExtensionSeparator dExtension ■ Dispersion Rule: dRevClassID[-9:-6:0:b]dRevClassID[-6:-3:0:b] ■ Web-viewable Path: env.WeblayoutDirgroupsdSecurityGroupdDocAccountdocumentsdDocType dispersionedispdDocNameRenditionSpecifierRevisionLabel ExtensionSeparatordWebExtension ■ Web URL File Path: HttpWebRootgroupsdSecurityGroupdDocAccountdocumentsdDocType dispersionedispdDocNameRenditionSpecifierRevisionLabel ExtensionSeparatordWebExtension The dispersion field is added in Path information for the storage rule and can be edited. The Web-viewable Path and Web URL File Path fields cannot be edited. The dispersion rule is added in web paths at the dispersion location. The dispersion rule allows you to specify :b for base 64 encoding of that part of the URL. For example, the following dispersion rule encodes the two parts to be base 64: dRevClassID[-9:-6:0:b]dRevClassID[-6:-3:0:b] An Oracle Content Server system containing documents and which does not have the FileStoreProvider component upgrade will return an informational message that the Revisions table is not empty, therefore dispersion for the default storage rule is not set for DefaultFileStore.

4.3.2.2 Empty Storage Rule

If a site has used an earlier version of the Oracle Content Server system without using the file store system, then upgraded and implemented the FileStoreProvider component, or a site has uninstalled the FileStoreProvider component completely and also removed the metadata fields added by FileStoreProvider, then when a user checks in a document it will not have an associated storage rule no xStorageRule field. When FileStoreProvider is implemented after these types of situations, users will find that documents checked in before FileStoreProvider was implemented will have an empty xStorageRule field. To fix this situation, users must perform an Update to the Content Information for those documents. The documents will be updated to the default value of the xStorageRule field and will be moved to the location specified by the storage rule. For details on xStorageRule, see Section 4.3.3.1.2, Oracle Content Server Metadata Fields.

4.3.3 Configuring FileStoreProvider