Keri Systems Doors.NET Manual - Manual (Page 472)

Doors.NET Reference Manual
- 472 -
Handling Offline or Network Outage
States
The system is designed to have the ability to handle communications loss to controllers
or network outage and recover from those when communications is restored. A system
entering into or already in a Global Lock/Unlock state can be greatly affected by an off-
line controller or a network outage. The system is designed to handle recovery from
these conditions, and to mitigate the effects the recovery may have on the system. The
following conditions are currently handled:
l
The Gateway service is not running when the system state is changed. The state
change could be software based or could occur via an input from another Gateway
that is online.
l
The Gateway is online but a controller on that Gateway is offline.
l
The Gateway service is running and was connected to Application Server but is off-
line when a state change occurs.
l
The Client UI is not running when a state change occurs.
l
The Client UI is running and was connected to Application Server but is offline
when a state change occurs.
l
A controller with a Global Lock or Global Unlock input and those inputs are Normal
goes offline, and then a state change occurs.
l
A controller with a Global Lock or Global Unlock input and those inputs are Active
goes offline.
l
A power outage or Application Server service stoppage.
Both the Client UI and the Gateway retrieves the current system state and Situation Man-
ager rules on startup and on a reconnect to the Application Server. The Client UI will
change its Situation Manager icons to match the current state. The Gateways will check
each controller as it comes online (either at initial startup or a reconnect) for the con-
troller’s current state (Normal, Global Lock, Global Unlock). If the controller’s state does
not match the Gateway’s current state, the Gateway will update that controller to the cor-
rect state.
The Application Server updates the database when in Latched mode as the changes
happen to Global Lock or Global Unlock inputs. This happens in real time as the events
are sent to the Application Server. This table is only updated by the Application Server
and is queried at Application Server startup. This ensures the current state of the Global
Lock and Global Unlock inputs will still be valid following a planned or unplanned shut-
down of the Application Server service.