What Are The Side Effects Of Setting A Longer SessionTimeout?
(Doc ID 502080.1)
Last updated on AUGUST 28, 2023
Applies to:
Siebel CRM - Version 7.5.3 [16157] to 8.2.2 SIA[22320] [Release V7 to V8]All Platforms
Product Release: V7 (Enterprise), V8 (Enterprise)
Version: 7.5.3 [16157] to 8.2.2 SIA [22320]
Database: Any
Application Server OS: Any
Database Server OS: Any
This document was previously published as Siebel SR 38-1123825251.
Goal
Users would like to avoid having to re-login to the application after every 30mins of inactivity (their Session Timeout is set to 1800). They have expressed a desire to increase this setting to a level that ensures that the application does not timeout during work hours but alternatively employ a method of closing all sessions on a nightly basis.
The client site in question has only 20 users of which there are only 12 connected concurrently at any given time and the customer is considering increasing the SessionTimeout to 18000 which would mean only two logons required from each user per day.
The customer would like advice on the pros and cons of configuring the application as mentioned above.
=> Questions:
1. Can you please advise if this practice is supported by Siebel?
2. Can you please advise what impact this will have on the Siebel and Database Servers, if any?
3. Are there any other disadvantages apart from a potential degradation performance?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |