Wednesday, June 18, 2008

The FileStoreProvider and making your job a little bit easier.

If anyone has ever run out of disk space on their Content Server v7.5.x or earlier, they know how difficult it can be to add more storage to the Content Server. Usually the process involved bringing down the Content Server, installing and setting up a new disk, migrating data over to the new disk, removing the old disk, and setting up the new disk with the old drives information (Driver letter or mount point).

With Content Server 10g, a new layer to the file system was added called the FileStoreProvider. What this component enables is a whole new world of storage capabilities for the Content Server. Some of these capabilities include:

  • The ability to relocate files easily.
  • The ability to partition files across multiple storage devices.
  • The ability to have the web-viewable file be optional.
  • The ability to manage and control directory saturation.
  • The ability to integrate with third-party storage devices
  • An API to use, extend, and enhance different storage paradigms.
Please note that once the FileStoreProvider has been enabled for a Content Server, this component should never under any circumstance be disabled as it sort of acts as the File Allocation Table for all your pieces of content.

For further information about Oracle's FileStoreProvider please see the File Store Provider Installation and Administration Guide in the UCM 10g Documentation Package.

No comments:

Official, Youbetcha Legalese

This blog is provided for information purposes only and the contents hereof are subject to change without notice. This blog contains links to articles, sites, blogs, that are created by entities other than Oracle. These links may contain advice, information, and opinion that is incorrect or untested. This blog, links, and other materials contained or referenced in this blog are not warranted to be error-free, nor are they subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this blog, links and other materials contained or referenced in this blog, and no contractual obligations are formed either directly or indirectly by this blog, link or other materials. This blog may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. The opinions and recommendations contained in this blog(including links) do not represent the position of Oracle Corporation.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.