View source | Discuss this page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Show collection (0 pages)
Collections help


Retail:Store Server Initial Data Reload


Bulbgraph.png   This functionality is available from RR17Q2.


When a store server is started it will always check with the central server if it is up-to-date with the data to be received from the central server. There are specific cases where the store server maybe not yet up-to-date:

The data reload logic is efficient in that it will only load the delta, the differences between the batches received in the store server before and new one's to be send from the central server.

Data Reload Status

A new field is present in the mobile server window: Reload Status.


This field can have the following values:

Mandatory versus Non-Mandatory Reload - forcing mandatory reload at startup

A distinction is made mandatory and non-mandatory reload.

Non-Mandatory reload will try to reload data from the central server. But if the central server is not available (because the store is offline) it will (after trying the reload) allow access from WebPOS.

Mandatory reload is relevant for when a store server is restored from a backup which might have missing data. In case of mandatory reload a successful reload from the central server is needed before the store server will allow access from WebPOS.

There are three different ways to force a mandatory reload:

ant -f modules/org.openbravo.replication.symmetricds/build.xml set.mandatory.reload.flag.current.server
The file path (location and name) by default is '/etc/hpvswitch.flag'. But you can override it by setting the file path and name in the property 'reload.flag.file.location' in The system will check for the existence of this file at startup. After a successful reload the system will set the value 'primary' in this file, so the mandatory reload is only triggered once.


The reload logic is triggered when the store server is started. The following steps are executed:

  1. The store server requests from the central server if there are any batches to load. The store server does this by comparing the last data batch which was loaded from the central server. It requests the central server to resend any missing batches. If the store is offline then no connection can be made to the central server and no data reload is done.
  2. The store server reload status is set to 'Reloading'. If the reload is mandatory for correct operation of the store server the status will be 'Reloading (Mandatory)'
  3. The store server then periodically (every 30 seconds) checks if the data reload has been done. In addition all import entries should be processed.
  4. If this is the case then the reload status of the store server is changed to 'OK'.
  5. If after 5 minutes the store server has not finished the data reload there are 2 cases:

WebPOS Access Disabled during Data Reload

During the data reload the WebPOS system can not access the store server. This is notified to the user with a popup box as is shown below.


Retrieved from ""

This page has been accessed 858 times. This page was last modified on 4 May 2017, at 08:19. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.