In ServerConfig.xml:

•AlivePeriod: The number of seconds between successive 'heart beat' signals indicating that a specific server login is still used (default 300 = 5 minutes).

This value must be lower than LoginTimeout, otherwise the session is considered 'idle' and removed from the database.

•LoginTimeout: The number of seconds of inactivity before a idle login is forced to logout (default 1200 = 20 minutes.).

The seconds are counted from the last 'heart beat' of the login.

Note that this timeout value is valid only for the Client logins (that is, the SOAP clients: Cmd4, Ted4, etc...). The Web logins (browsers) are limited to the IIS session timeout value.

•CheckLoginTimer: In versions 2.2 and newer: The time inverval of AlivePeriod is used. In versions prior to 2.2: The number of seconds between successive Client login timeout verifications (default 300 = 5 minutes). It is the polling time of the server timer that looks for the 'idle' sessions. Note that the server timer checks only the timeout of the Client logins (that is, the SOAP clients: Cmd4, Ted4, etc...).

In Back4Config.xml:

•LoginLastAccessTimeSpan of the CleanupProcess.

It is a time-span (default '0.00:30:00': 30 minutes).

The logins that have not been used for longer than this time-span are eliminated by Back4.

 

Be careful when configuring these parameters: wrong values can force GN4 to remove login data from the database when the session is still alive.

In this case, the 'Failure to restore login' error occurs at the first request that the user sends to the server.