Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack
Certificates and HTTPS
Lesson 107 of 184 · 2 min
Where the certificate lives, how to replace it, and THE EXPIRY DATE THAT WILL TAKE THE SYSTEM DOWN ON A DAY YOU CAN PREDICT TODAY. The certificate that secures the login page is the most predictable outage an EBS estate has, and it is entirely preventable. ON THE EXPIRY DATE, EVERY BROWSER REFUSES OR WARNS. Modern browsers do not offer a way past it for most users, so the practical effect is a total outage — and the system itself is perfectly healthy, which makes every internal check say the estate is fine. THE CONFUSING PART IS THAT SOME PEOPLE STILL GET IN. An open session continues; an internal integration that skips validation keeps working. So the report is "most people cannot log in" rather than "the system is down", which does not sound like a certificate. WHERE IT LIVES DEPENDS ON WHERE TLS TERMINATES, AND THAT IS THE FIRST…
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