Setting the User Session Timeout Value

A session begins when a user successfully logs in to RDC. The session ends either when the user logs out or when RDC times out due to inactivity.

By default, RDC times out after 30 minutes of inactivity. However, you can change the timeout interval to another value. If a user remains inactive in a session for the specified period of time, RDC automatically times out and logs the user out of the application.

The automatic timeout provides added security to unauthorized use of the application. If a timeout occurs, RDC prompts the user to log in again.

For more information, see:

• Recommendations for Setting the Session Timeout Value
  
• Changing the Session Timeout Value
  

Recommendations for Setting the Session Timeout Value

When determining whether to increase the session timeout to more than 40 minutes, you must consider the following issues:

• High timeout values may negatively affect performance and scalability because memory usage increases as the timeout value increases. Specifically, when a session times out, the system cleans out all resources assigned to the user. Increasing the timeout value means the system continues to use resources for a longer time. However, if the number of concurrent users accessing the system is low (that is, 25–50), you may not notice that resources are used for a longer time, and therefore, you may not experience any resource problems. Furthermore, if you have correctly configured your server for the number of users accessing the system, you should not experience any problems with memory or CPU resources.
• The value for the jbo.ampool.maxinactiveage setting in the bc4j.xcfg file must be set higher than the session timeout. The default value for this setting is 60 minutes. Therefore, you must also edit the jbo.ampool.maxinactiveage setting if you set the session timeout to 120 minutes (1200000).

For additional information about the various configuration settings you can use to improve the performance of RDC, consult the following white paper on My Oracle Support:

Document Name: Oracle Clinical Remote Data Capture Onsite Browser Infrastructure Tuning Tips for Releases 5.4

Document ID: 2851842.1

Changing the Session Timeout Value

To change the timeout interval for an RDC session:

1. Stop the WebLogic Admin Server instance.
2. Log in to the RDC application server.
3. Navigate to the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa54, found under HKEY_LOCAL_MACHINE > Software > Oracle.
4. Open the RdcConfig.properties file with a text editor.
5. Find the following line and edit the value (number of minutes) to change the session timeout limit:

   rdc_session_timeout=30

   Note:

   If you set the session timeout to more than 59 minutes, you must also change the value for the jbo.ampool.maxinactiveage setting in the bc4j.xcfg file to be greater than the value of the session timeout.
6. Save your changes.
7. Restart the WebLogic Admin Server instance.