How to enable Data Aging in Content Services?

To enable data aging, navigate to the Content Services Domain Properties window. Set the

two properties

IFS.DOMAIN.BFILE.Enabled &

IFS.DOMAIN.BFILE.AgingEnabled to true. 

For the change to take effect, the domain must be restarted.

There are two settings for BFILE storage management:

1. The base path for the BFILE storage must be set. This is the directory off which the folders containing the BFILEs will be created. It can be an absolute path, or by prefixing it with ./ it will be a path relative to the database’s Oracle home directory.The default is named after the Content Services datastore schema name, ./ifsbfiles/CONTENT.
2. The BFILE policy determines whether to remove the file physically from disk if the document is deleted from within Content Services (this is the default) or whether it should remain available as operating system files after deletion.

Then configure the Content Agent. This is the process that will manage the migration of data between BLOBs and BFILEs, transparently as necessary.

• IFS.SERVER.AGENT.CONTENTAGENT.ContentToBfileManager: The Java class that implements data aging and should not be modified
  
• IFS.SERVER.AGENT.CONTENTAGENT.MaxFilesPerFolder: The maximum number of files to be written for every path created for BFILE storage. This should be adjusted according to optimal values for the file system and hardware of the node running the database.
  
• IFS.SERVER.AGENT.CONTENTAGENT.MaxFoldersPerActivationPeriod: The maximum number of folders (or directory paths) that may be created by each run of the agent
  
• IFS.SERVER.AGENT.CONTENTAGENT.RetentionPeriod: The period for which a file will be kept within the database, unaccessed, as a BLOB before migration to a BFILE. The default of 180 days may be excessive for many sites.
  

To start the Content Agent automatically, from the Content Services home page take the Node Configurations link. Select the node on which you want to run the agent to reach the node’s home page. All the possible agents are listed, but the Content Agent is not started initially by default; select it, and check the Initially Started check box.