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 Update User Documentation


Bulbgraph.png   This functionality is available from RR17Q2.1.


Openbravo provides several windows/tools for the application administrator to follow the update process and enable hot fixing. Only in exceptional cases will the end user be notified of any version incompatibilities.

Store Server Version Overview Window

This is the main window which you can use during the update process to check the status of each store server. You operate this window from the central server. It gives version details for each server and also related information like server status and version differences between the store and central server.

The window retrieves its information by calling the store servers directly so it shows real-time information. It will also signal if a store server can not be reached (it will show version status Unknown in that case).

StoreServerUpdate Overview Window.png

The meaning of the different fields:

The version status field is also shown in the Mobile Server Window.

Modules by Server

To provide complete visibility of what is installed in your environment you can check the Modules by Server sub tab in the Mobile Server window. It shows the modules installed on the store server with their respective version numbers.

StoreServerUpdate Modules by Server.png

Incompatible Versions and Data Pending to Sync - User Message

There is one special case in which a user will get notified of a version incompatibility:

If this situation occurs the user will see a message like this and is logged out automatically:

StoreServer Update StoreCentralDifferent.png

In this case the user can not continue on the central server as the WebPOS client is in a newer version than the store server and would try to create data in the data would be created in the central server while there is also data pending to sync from the store server to central.

The solution is that the user uses the store-mode, so uses the store server url to load the WebPOS. The assumption is that the user has a short cut on the desktop to switch to store-mode, or another easy accessible way to accomplish this.

Forcing Version Computation (available from 17Q3)

The version information of a store/central server is recomputed every time when the server is restarted. Still it can make sense to force a recomputation if you feel that the data is not up-to-date. This can be helpful in testing situations.

For this purpose you can select a server and click the 'Recompute Version Information' button to let the version information for that server to be recomputed.

StoreServer Update Version Module.png

Installing hot fixes - the ignore-version-check preference

Hot fixes are updates which fix urgent issues in a production environment. These types of updates need to be installed quickly and are most of the time backward compatible.

If the hot fix is applied without a module version change then the version checking will not detect differences and work can continue as if there was no update.

If your hot fix also included a module version change then to prevent version-compatibility checks from failing you need to set the ignore-version-check preference before installing the hot fix. The preference should not be set on system level (client/org 0) but in your specific client and without filtering fields (like user/organization etc.).

The value should be set to 'Y' to enable the preference and to 'N' to disable the preference.

StoreServer Update SetPreference.png

Retrieved from ""

This page has been accessed 1,174 times. This page was last modified on 26 June 2017, at 15:42. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.