The FileSystem Companion Manager displays a list of existing configurations. You can create new configurations, as well as edit, delete and activate/deactivate existing ones. If the name of an existing FileSystem Companion instance and the name of a configuration match, the settings specified in the configuration take effect for the respective instance.
The following Information is displayed for each instance:
• Status – Running/Not Running/Deactivated
• Name – Name of the instance. Should match the name of an existing instance of the FileSystem Companion
• Folders – Number of and path to folders to be watched, and name of the catalog to which the file system events are synchronised
• Event Queue Size – Number of assets for which file system events are waiting to be processed
The following columns provide information on inconsistencies found by the resync process running in the background. Usually, these inconsistencies are solved automatically within a certain amount of time.
• Missing Records – number of assets with no corresponding records
• Missing Assets – number of records with no corresponding asset
• Checksum Problems – number of reference inconsistencies
Existing or new instances are configured via the Edit Instance Configuration window.
Folders
A list of folders to be watched by the instance. The following information is displayed for each folder:
• Folder – Absolute path to the folder to be watched. All folders below this folder will be watched, too
NOTE: This leads to a (technical) source category tree which is visible under All in the Category pane. This category tree must not be modified manually!
• Catalog – Name of the catalog to which file system events from the specified folder are synchronized. Catalogs can be selected via d drop-down list
NOTE: It is not possible to apply system events from different folder paths to the same catalog!.
• Asset Handling Set – Name of the Asset Handling Set to be used with the Cumulus action. Can be selected via a drop-down list
• Permissions Template – Name of the Permissions Template to be applied. Can be selected via d drop-down list
Settings
In this section, several time out values can be specified.
• Activity time-out – Minimum delay between the receipt of a file system event and its conversion into a Cumulus action.
NOTE: Usually, the actual time between a file system event and the resulting Cumulus action is larger than this value, depending on the load on the machine and the number of file system events coming in.
• Timeout for record resync runs – Resync thread waits at least that amount of time between checking for records without asset and assets without record
• Timeout for category resync runs – Resync thread waits at least that amount of time between checking the technical FileSystem Companion category structure for categories without matching folders on disk.
• Timeout for delaying actions in resyncs – Resync thread waits at least that amount of time after it has detected an inconsistency (for example a record in the catalog with missing asset) and before the according cleanup function is executed (in this example, deleting the record).
Exclusion List
A list of files, file types and folders which are to be ignored by the FileSystem Companion.
These settings must be notated in regular expressions!