Skip to content

Engine runner

Allows us to run the replication process directly, without the necessity to create a scheduled process.

below we can see how the initial screen looks like:

Engine runner example

In this screen we have three common fields:

  • Operation Type: Is the kind of operation that we want to execute. There are three types: Export: Represents an export process. Import: Represents an import process. Sync: Represents an import/export process.

    Each time we change this field, the screen will be updated and will only show the fields that belong to the respective operation.

  • Applications: Applications available for replication.

  • Sites: Sites available for replication.

Date and Time fields are only available for sync and export operation, and together compose the LAST_EXPORT_TIME placeholder. This placeholder is used to set a lower bound for LastUpdatedUtc.

  • Date: Represents the date that will be used to filter the data.
  • Time: Represents the time that will be used to filter the data.

Important

When an export process is performed, there will be only selected those rows whose LastUpdatedUtc values are higher than the LAST_EXPORT_TIME placeholder. This value is persisted separately for each rule, source site and destination site in an entity called ExportRuleExecutionTime. When none is found, the placeholder takes the minimum value allowed by the database, disabling the restriction. The previous configuration is used to manually set this value during execution.

Engine runner export

The following field is only available for sync and import operations:

  • Ignore sequence numbers: allows us to ignore the sequence number when importing.

Engine runner import