HTML servers, which are technically Java Application Servers (JAS), are usually the final step in presenting a user the Oracle JD Edwards EnterpriseOne graphical user interface. Before it gets to that point, there are several steps that need to happen, depending on the page or application that is being accessed. For pages like the JDE E1 homepage or custom JDE E1 pages and applications like the Address Book or Purchase Order Inquiry, there may be calls to the AIS server for display items like Notifications, WatchLists, or Composite Pages. However, for more complicated applications like the Work Center Load Review Calendar, displaying the page to the user involves calls to the Application Interface Services (AIS) server as well as the Application Development Framework (ADF) server.
The relationship between HTML servers, ADF servers, and AIS servers is a delicate one. They depend on each other for the successful operation of user experience functions as well as daily tasks. One of the settings that is important to get correct is the timeout setting. Each server has its own timeout setting to maintain healthy connections between sessions. To ensure that the AIS and/or ADF resources are available to the HTML server when they are called upon, there needs to be some thought put into their configuration.
The general rule that can be used for the successful relationship between these servers is that the session timeout settings of the HTML server need to be less than the session timeout settings on the ADF server which need to be less than the session timeout settings on the AIS server:
HTML < ADF < AIS
The example below is for a user session timeout of one hour:
- HTML Server:
- Setting location from the Server Management Console: Server Manager > Cache > User Session Cache Timeout
- Setting location in the jas.ini
[CACHE]
UserSession=3600000 // (60 min)
- Setting location from the Server Management Console: Server Manager > Cache > User Session Cache Timeout
- ADF server:
- Setting location from the Server Management Console: Server Manager > Session > Session Timeout
- Setting location in the e1adf.ini
[SECURITY]
sessionTimeout=3900000 // (65 mins)
- Setting location from the Server Management Console: Server Manager > Session > Session Timeout
- AIS Server:
- Setting location from the Server Management Console: Server Manager > Security Information > Session Timeout
- Setting location in the rest.ini
[SECURITY]
SessionInactivityTimeoutMinutes=70 // 70 mins
- Setting location from the Server Management Console: Server Manager > Security Information > Session Timeout
For more information on AIS Session Token Life and Timeout Settings and How They Relate to HTML Timeout Settings please see Oracle Support Doc ID 2522434.1.
JDE EnterpriseOne Notifications, WatchLists, Composite Pages, etc… involve the successful operation of several different servers. Having those servers properly configured to provide a stable application environment can mean the difference between a satisfied user and frustrated user.
Syntax has over 40 years of Oracle ERP experience and over 20 years providing cloud and managed services for JD Edwards solutions. Contact us today to take full advantage of what Oracle JDE EnterpriseOne has to offer.