Introducing the edge deployment server

Sterling Order Management System Software serves a multitude of stores simultaneously with a single enterprise server. In such scenarios, the load on the enterprise Sterling Order Management System Software enterprise server would be too high and since all the clients connect to a single server, the communication time increases. To handle such issues, Sterling Selling and Fulfillment suite version 9.3 features architectural enhancements for Sterling Order Management System Software to be extended to multiple servers, each serving a local population of users. These enhancements enable a scalable implementation model having a mix of corporate enterprise servers, regional servers, and remote servers that reside on the edges of the network, such as retail stores, warehouse and depot locations. These edge deployment models lend themselves very well to point of sales implementations, which may involve the use of additional servers deployed locally in the physical store. Such servers can support key functional components across a choice of implementation models.

Edge deployment server has its own database where the configuration data and the master data are synced from the Sterling Order Management System Software. The order data that is captured on the edge resides on the edge deployment server. After the order capture process of the order flow is completed by the edge, it synchronizes this data to the Sterling Order Management System Software enterprise server and the order data that is on the edge deployment server can be purged.

The following diagram and description explains the interaction and the synchronization process flow between edge deployment server and the Sterling Order Management System Software enterprise server.

  1. The clients of Store 1 are connected to the OMS Server v1. Where OMS Server v1 is the Sterling Order Management System Software enterprise server.
  2. The clients of store 2 and store 3 connects to EDS-S2 and EDS-S3 servers respectively. Where EDS-S2 and EDS-S3 are the edge deployment servers that physically reside at store 2 and store 3.
  3. The EDS-S2 and EDS-S3 in turn connects to all the external servers that the OMS Server v1 connects to. That is, from the above diagram, the edge deployment server connects to the Promising Server, Tax Server, and Other External Server.
  4. EDS-S2 and EDS-S3 has its own database where the configuration data and the master data are synced from the OMS Server v1.
  5. All the order data that is captured on the edge deployment servers for store 2 and store 3 resides on EDS-S2 and EDS-S3.
  6. Once the sales order capture process is completed, the order sync process is initiated between EDS-S2, EDS-S3 and OMS Server v1.
  7. Once the order sync process is completed, the order data that is on the EDS-S2 and EDS-S3 can be purged.