Configuring Client Redundancy
Client redundancy in GENESIS allows front-end clients, such as GraphWorX, HTML5, or Data Explorer, to switch between FrameWorX connections, so that they have continuous access to data.
Unlike FrameWorX redundancy, which the servers apply on the server side, client redundancy runs the same switching logic inside the client application. When the FrameWorX server the client is connected to becomes unavailable, the client fails over to the next server in the cluster on its own, without waiting for a server to redirect it.
To set up client redundancy, select the Use as default Cluster for Standard Clients checkbox in the FrameWorX cluster settings.
Clients then download the cluster configuration and keep it up to date automatically. A client applies the configuration as soon as it connects and continues to use it even after a restart, and any later change to the cluster is picked up without reconfiguring the client.
You can verify the functioning of security context switching by configuring FrameWorX/Client Side Redundancy and enabling Security. Login and open GraphWorX, subscribe to :ServerComputerName in a process point and shut down the FrameWorX service on the server you are connected to. GraphWorX should switch automatically to the next node in the cluster and you would be signed under the same user and continue viewing your screen.
Security Context Continuity
When GENESIS Security is enabled, the active user's security context is synchronized across the FrameWorX servers in the default cluster. If a failover occurs, a signed-in user remains signed in on the new active server and continues working without being prompted to log in again.
All computers in the default cluster must use the identical configuration database, in particular the cluster and security configuration, for security context continuity to work correctly.
FrameWorX Connections
You can only set up client redundancy with direct FrameWorX connections, because clients always connect to FrameWorX (not the other way round) and cannot use a reverse connection to a FrameWorX server.