Data migration and Order Archive agent

You can review the information about data migration and Order Archive agent.

For orders to be eligible for archival, it is mandatory that the orders are saved in Order Search and the corresponding record is present in the archival staging location. Orders are staged for archival once they are purged and moved to history table. Due to this reason, archival of existing history orders, which are already purged may not happen as they are not staged for archival and not present in Order Search.

The following agents handles archival of such orders:

The OSI_HISTORY_MASS_SYNC agent migrates history orders to Order Search and stage the orders for archival. The eventual goal of this agent is to facilitate archival of orders present in history tables and delete them from Sterling Order Management System Software. However, every order in history is not eligible to archive at a time, and hence this agent stages them for archival so that the OSI_ORDER_ARCHIVE agent that runs periodically can archive the eligible orders. Basically, this agent migrates the order outline data for history orders to Order Search and initiate the archival of history orders to Archive Service, which archives and removes the entire order data from Sterling Order Management System Software. This is required to run immediately after enabling the build-in integration with Order Search and enabling the Sterling Search Index feature. You can stop this agent after all the history orders are migrated to Order Search and staged for archival.

The OSI_ORDER_ARCHIVE agent archives the orders present in staging location to Archive Service. On successful archive, it deletes the order and its related history records from the Sterling Order Management System Software database.

For more information about these agents, see Business process time-triggered transactions.