Using File Store Provider to Store Content files in database

Using File Store Provider to Store Content files in database

Here are the steps for doing this

1. Open Content Server providers page


2. From the providers page edit “DefaultFileStore” provider, by opening “Info” link


3. Enable file store provider by clicking on “Upgrade” button


4. Restart content server

5. Repeat Sep 1 and 2, and then click on “Edit” button

6. By default, there is a Storage Rule created for you, and we will edit this rule (if you want, you can add new rule). In “Edit File Store Provider” page, click on “Edit Rule”


7. “Storage Rule” page, choose “JDBC Storage” option, and in “Renditions” list, don’t choose anything (not choosing any rendition option means, we will store both the original file and weblayout file in the database). Don’t change Path information.


8. Open “File Store Administration” page


9. Click on “Add Partition” button


10. On “Add Partition” page, add “Partition Name” field that you want, and in “Duplication Methods” choose link which means that if the original file has not been converted, a link to the original file will be used (instead of making a copy of the file, which is duplicating the content)

Note, choosing link in “Duplication Method”, will save space in the database, because large part the content will not be converted


11. Restart content server
    
12. We want to test what we did, so we will check-in a new file into the content server.
13. Query the database table “FileStorage”, you will find primary file and weblayout files added into two records and that two records identified by dID

I still have questions about File Store providers, and I wish some can help me

• How many partitions should I create?
• What about the old content that is already stored in file system?