E1: JAS: AIS: LDAP: Best Practices on Setting Idle Session Timeout Values for Different Components Involved in the Communication Chain with JD Edwards EnterpriseOne
(Doc ID 2714667.1)
Last updated on NOVEMBER 09, 2020
JD Edwards EnterpriseOne Tools Information in this document applies to any platform.
This document covers how to set the idle sessions timeout values for all components involved in the communication with JD Edwards EnterpriseOne, including:
Idle session timeout for E1 HTML server (JAS server)
Idle session timeout for E1 AIS server and the back-end JAS server dedicated to AIS (for processing the UX One components)
Idle session timeout for Oracle Access Manager (in case Single Sign On with Oracle Access Manager authentication is used)
Idle session timeout for Load Balancers (in case a Load Balancer is used)
The scope of this document is to provide the information on how the idle session timeout values should be set along the communication chain from user workstation (web client) until E1 HTML server (JAS server). The values mentioned here are general recommendations and may vary from customer to customer as per their requirements. You must be familiar with Server Manager Console, Application Server Console, OAM console and Load Balancer configuration console (which is vendor specific) to make these changes.
The rule of thumb for updating the timeout values for EnterpriseOne user sessions is, the JAS.INI setting(s) for timeout should be set to the lowest value compared with the timeout setting defined for all other components involved in the communication from web client to EnterpriseOne HTML server (JAS server). This is to avoid any record locking.
It is important to note that you should not set User Session timeout in JAS.INI to a very high value (over 60) as this may affect the performance of the system.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!