Overview

Timeout settings determine the period after which a session would expire. The inactivity timeout option in Gemini is a profile option in Oracle Applications named BPA: Inactivity Timeout. This profile option value is set in minutes. This value will apply to Gemini sessions started after this profile option has been saved. 

This article is intended for system admin and support technicians configuring or troubleshooting idle or inactivity timeouts in Gemini environment.

Note: The following settings are intended to be used as an example only.

Information

If we set the BPA Inactivity Timeout to 15 minutes in Oracle, we would want the RFUI timeout to be 30 minutes = 1800 seconds. Basically, Oracle timeout should be 15 minutes less than RFUI. 

• Oracle Profile: For Inactivity Timeout search for the profile option BPA: Inactivity Timeout in Oracle Apps. BPA: Inactivity Timeout to 15---this equals minutes 
  
  
• RFUIServer: For Inactivity Timeout in the rfuiserver.ksh, add setting: RFUI_ARGS:"-timeout # of seconds". Set the RFUI_ARGS="-timeout 1800---this equals seconds.

BPA: Inactivity Timeout 
Automatically logs out a user after a specified period of inactivity. Valid values are numeric, in minutes. If this profile option is set to zero or NULL, no timeout occurs. To use this profile, you must have Connect v2.5 or later installed. 

RFUIServer: 
The inactivity timeout option is configured by editing the rfuiserver.ksh file, and then restarting the RFUIServer. 

ADMIN_PORT=6003 
MIN_MEMORY=-Xms64m 
MAX_MEMORY=-Xmx128m 
PROGRAM="main" 
# Add any extra command line arguments here, i.e. inactivity timeout, etc. 
RFUI_ARGS="-timeout 1800" # where 1800 is in seconds. 

Issues pertaining to RFUI Server timing out and database connection not closing properly will get resolved once the Inactivity Timeouts have been configured correctly.