- IBM iSeries/AS400/System i
- Backup libraries and IFS directories
- Register Pristine Environment in Server Manager
- Create Server Manager Server Group for Pristine
- Upgrade Pristine
- Web Server
- Create IBM WebSphere Application Server in Server Manager
- Create IBM HTTP Server in Server Manager
- HTML landing page: update links and info
- Change DNS entries
- Copy the code used to restrict access to specified environment
- Copy images and code for custom backgrounds
- Modify the JAS.INI file to specify the correct logon logo
- Set web server to restart nightly and cleanup logs
- Verify that the server is being backed up and replicated to DR hot site
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, EnterpriseOnes 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 applications user session timeout setting. The screenshots for IBM Websphere 22.214.171.124 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 users 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
In developing the Employee Self-Service user interface without using the portal, the development team had a need to be able to print out an employee’s paystub and have it emailed to them. The email portion of the process is handled by Optio but before it gets to the Optio server, it needs to be sent to an outqueue on the Enterprise Server. Because of the flow of the UBE submission application, upon requesting the paystub (UBE) the user is presented with a printer selection verification screen. It was decided that this screen would be pretty confusing to those employees that do not use EnterpriseOne regularly. So, the developer found a way around that. She submitted the UBE using a Named Event Rule (NER).
Because of using the NER to submit the UBE, the Print Immediate parameter in the JAS.INI file doesn’t get read. This is because it is being submitted by the Enterprise Server instead of the JAS server. If the job isn’t printed, or sent to an outqueue, then the PDF never gets to the Optio server to be processed and emailed to the user.
After consulting with Oracle Support, we changed the VRVCC3 field of the F983051 to contain a ‘1’ in the record of the UBE Version that we wanted to Print Immediate. Apparently, this version Print Immediate parameter is used in the 8.12 applications but is also read in the 8.11 SP1 version.
Note: We are using 8.11 SP1 and this solution may or may not work with earlier versions.
This is not new to most larger organizations, but it’s new to us. Since it is new and there will be employees accessing EnterpriseOne who do not use it for their daily jobs, we wanted to make it look a little different.
One of the things that we wanted to change was the login screen.
The screen shot to the left is the standard login screen for EnterpriseOne 8.11 SP1 using Tools Release 126.96.36.199.
We really wanted to change the Oracle JD Edwards EnterpriseOne logo. So, I did a little checking on Oracles Support site and found Solution ID: 201052190 (requires login). This solution doesn’t specifically address the login image but it does talk about the disclaimer text at the bottom of the page. So, it gets you to the right files.
[Websphere Install Directory]installedAppsmdur-ets-ME1WEBNode01EA_JS_87.earwebclient.warshare.
That location may be different in your installation. Also, remember that this is for Tools Release 188.8.131.52. Anyway, this file has a variable in it called "companyLogoImageURL". Just point this variable to your image.
Here is the new login screen. Well, not really, but you get the idea.
I always thought that the way I had things setup wasn’t necessarily supported. You see, I use VMWare for the two IBM Websphere JAS servers in our instances. However, thanks to some insight from a fellow SysAdmin, I now know different.
So, according to this, I think my next Deployment Server upgrade will also be on VMWare.