|
OmniRim > OmniCare Support > FAQ's
How Session Timeout Values are configured
The following outlines how to control timeout values in OmniRIM. Note: Ultimately timeout values should be set based on your own specific internal security policies.
_________________________________________________
I. INISETTINGS Table (as of OmniRIM 6.4 SP2)
The session timeout value on most screens in OmniRIM including the Home Screen are set in the INISETTINGS table in the database. The default value is 30 minutes. The value can be reset using the following query:
UPDATE INISETTINGS SET ITEMVALUE = x WHERE ITEM = 'SESSIONTIMEOUT'
Recommended setting = 1440 which allows for a daily reset.
_________________________________________________
II. global.asa
The session timeout and script timeout for more complicated functionality which require longer periods to complete are set in the global.asa file.
Session.TimeOut=1400
Server.ScriptTimeout=720
Warning: do not attempt to alter these settings without consulting OmniRIM Support.
_________________________________________________
III. Application Pool (IIS 6.0 only)
IIS 6.0 allows web application to run under Application Pools which can be controlled in various ways. Each pool runs under a separate w3wp.exe process. These processes can be set to recycle or shutdown at various times. Because OmniRIM is an in-process application its sessions will be recycled or killed with the Application Pool it is running under. Two key settings can strongly affect OmniRIM sessions:
1. Idle timeout > Shuts down worker processes after being idle for x minutes. Default value = 20 minutes.
In a multiuser environment this setting can most likely be set lower than the session timeout; however, to ensure users do not have their sessions inconveniently reset we recommend setting the value to match the session timeout used in the INISETTTINGS table (see section I. above).
Recommended setting = 1440 which allows for a daily reset.
2. Recycle worker processes > Recycles worker processes after x minutes. Default value = 1740 minutes.
By default, the WWW service establishes an overlapped recycle, in which the worker process that is to be shut down is kept running until after a new worker process is started. This overlap methodology means users will not notice a session timeout. Note that overlapping can be turned off by setting the 'DisallowOverlappingRotation' metabase property to true. This property should be verified if users are experiencing strange session timeouts
As well, setting the recycling to occur too often may reduce performance.
3. Web gardens > In worker process isolation mode, you can configure an application pool to be supported by multiple worker processes. An application pool that uses more than one worker process is called a Web garden. (Web gardens are to be distinguished from Web farms, which use multiple servers for a Web site.) Note OmniRIM requires the Maximum number of worker processes = 1. Setting this value greater than 1 will either disable the application or result in unpredicatable session timeouts.
To access the Application Pool settings:
1. Open the IIS Mangement Console by clicking Start > Run
2. Type 'inetmgr'. Then click OK.
2. Under Web Sites locate the OmniRIM Web Site or Virtual Directory.
3. Right-click on the OmniRIM site and bring up properties
4. on the Home Directory tab (web site) or the Virtual Directory tab (Virtual Directory) check the Application pool setting and note the Application Pool OmniRIM is running under
5. expand the appropriate Application Pool and right-click on it to bring up properties
_________________________________________________
IV. How to set timeout values in IIS
OmniRIM mostly overrides the session.timeout and script.timeout values set in IIS. However some functionality do rely on the IIS settings. To set these values in IIS follow the instructions below.
Accessing the IIS Management Console:
1. On the web server click Start > Run
2. Type 'inetmgr' and click the OK button
Virtual Directory:
By default OmniRIM is created as virtual directory named 'omniweb' under the Default Web Site. To change timeout values for a virtual directory:
1. Right-click on the virtual directory and select Properties
2. Select the Virtual Directory tab
3. Click the Configuration button
4. On the Application Configuration dialog select the Options tab
5. The default Session timeout is 20 minutes. The recommended timeout is 20 minutes. It can be increased to a maximum of 2000000000 minutes.
6. The default ASP script timeout is 90 seconds. The recommended timeout is 720 seconds. It can be increased to a maximum of 2000000000 seconds.
7. Reset the values you wish to change then click OK to exit the Application Configuration dialog
8. Click OK again to exit the Property dialog
Web Site
If you have manually set up OmniRIM as a web site, perform the following to change the timeout values:
1. Right-click on the web site and select Properties
2. Select the Home Directory tab
3. Click the Configuration button
4. On the Application Configuration dialog select the Options tab
5. The default Session timeout is 20 minutes. The recommended timeout is 20 minutes. It can be increased to a maximum of 2000000000 minutes.
6. The default ASP script timeout is 90 seconds. The recommended timeout is 720 seconds. It can be increased to a maximum of 2000000000 seconds.
7. Reset the values you wish to change then click OK to exit the Application Configuration dialog
8. Click OK again to exit the Property dialog
For more information on Application Pools in IIS 6.0, refer to the following Microsoft TechNet article:
http://www.microsoft.com/technet/technetmag/issues/2006/01/ServingTheWeb/
|
