Synchronization Scheduler performs the synchronization of the applications from Adobe® LiveCycle® repository to CRX™ repository. It reads all resources from LiveCycle and selects only the supported resources to synchronize with the CRX repository. It runs periodically and on each run synchronizes the applications that have been marked for synchronize on CRX repository. On-demand synchronization option synchronizes all applications between CRX and LiveCycle repositories. The applications that are present on LiveCycle and not yet on CRX are created as hanging nodes and marked for synchronization. So when Synchronization Scheduler runs, it finds all applications marked for synchronization and performs the synchronization operation.
Synchronization Scheduler performs the following operations at each run:
Activation Scheduler performs the function of activating/deactivating assets that have been scheduled for activation/deactivation. It also performs the function of purging temporary archives. Upload/download operations on the Forms Manager user interface create temporary archives. The scheduler runs periodically and searches for scheduled assets. You can also force the operation of Activation Scheduler using Force Schedule.
Activation Scheduler primarily performs two functions:
SynchronizationSchedulerFrequency variable in FormsManagerConfiguration defines the time period (in minutes) after which the scheduler runs. The default value for the period is three minutes. For more information about configuring this value, see Changing secheduler configuration below.
Also, you can choose to synchronize forms either synchronously or asynchronously. The optimum and the default method to synchronize forms is asynchronously.
To change the configuration of the schedulers, go to the OSGi console and perform the following steps:
Root folder property defines the CRX node path where the LiveCycle application data is replicated on CRX. Apart from the resource properties for all applications, forms and image, the node also contains additional metadata about the form (for example, activation date, deactivation date, tags, sample data, submit URL and render profiles). The default value for this property is /content/dam/lcapplications. Do not update this property value once meta information is added to forms.
To change the configuration for the root folder, go to the OSGi console and perform the following steps: