Sync

Syncing mapping algorithms

Mapping algorithms can be synced in one of two ways:

1. Syncing a locally managed Mapping algorithm: This can be done to effectively make a copy of an algorithm from one Continuous Compliance Engine to another. In addition to syncing the algorithm, the mappings must be manually exported from the source engine and imported into the target engine. Once this is complete, the two algorithms (on the source and target) will have the same names and initial set of mappings (at the time of sync) but will function as two separate algorithms. That is to say, adding new mappings on the source will not have any impact on the algorithm on the target.

   1. For subsequent syncing of a mapping algorithm that already exists on the target, follow the steps below to sync a mapping algorithm with locally managed mappings:

      1. Export the mapping algorithm from the source.

      2. Export the mapping values for the mapping algorithm from the source via UI or API. This step can be skipped if the mapping values are available from the original .txt or .csv file.

      3. Delete the current mapping values associated with the mapping algorithm from the target.

      4. Import the mapping algorithm to the target.

      5. Import the mapping values that were exported from the source. Mapping values can also be imported from the original .txt or .csv file.

2. Syncing a remotely managed Mapping algorithm: This can be done to share the same Mapping algorithm across Continuous Compliance Engines. In this case, once synced, the algorithm on the source and target(s) would point to the SAME remote mapping database. This would mean that adding/removing/manipulating the mappings would affect the algorithm on all engines that use it.

More information on Sync can be found on the Introduction (Managing multiple engines for masking) page.