Data export scenarios

You can review the different scenarios for exporting data.

The three scenarios of data export are as follows:

Mass update

In this scenario, the system imports a substantial number of changes from an external system. An export is triggered immediately after the import is complete. The product administrator sets up a service to trigger the export upon completion of the update.

Note:

Mass updates are done by using the YSCEntityChangeMassManageUtil that is part of the change project management system. At times, changes are first made on a staging server, and then promoted to a production server. In such cases, mass updates must also first be done on the staging server and then exported to the production server. The production server then exports changes to profiles which are transferred to the targets.

Scheduled export

A scheduled export is done according to a preset configuration and is the most common way of running agents in the SMCFS product. The agent is configured to run at defined intervals (hourly, daily, weekly) or as defined by the administrator. When the transport layer receives an event that indicates an export was completed, the transport layer transfers the files to the targets appropriately.

On-demand export

In this scenario, the user completes some high-priority updates to the system and exports the changes immediately by manually triggering an export agent.

External custom data export

In this scenario, because of the high volume of the data, initial full sync of the catalog and related sync profiles is done manually outside the sync agents using the native database features. Delta-sync for the same sync profiles is done using the data-sync feature of the SMCFS product.

For more information, see External custom full sync support.