Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack
Java versions and the technology stack
Lesson 108 of 184 · 3 min
What EBS mandates, how to check what you have, and THE UPGRADE THAT BROKE FORMS FOR A WHOLE DEPARTMENT. EBS is certified against specific versions of the software underneath it, and "certified" means tested rather than recommended. Running something else may work perfectly and is unsupported — which matters most at the moment you have a problem and need help. SO CHECK WHAT YOU HAVE RATHER THAN WHAT WAS INSTALLED. Java, the middleware, the database, the operating system — each has a version, and each may have been updated by somebody who was not thinking about EBS at all. That is the whole mechanism of the failure in the title. THE UPGRADE THAT BROKE FORMS IS ALMOST ALWAYS A CLIENT-SIDE JAVA UPDATE, AND NOBODY INVOLVED DID ANYTHING WRONG. A desktop team rolled out a security update, correctly and on policy. The professional interface depends on Java in the browser, so…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 10 · WebLogic and the technology stack
- 1What sits between the user and EBS
- 2The admin server and the managed servers
- 3Starting, stopping and the order
- 4Reading a WebLogic log
- 5Memory, and the server that keeps restarting
- 6Certificates and HTTPS
- 7Java versions and the technology stack
- 8The load balancer, and who owns it
- 9What breaks: three technology stack failures
- 10Lab briefing · Follow one request all the way down
