Migrating the existing order data to Order Service

IBM Sterling® Order Management System provides indexing and search capabilities of transactional data through Order Search, a component of Order Service.

Sterling™ Order Management System provides a built-in integration for the ‘Order’ entity, and an outline of an order is saved in Order Search whenever it is created or modified in Sterling Order Management System. This brings the latest state of order to Order Search to search for orders without depending on Sterling Order Management System and Order Search becomes the single source of visibility for all the orders that are fulfilled through Sterling Order Management System.

When you enable the built-in integration, orders created or updated in the Sterling Order Management System application server and agent/integration servers are saved and indexed in Order Search.

The orders which are created or modified from the time of enablement are processed automatically for indexing. But Sterling Order Management System contains orders that reached an end-state such as fulfilled, delivered, closed, and so on. There could be orders that are on hold or waiting on some resolutions to proceed forward. Besides these, many orders would have reached history tables at the time of enabling the built-in integration with Order Service. So, for Order Search to become a single source of truth for orders that are fulfilled through Sterling Order Management System, you must migrate these types of orders to Order Search.

Sterling Order Management System provides synchronization agents to migrate all existing orders to Order Search. To optimize the effort to save and index orders appropriately, you must adhere to the following steps.

Migration strategy

Complete the following actions in the following sequence:

Configure the agent criteria for SSI_MASS_SYNC. Use ‘unindexed’ mode for migration purpose. Do not set for auto-triggering.
Start the server where the SSI_MASS_SYNC agent is associated with and trigger the Mass Sync agent criteria one by one. All the unindexed non-history orders get migrated.
After completion, stop the agent server where the SSI_MASS_SYNC agent is running.
Log in to the System Management Administrator Console and mark order index as synchronized for all the enterprises for which you ran the SSI_MASS_SYNC agent.

The non-history orders and all order modifications are sent to the index for the current period. Contact your Elasticsearch administrator periodically to monitor the index size. If the index file size is nearing to maximum file size as recommended by Elasticsearch, you must clone the current index to create an index. Despite that cloning the current index at regular time intervals based on your order volume is a good practice. It is recommended to follow this.