Setup on the Offline POS

In this article

Setup

Get packages

Note: If you are using Update Service to install the offline POS, most of the setup listed below is included in that process. Refer to the Implementation Guide to see instructions on how to set up the Offline POS using Update Service.

To be able to receive the data packages, follow the instructions below on how to set up the location and how to get packages.

Setup

1. Set the distribution location and store number to the current location.
   • In the Retail Setup card, the General FastTab, specify:
     • The current location in the Local Distribution Location field, for example DEVICE001.
       
     • In the distribution location (the Local Distribution Location in the Retail Setup card), activate the Azure Storage Active field in the Distribution Location Card:

       

     • The current store in the Local Store No. field - although it is not needed for the replication, it is needed to run the POS terminal later.

2. Set the distribution location to the Azure Storage Control Location (HO), to which the requests for new packages will be sent:

   • In the Scheduler Setup card, in the General FastTab, specify the control location in the Azure Storage Control Location field.
     Note: In the distribution location for the Azure Storage Control Location (HO distribution location), you need to have the Web Server FastTab properly filled out for the POS to be able to connect to Head Office in SaaS.
     

Get packages

You have two options, Background session and Scheduler job, when it comes to updating the data in the POS terminal:

1. Background session

   If you choose the this option, to run the update on the POS as a background session, the update process is active while the POS is running.

   • Navigate to the POS Functionality Profile Card, the Web Services Settings FastTab, and enable the Run Azure Storage Repl. Update In Background Session check box.

   The POS monitors this background session, and notifies if something is wrong.

   Tip: You can also monitor the background session in LS Central in the POS Terminal Card:

   • Go to the POS Terminal List, click the Terminal action, and then click Background Sessions to display a list of all POS related background sessions.

2. Scheduler job

   If you choose this option, to run the update as a Scheduler Job, you must create a Scheduler Job to run codeunit 10000773 LSC Web Repl. AzS Utility.

   • Go to the Scheduler Job page, and in the Object Setup FastTab, fill in the fields as shown in the image below:

     

Note: We recommend to manually run the AZSREPLUPDATE scheduler job after you set up the POS for the first replication, to verify that it is working fine.

The process of getting the packages is the same, whether as a background session or a Scheduler job.

A request is sent to the Azure Storage Control Location (HO) asking for a reference to the next package to fetch. During this step, the Local Distribution Location in the Retail Setup is sent in the request so the HO knows what location is actually asking for new packages. The package is then imported from the Azure Storage Account and the web replication module updates the data.

When the package has been imported at the destination location, a web service call is made to the Azure Storage Control Location (HO) confirming that the package has been successfully received and processed.