Data Replication Apps

Use a TIBCO Cloud™ Integration - Connect Data replication app to copy the contents of your CRM or marketing system to a local database for reporting or business intelligence.

The Apps list displays information about the status of On schedule, On event, and Data replication apps. The status icon provides a quick visual status of your apps. See TIBCO Cloud™ Integration - Connect Apps for detailed status information.

Once a Data replication app has been configured and is scheduled to run, the replication process does the following:

Note: If the target Connection configured in the Data replication app supports Bulk operations, then Batch Processing is used automatically to process records in batches instead of one at a time.

First Execution - The Data replication app creates the tables and corresponding fields in the target datastore in the likeness of the source datastore. Then, all source records for the entities selected in the app are replicated.
Subsequent Executions - The Data replication app selects new or updated source records, based on a datetime field, and only replicates those records. The source Connector automatically chooses the datetime field to be used for the Last Modified Date for each table.
These date fields are used each time a Data replication app runs to select only new or updated source records for replication. When the Data replication app runs, TIBCO Cloud™ Integration - Connect checks the target datastore for the most recent date in the fields specified by the Connector. TIBCO Cloud™ Integration - Connect uses that date to filter records in the source datastore. Records selected for replication include only records newer than the most recent date in any target record in the selected table.
If there is a Fatal Exception during replication, the next time the Data replication app runs TIBCO Cloud™ Integration - Connect subtracts 500 milliseconds from the date/time field found in the target table where the failure occurred. This ensures that no records are missed, however, a few records may be reprocessed unnecessarily.
Note: If you have manually imported records into your source datastore with a Last Modified Date that is older than the Last Modified Date in the target, these records are ignored during replication because the dates are too old.
Note: If you change the source schema, those changes are propagated to the target before the data is replicated. See Editing the Source Schema for additional details.
Note: If you change the source Connection for a Data replication app that has already replicated once and the new datastore has tables with the same names but a different schema, the app does not process any records. See the No Records Processed For Replication Solution With New Source Knowledge Base article for more information.
Note: Do not make manual modifications to the target datastore. Manually changing the target datastore can result in errors and prevent your Data replication apps from running.

Review the following additional topics for Data replication apps:

Note: If your subscription expires, or if you disable an app from the App details page, the app is marked as disabled. See Disabled Apps for more information.

Subtopics