Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. To what should the OPAC session timeout be set?

    To what should the OPAC session timeout be set?

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Description:  
    2. Resolution:  
    3. Additional Info

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description:  


    What should the OPAC session timeout be set to?
       


    Resolution:  


    The session timeout is controlled by the www_a_session_time_out or the Meta-tags "REFRESH" value -- if it is present and has a lower value. 

    There are two considerations: 
    One is the freeing up of the resources associated with a session and a second is the privacy issue associated with public terminals. 

    1) Since the ALEPH Web OPAC is "stateless" there aren't many resources associated with a session. The z05/z110 result-sets persist regardless of any timeout which may occur. For license purposes, web sessions are considered active for 2 minutes even if the session has timed out. (And having a timeout longer than 2 minutes will not result in the session continuing to be counted as active for license purposes: the system will stop counting it after 2 minutes if the user has not hit Enter, even if it has not timed out.) 

    2) Thus, the main session time-out issue is the public-terminal privacy issue. Within this, there are 2 sub-cases: 
    (a) the case where the user is not signed on; and 
    (b) the case where the user *is* signed on. 

    2.a. If a non-signed-on user walks away from a public terminal, you, ideally, would not leave the search indefinitely for the next user to view. On the other hand, you don't want to kick a user back to the initial screen who is legitimately just sitting and thinking about a particular screen. We have been distributing the setenv www_a_session_time_out as 600 seconds (10 minutes). Customers implementing the OPAC have found a REFRESH value of "200" (3 minutes) to be too short. 

    2.b. The case of a user who *has* signed on and has failed to log off has bigger implications: the succeeding user could get the logged-on user's phone#, address, the books he/she has signed out, and change the user's pincode. 

    Additional Info

     

     


    • Article last edited: 12-Mar-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • TNS:packet writer failure"; "not connected to ORACLE"
      • Today's date in generic fix routine
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved