Configuring the FEM Task for Updating Cached Synchronization Data

A flexible execution model (FEM) task runs in the background and monitors the associated build list designs for changes. When it identifies a change, it updates the cache. You can configure how this task runs.

Prerequisites

• You should be a system administrator.

• You must have configured Capital Integration Server in the capitalintegrationserverconfiguration.xml file in the config directory of your installation. See also “The capitalintegrationserverconfiguration.xml File Format” in the “clientprops.xml File Format” section of the Capital Configuration Files Reference Guide.

Procedure

1. Navigate to the config folder of your Capital installation and open the topologysync-configuration.xml file to edit.Figure 172: Default topologysync-configuration.xml file

2. Find the CachedSyncTask line and edit the parameters:autoschedule Set this to true to enable the updating of the cache. The scheduling specified by the cronexpression runs from when the Capital Integration Server starts.

cronexpression Enter a cron expression to schedule how often the indexing and tagging task runs. See Cron Syntax Usage Example to define cron expressions.

store_logs_per_execution Defines whether you want to store all execution logs. Default is set to false which means the log for only the latest execution run is stored.

3. Find the TaskParameters line and edit the parameters:cleanupfiles If the CachedSyncTask runs frequently, it accumulates task parameter files and log files quickly. Specify “true” to clean up (delete) these files automatically. Specify “false” if you do not want to run clean-up functionality. To archive the files rather than delete them, you can implement your own OS batch script.

cleanuptype If you have set cleanupfiles to “true”, this specifies how the files are cleaned up. Specify one of the following values: simple Deletes all the parameter files and log files for the task, excluding the files for the current task run.

retainbytime Deletes all the files that are older than a specified retention time (retentiontime parameter).

retainbycount Deletes all the files, excluding those for the specified number of last task executions (retentioncount parameter).

retentiontime Relates to the cleanuptype parameter with value retainbytime. Specify the maximum age (in milliseconds) of the parameter files and log files that are not deleted.

retentioncount Relates to the cleanuptype parameter with value retainbycount. Specify the number of last executions for which the parameter files and log files are not deleted.

cacheretentiontime Specifies the time (in seconds) that the system retains an unused cache for an associated build list before deleting it. This is useful in a situation where you remove a build list association in the Capital Wiring Integrator design, save, associate a different build list, and then decide to switch back.

Default parameters: With the following default parameters, the system deletes a cache if it has not been used for 1 day. It deletes the parameter and log files, but retains those from the last execution run of the task. cleanupfiles="true" cleanuptype="retainbycount" retentioncount="1 cacheretentiontime="86400"/>

4. Save and close the topologysync-configuration.xml file.

Results

• When Capital Integration Server starts, the system follows the scheduling specified by the cronexpression to run the task for updating the cache.

• For each execution of the task, the system creates two files in the temp folder of your Capital installation: An XML task parameter file whose name starts with “CachedSyncTask” followed by a unique identifier.

An execution log file whose name starts with “CapitalRunner” followed by the same unique identifier.

• You can monitor the tasks in the Tasks Tab in the Output Window, and access the log files. You can also access the log files in your temp folder.

Parent Topic:

Cached Synchronization Data

Capital Logic Designer User Guide, 2512

Unpublished work. © 2025 Siemens