Failover

Both Windows and Mac desktop apps can fail over from one

BlackBerry AtHoc

server (the primary) to a secondary server. When the primary server becomes unresponsive and CUs fail, desktop apps that have a failover URL will fail over; that is, they will swap the Base URL with the failover URL. The desktop client attempts to contact the current server the number of times configured in the "Reconnect Attempts Before Failover" setting before trying the failover server.

There can be only one failover URL. You can configure the failover server URL in the

BlackBerry AtHoc

management system at

Settings

>

Desktop App

. The desktop app picks up the failover URL at SO but not at CU.

Failover occurs automatically. If the desktop app is unable to connect at CU, it will keep trying until it exceeds the value in “Reconnect Attempts Before Failover” in the Failover section of the Desktop App settings.

After the desktop app is connected to the failover server, if that server stops responding, the desktop app attempts to connect using the original Base URL value.

The user token (and possibly the userid) may be invalid when failing over or failing back. Users should be present in the failover system because it should be a recent copy of production. However, the user token or session ID may not be current which causes the server to reject the SO.