In this article
Content of the Configuration Packages
This article explains how to create the packages containing the data to be replicated to the POSs, and how to send these packages to the Azure Storage where they are later downloaded to the POSs.
Click here to download the configuration packages containing these scheduler jobs from the LS Retail Portal (requires login).
Content of the Configuration Packages
The OFFLINE_POS_INIT, OFFLINE_POS_UPDATE, and WEBREPLICATION scheduler jobs are included in the configuration package as examples that can be reused for the Offline POS using Azure Storage replication.
| Job ID | Description |
|---|---|
| OFFLINE_POS_INIT | Scheduler job with normal subjobs to replicate the most common tables to run the POS. |
| OFFLINE_POS_UPDATE | Scheduler job with action subjobs to replicate the deltas (inserted, modified, and deleted records). |
| WEBREPLICATION | Scheduler job to process the web replication request queue, create the data packages, and send them to Azure Storage. |
The OFFLINE_POS_INIT and OFFLINE_POS_UPDATE jobs are meant to create an entry in the Web Replication Request Queue page, which will later be processed by the WEBREPLICATION scheduler job to create the package containing data to be replicated to the POSs and to send them to the container in Azure Storage. You can create as many replication jobs as you need.
Scheduler jobs created for this purpose should have the Use Web Replication check box enabled.
The WEBREPLICATION job is responsible for processing all the entries in the Web Replication Request Queue page. When processing each entry, the job creates the packages with the data to be replicated to the POSs and sends these packages to the container in Azure Storage.
Most likely, you only need to have one job for this purpose, and the Use Web Replication check box does not need to be enabled.
Setting up the Scheduler Jobs
Take for example this scheduler job named OFFLINE_POS_INIT:
/Create packages_1_700x1009.png)
- In your job's Scheduler Job page, in the Object Setup FastTab:
- Enable the Use Web Replication check box.
- Enter the LSC Data Distribution WS codeunit (Object Type: Codeunit, Object No.: 99008923).
- Click the Run Now action.
- Running the job (if there is anything to do) results in a new Request Queue entry as usual.
To see the request queue, click the Related action, then click Web Replication - Request Queue./Create packages_2_700x204.png)
-
Process the waiting request queue by reading the required data and sending the package to the Azure Storage Account. Use, for example, the WEBREPLICATION scheduler job:
/Create packages_3_700x374.png)
- In the Scheduler Job page, in the Object Setup FastTab:
- Enter the LSC Web Repl. Functions codeunit (Object Type: Codeunit, Object No.: 99009521)
- Click the Run Now action.
- This processes the waiting request queue by reading the required data and sending the package to the Azure Storage Account.
If the package has been stored at the Azure Storage Account, a Web Replication Storage Packet Queue entry is created./Create packages_4_700x136.png)
For each data package a link is created in the Web Replication Azure Storage Distribution Queue for each destination location that should receive the package.
/Create packages_5_700x187.png)
This concludes the process at the source location (HO).
The Azure Storage Distribution Log (which is accessible from the Web Replication Azure Storage Packet Queue page) is filled out when destination locations have confirmed the package as received.
Note: Any limitations that may have existed for the web replication are still in place (see Web Replication Limitations).