The EnterpriseOne Session Timeout Two-Step…Ok, Three Step
Filed under: EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), Microsoft, Oracle Server Manager, enterpriseone, oracle
We have several work areas that require a longer inactive timeout setting than the default 20 minutes (Payroll Time-entry, Fixed Asset Accounting, etc.).
Unfortunately, EnterpriseOne’s architecture does not make the process of configuring a session timeout very easy. There are three separate separate settings that need to configured correctly. Depending on your architecture that could mean three separate machines using three separate platforms. Whatever your architecture looks like there are at least three.
- The Java Application Server (JAS). No matter what flavor of JAS you are running (IBM Websphere, Oracle Application Server, BEA, etc.) you will need to configure the application’s user session timeout setting. The screenshots for IBM Websphere 6.0.2.13 are below:
- The EnterpriseOne HTML Server. This setting is in the JAS.INI under the [CACHE] stanza. The setting is in milliseconds (3600000 = 1 hour). If you are running the Oracle Server Manager for EnterpriseOne, you can find it in the “Cache Configuration section under the “Web Runtime” configuration.
- The HTTP server. The instructions for both Microsoft IIS and IBM HTTP Server follows:
- Microsoft IIS:
- Display the properties of the website that is configured to host EnterpriseOne
- On the “Website” tab, modify the “Connection Timeout” setting. Please note that this value is in seconds, not milliseconds.
- IBM HTTP Server:
- Edit the “Timeout” setting in the HTTPD.CONF file. Please note that this value is in seconds, not milliseconds.
- Microsoft IIS:
NOTE: To avoid record locking Oracle specifies to configure the system so that the JAS server will “timeout” the user’s session. To do that both the EnterpriseOne HTML Server and the HTTP server need to be set to great times than the JAS server. For example:
- To configure a timeout value of 30 minutes:
- JAS Server: 30
- EnterpriseOne HTML Server: 3600000
- HTTP Server: 3600
Current Installation
Currently, we have two installations with the following configurations:
| E1 Software | ||
| E1 Version | Tools Release | |
| InstallationA | 8.11 SP1 | 8.96.1.5 |
| InstallationB | 8.11 SP1 | 8.96.1.5 |
| Enterprise Server – IBM iSeries 550 | |||||
| OS | CPU | Disk | RAM | NIC | |
| InstallationA | V5R4 | 1.4 | 1.5TB | 25GB | 1GB |
| InstallationB | V5R4 | 0.6 | 600GB | 17GB | 1GB |
| Deployment Server – MS Windows Server 2003 | ||||
| CPU | Disk | RAM | NIC | |
| InstallationA | Dual Intel Xeon 2.8 GHz | 136 GB | 2 GB | 1 GB |
| InstallationB | Dual Intel Xeon 3.2 GHz | 136 GB | 2 GB | 1 GB |
| Java Application Server – MS Windows Server 2003 | ||||||
| CPU | Disk | RAM | NIC | JAS | HTTP | |
| InstallationA | Dual Intel Xeon 2.8 GHz | 68 GB | 2 GB | 1 GB | IBM WAS 6.0 | IBM HTTP 2.0 |
| InstallationB | Dual Intel Xeon 3.2 GHz | 68 GB | 3.2 GB | 1 GB | IBM WAS 6.0 | IBM HTTP 2.0 |
Introduction to Oracle EnterpriseOne (E1)
Technically I guess the name should be Oracle JD Edwards EnterpriseOne (E1). How’s that for a name. Anyway, the main system that I work on during the day is EnterpriseOne (E1). It is what my employer uses for their ERP (Enterprise Resource Planning – a fancy name for accounting) system.
It was originally a JD Edwards product called OneWorld (the new version of JDE’s very stable product “World”). Then JD Edwards was purchased by PeopleSoft to try and avert a take-over by Oracle and was named EnterpriseOne (E1) (combining PeopleSoft’s product name, “Enterprise”, with “OneWorld”). However, in the end, Mr. Ellison won the battle to acquire PeopleSoft, which resulted in the name JD Edwards EnterpiseOne.
Ok, enough with the name…
Currently, we have two installations with the following configurations:
.myT {font: bold 10px; border: 1px solid #000000;}
| E1 Software | ||
| E1 Version | Tools Release | |
| InstallationA | 8.11 SP1 | 8.95.P1 |
| InstallationB | 8.11 SP1 | 8.95.P1 |
| Enterprise Server – IBM iSeries 550 | |||||
| OS | CPU | Disk | RAM | NIC | |
| InstallationA | V5R3 | 1.4 | 1.5TB | 25GB | 1GB |
| InstallationB | V5R3 | 0.6 | 600GB | 17GB | 1GB |
| Deployment Server – MS Windows Server 2003 | ||||
| CPU | Disk | RAM | NIC | |
| InstallationA | Dual Intel Xeon 2.8 GHz | 136 GB | 2 GB | 1 GB |
| InstallationB | Dual Intel Xeon 3.2 GHz | 136 GB | 2 GB | 1 GB |
| Java Application Server – MS Windows Server 2003 | ||||||
| CPU | Disk | RAM | NIC | JAS | HTTP | |
| InstallationA | Dual Intel Xeon 2.8 GHz | 68 GB | 2 GB | 1 GB | IBM WAS 5.0.2 | IBM HTTP 2.0 |
| InstallationB | Dual Intel Xeon 3.2 GHz | 68 GB | 3.2 GB | 1 GB | IBM WAS 5.0.2 | IBM HTTP 2.0 |
Although 70-270 or 646-204 is not a prerequisite in 70-620 or the proceeding advanced exams like 220-601 and 70-649, but eventually one suffers because of ill preparation in SY0-101.
Tags: e1, enterpriseone, EnterpriseOne - General, esu, ibm, iseries, jas, java application server, jd edwards, jde, oneworld, oracle, oracle enterpriseone, peoplesoft, Tools Release, version, world, xe
