Synchronizing Changes¶
Background¶
As a customer, you may have a mix of aPriori applications:
- Multi-tenant application operating in the cloud, such as aP Design.
- Single-tenant applications operating on-prem, such as aP Pro on-prem
If your system has such a mix, you should synchronize the entities operating between both systems, to ensure that changes made apply to both sets. For example, after making changes to Digital Factories in aP Pro, these changes must be synced to the cloud to be available in aP Design.
Synchronization - ETL Sync¶
aPriori uses an ETL (Extract, Transform, Load) sync operation to synchronize aPriori single-tenant operational databases to the aPriori multi-tenant cloud.
This ETL sync operation is set up for you by aPriori when deploying your system, and typically runs out-of-hours each week.
Note:
aPriori strongly recommends out-of-hours operations, as if users cost parts while this ETL Sync is running, it may cause both costing failures and a failed sync operation.
To request an additional sync, please contact aPriori support.
Synchronizing Published Digital Factory Changes¶
Tip:
After you have made and published changes to Digital Factories (see Editing Digital Factories), these changes should be synced.
Some Digital Factory changes (such as logic changes or Machine data) also require a manual restart of the cloud services.