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

PDF Books
Add page
Show collection (0 pages)
Collections help


Store Server Online and Offline Concepts


Online & Offline concepts of Store Servers

An important feature of the store and central server management is keeping track of the connection status to other servers. The connection status to other servers (most importantly the central server) controls the 'online status' of a store server. If a central server can be reached a store server is online, if it can't be reached a store server is offline. If the central server itself is offline all store servers are offline also.

So only specific servers in the mobile server definition are of importance for the connection status of a store server. These are the servers which have the 'trigger' flag checked and which are accessible for the organization of the store.

Online & Offline State Transitions

An Openbravo Commerce store server can go through several states:


When the store server is transitioning to online or offline the WebPOS clients are not allowed to perform any transactions. In this case the user is notified and can relog in. Normally the transition period should be short, minutes. This 'blocking' behavior is by default switched of. To enable it you have to set the preference Multi Server Architecture Enablement to 'Y'. After changing this preference the system should be restarted as it caches the current value.


At startup: offline to online

Just for your information: when a store server starts it is automatically set to offline state and then to transition to online. If all the checks pass then the server automatically transitions to online. If one or more of the online checks fail then the server remains (correctly) in offline state and the standard periodical check is done for transitioning to online.

This approach is taken to ensure that the store server at startup is in the correct state (either offline or online).

Detecting Central Server Connection Status

When the store is operating any user action which involves the central server will automatically check store to central server connectivity. It also makes sense to check connectivity in store-closed hours. For this the store server logic will automatically install and schedule a process request which runs periodically to check the connection status to the central server.

The run period is determined by the Mobile Server Status Ping Periodicity. If the preference is not set then the default is 300 seconds.

The logic of this process is that it sends pings from the central server to the store servers. The store servers check when they last received a ping. If more than 3 pings are not received (so wait time is three times Mobile Server Status Ping Periodicity) then the store server will go offline. As the process runs periodically it can take in average 3.5 times the Mobile Server Status Ping Periodicity before offline central server is detected in quiet periods.

Causes for staying offline

There can be several reasons that a store server is and remains offline:

The reason for a store server remaining offline can be found in the 'Offline Log/Cause' field in its mobile server window.


If there is a connection between central and store then this field is replicated from the store to the central server and can be checked there. If no connection between central and store then you can check this field in the relevant Mobile Server Definition record in the store server.

Currently 2 types of messages are shown in the offline log field:

Transitioning Triggers - Send Transition to Online

Transition to online and offline is triggered by different events.

An online server communicates with the central server frequently for example when creating tickets (in synchronized mode). When the communication fails or the server responds with a server error then the server is assumed to be offline. For transition to offline the main trigger is the un-availability of the central server.

An offline server will test the connection to the central server at regular intervals (using the request router ping time). If the central the server reacts to the ping then the store server will move to transition to online. If the transition to online fails then the store server will move back to offline. As the transition to online failed the store server will now wait a longer time, defined by the Failed Transition to Online Wait Time preference (default one hour).

Another way to trigger a server to transition to online is to send it a transition to online trigger. This can be done from the central server by going to the mobile server window, selecting the offline server and then clicking the 'Send Transition to Online' button.


Clicking this button will trigger a transition to online, depending on the situation the store server transitions to online after a few minutes.

Retrieved from ""

This page has been accessed 1,682 times. This page was last modified on 13 March 2018, at 16:34. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.