QlikView App Dev

[ssriramin19]

Hello everyone,

What is the meaning of the following parameters in the QVS setup:

Maximum Inactive Session Time

Maximum Total Session Time

Possible Session Timeout

Document Timeout

Whether the above parameters can be configured ? Is there any default for all the above parameters ?

Please provide the inputs

Thanks

Sriram

[simsondevadoss]

Possible Session Timeout (seconds)

When the session has had no activity for the specified number of seconds, it is eligible to be closed if a

new user requests to start a session

Maximum Inactive Session Time (seconds)

If this setting is non-zero, and the session has had no activity for the specified number of seconds, it will

automatically be terminated by QlikView Server.

Maximum Total Session Time (seconds)

If this setting is non-zero, all sessions will be limited to the maximum number of seconds as specified.

Once the time limit is reached, the session will automatically be terminated by QlikView Server.

[simsondevadoss]

And above can be also configured

[Levi_Turner · Accepted solution]

Remember that you can always click on Help in the QlikView Management Console to get context sensitive help:

Maximum Inactive Session Time - Maximum time at which the QlikView Server will close a session with a user who has no activity.

Maximum Total Session Time - Maximum time at which the QlikView Server will close all sessions, regardless of whether the user is active or not.

Possible Session Timeout - Time at which the QlikView Server can close an inactive session. The QlikView Server will do so if the maximum number of concurrent sessions has been reached and there is another user who has requested a session. So if you have a max of 100 sessions, and one person has not been active in 30 minutes while another user is requesting a session, then the QlikView Server will end the session with the inactive user and allocate the session to the new user.

Document Timeout - Document level settings which can over-ride the Server level settings. The more restrictive is used. So using more permissive settings on the document level will not achieve the effect you desire.

[tresesco]

Goto QMC->System->QVS Select your server name)->Performance (tab)

Here, you get to set these parameters. Defaults values are, 5000, 1800, 1800 seconds (are set already). For what it is for, click on the 'Help' when the tab is open, it is explained nicely there.

[ssriramin19]

What is document time then ?

Please brief on document time out

[Levi_Turner]

There's a system wide document timeout which is the amount of time an inactive document will be kept in the QlikView Server's memory. That is set in the System settings:

But there are also document level settings which can be set to be more restrictive than the system wide settings like so:

[qvraj123]

Hi

our security department gone through our existing applications and has some findings. I am not an admin but was assigned to do some research on the following.

ISSUE

Is from the browser when a single user using his AD credentials can login into two different computers

and access the report - two different sessions on two different systems (lets say a laptop, and a desktop)

When this happens - are we not supposed to see any message like session already active, some kind of message so that the user has only one session active; may be restrict the user to only 1 session which is active

>> we are QV version 11 with 64BIT 

could you please point me in the right direction as to what could be settings if any

thanks a lot for your time

Rj

[Levi_Turner]

So as I understand it, you'd like to configure things so that users cannot have two simultaneous sessions*?

Let me preface this by saying I have focused on Qlik Sense over the past 6 months, but from memory out of the box there is no way to limit the sessions. This would need to be done at something before the user gets to QlikView. But that is from memory.

* Strictly speaking you cannot have two simultaneous sessions in QlikView. When you try to move from session two back to session one, you will receive a reconnecting dialog.