Siebel Timeout Is Not Working in IP17 After Changing the Active Session Timeout Parameter
Last updated on FEBRUARY 22, 2018
Applies to:Siebel CRM - Version 17.4 [IP2017] and later
Information in this document applies to any platform.
In Siebel IP17, the Active Session Timeout Value (seconds) was changed from 900s to 9000s in the application interface profile in SMC and the profile was deployed accordingly.
The sessions are not timing out and it looks like the Active Session Timeout is still set to 900 seconds.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms