Web Replication Using Azure Storage

This is an addition to web replications that utilize Azure Storage Account to distribute data packets from Head Office (the source) to stores or POS terminals (the destination). The process to set up what data to send and to which location is the same as before. You set up a Scheduler Job and a Scheduler Subjob to define the date and the source location and the destinations.

The jobs are triggered to run at scheduled intervals. When the jobs run, they create a package with the requested data, the package is then sent from the source to each destination location by the web replication module.

There is now an option to use Azure Storage Account to share packages with the destination location instead of pushing the packages into each destination location by OData requests. This will free the source location (HO) from doing the actual update at the destination location, which is the most resource consuming effort in the web replication process. By sharing the package in Azure Storage Account, the source location will only read the data and send it to Azure Storage Account, the destination locations will get the package from Azure Storage Account and update the data in the destination location.

Note: Any limitations that may have existed for the web replication are still in place (see Web Replication by Scheduler).

What's new in this process?

The source location keeps track of all data packages in the Azure Storage Account and keeps track of what destination locations should receive each package and what destinations have successfully received the package. The source location publishes a web request that destination locations call to get information about the next package to receive to confirm that a package has been received and the data has been updated at the destination location.

Web Replication Using Azure Storage

In this article

What's new in this process?