Adjusting Session & HTTP Request Timeouts Whitepaper

An Oracle White Paper

January 2014

Introduced in Release 6.1.1

E50734-02

Adjusting Session and HTTP Request Timeouts

Table of Contents

Table of Contents .............................................................................. 1

Overview ........................................................................................... 2

HTTP Request Time-out .................................................................... 2

Session Time-out .............................................................................. 3

Overview

This whitepaper discusses two possible configuration changes for Oracle Agile PLM for Process. It is valid for releases 6.1.1 and earlier.

1. HTTP Request Time-out

If page requests are timing out, this could indicate a performance issue. This could be due to a variety of reasons, some being: hardware is not sized appropriately to handle the user load, database indexes are needed, or there can be a defect. If changes to the environment are unable to resolve the issue, increasing the ‘HTTP Request Time-out’ value is possible. This will allow the user to complete their task and help determine if it is a defect.

2. Session Time-out

When a logged in user is inactive for a certain period of time (20 minutes by default), they will be presented with a warning message informing them that their session will expire. If not acted upon, the user will receive a message that their session has expired. The user will then need to re-login. The maximum inactive time for the user’s session or the timing when the messages are presented, are configurable.

HTTP Request Timeout

In order to increase the timeout for a page request, you may adjust the httpRuntime executionTimeout config value in the <system.web> node of machine.config or web.config.

<system.web>

If you want to increase the timeout for all Oracle Agile PLM for Process applications running on the server, you can modify machine.config. This will either be ‘%WINDIR%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config’ or ‘%WINDIR%\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config’ depending on your Oracle Agile PLM for Process deployment.

If you want to increase the timeout for a single Oracle Agile PLM for Process application, you can modify the web.config located in ‘PLM4P_HOME\web\<app>\’.

Session Time-out

In order to increase the session timeout for inactive users, please make the following modifications.

$Text Box: NAME DESCRIPTION IIS App Pool Idle Timeout IIS/App Pool/Advanced Settings/ Process Model/Idle Timeout = {Minutes} This controls the Worker Process where the session is stored. Set to 0 for unlimited. IIS Cookie Setting Timeout IIS/Site/Session State/Cookie Settings/Timeout(minutes) = {Minutes} Controls timeout setting of cookie which holds the authentication data Session Timeout Machine.Config <system.web> <sessionState timeout="{Minutes}" /> Timeout value for the actual session Warning Messages DeployedConfig.config This needs to be added to the %CONFIG_HOME%\DeployedConfig.config file under <DeployedConfig> <Core>: <Timeouts configExtends= "file:%CONFIG_HOME%\Core\CoreAppSettings.config,CoreAppSettings/ProdikaSettings/Timeouts" configExtends2="file:%CONFIG_HOME%\Custom\CustomerSettings.config,CustomerSettings/Core/ProdikaSettings/Timeouts"/> CustomerSettings.config Add the Timeouts section to %CONFIG_HOME%\Custom\CustomerSettings.config under <CustomerSettings>/<ProdikaSettings> with the appropriate values for the timeouts: <Timeouts configChildKey="key" > <add key="SessionTimeout" value="{Milliseconds}"/> <add key="AuthenticationTimeout" value="{Milliseconds}"/> <add key="ForeWarning" value="{Milliseconds}"/> <add key="CheckFrequency" value="{Milliseconds}"/> </Timeouts> This controls the JavaScript pop-ups. § SessionTimeout – Number of milliseconds after page opens until user receives message: 'The session has ended.' § ForeWarning – User will receive message this number of milliseconds prior to SessionTimeout value: 'Session will timeout, causing loss of any unsaved data.' The user will receive a message this many milliseconds after page opens: SessionTimeout- ForeWarning NAME DESCRIPTION § AuthenticationTimeout - User will receive message this number of milliseconds prior to SessionTimeout value: 'You will need to reauthenticate.' § CheckFrequency – Frequency at which the above warnings are checked These values do not actually control the session duration. They should be set up so they are in sync with the actual session expiration.$