Summary

You can set the amount of time that a WebLink user can remain inactive before being logged out of the Laserfiche repository. This article describes how to configure this timeout limit.

Resolution

The length of time that a user can remain inactive before being logged out of the Laserfiche repository while using WebLink 6 is controlled by Internet Information Services (IIS). You can configure this session timeout setting in IIS. The session timeout when using WebLink 7 is controlled by the Web.config file located in Web Files subfolder of your WebLink 7 installation folder.

To change the Session timeout value in Internet Information Services for WebLink 6:

1. Load the Internet Information Services MMC snap-in. It can be found under Administrative Tools in the Control Panel.
2. Expand the server hosting WebLink.
3. Expand Web Sites.
4. Expand Default Web Site.
5. To configure WebLink 6, select WebLink.
6. From the Action menu, select Properties.
7. In the Virtual Directory tab, click Configuration to open the Application Configuration dialog box.
8. Click the Options tab.
9. In the Session timeout option, set the amount of time (in minutes) that you wish to allow a WebLink user to remain inactive before being logged out of the repository.
10. Click OK to close the Application Configuration dialog box.
11. Click OK to close the virtual directory's properties dialog box.

To change the timeout value in Web.config for WebLink 7:

1. Using a text editor, open the Web.config file located in the Web Files subfolder of your WebLink 7 installation folder. By default, Web.config should be located at C:\Program Files\Laserfiche\WebLink 7\Web Files.
2. locate the <sessionState> element.
3. Modify the value of the timeout attribute to the desired timeout (in minutes).
4. Save your changes and close the file.

More Information

A longer timeout period can lead to more simultaneous users accessing the repository. This may lead to degraded performance in WebLink as more system resources are needed for multiple users performing actions.

Please also be aware of the number of available licenses. A longer timeout period can lead to more simultaneous users each using up a license. This can lead to a scenario where all current licenses are in use and a user may be unable to log in to WebLink.