eSync: Metadata Dependency Checking on Content

  • Updated

When you select a particular content item to synchronise, eSync determines whether the content item contains any dependencies on other items, such as images or files in the library; those images or files can be synced at the same time as the content. The dependency check also uses metadata values. For example, if there is a Content Resource Selector defined in the metadata, and it contains links to other, related, content, the dependency checker also parses those content items. This can lead to extended run times for a simple content sync because (worst-case) it could end up reading through all content items in the database.

The Ektron Windows Service handles eSync and the dependency checking. By default, metadata dependency checking is enabled and configured for unlimited recursion.

You can configure the Ektron Windows Service 4.0 configuration file (typically located at  C:\Program Files (x86)\Ektron\EktronWindowsService40\Ektron.ASM.EktronServices40.exe.config ) to disable metadata dependency sync or limit its recursion using the following key/value pairs:

  • EnableMetadataEvalInDependencySync - The default value is true; this enables metadata dependency checking. When set to false, files and content specified in metadata will not be synced during a content sync.
  • DependencySyncRecursionDepth - The default value is 0; this means that all dependencies will be evaluated regardless of recursion depth. A value other then 0 limits the depth to that value.

After making changes to the configuration file, stop and then restart the Ektron Windows Service.