Encodify provides the capability of linking a Module with an external file system, with the files being represented by individual Module items.
This scheduler job is set up to regularly scan the file structure for changes and synchronize them with the Module.
Parameter | Description |
|---|---|
joblist=FileSystemSynchronizer | Name of the Scheduler job to be executed. You can specify your own name instead of “FileSystemSynchronizer” in the example. |
job.FileSystemSynchronizer.type= dk.encode.ebms.core.file.externalFileSystem.ExternalFSSyncJob | The name of the class that performs the synchronizer job. |
job.FileSystemSynchronizer.param.moduleId | Specify ID of the module to run synchronization for. You can specify several module IDs, separating them by commas. |
job.FileSystemSynchronizer.siteId | If synchronization for all the Modules with enabled EFS within the site is needed, specify ID of the site. Similarly, you can specify several site IDs separating them by commas. |
job.FileSystemSynchronizer.interval | Interval in seconds at which Synchronizer job will be rerun. |
job.FileSystemSynchronizer.param.isDetectingOfEfsIdentifierEnabled=false | If “true”, job will synchronize the system and EFS only when the EFS identifier file (name is ".efsIdentifier" without quotes) is present in the folder mapped as EFS root (no matter if the folder is local or a symbolic link). If the identifier is not present, the job will stop normally with an informative message |
Note! If no files or subfolders are present in EFS root folder, the job will not run. For example, if root folder is completely cleared for some reason, module items will not be removed. To avoid this, an empty folder should be created in the root folder.