What sits between the user and EBS

Browser, web server, managed servers, and the application. WHERE A REQUEST GOES and WHERE IT CAN STOP. Between a click and a row in the database there are five or six components, and almost every diagnosis in this module is about establishing how far the request got. THE BROWSER SENDS THE REQUEST, WHICH REACHES A LOAD BALANCER IF THERE IS ONE — Lesson 8, and whether one exists changes what "some users are affected" means. THE WEB SERVER TAKES IT NEXT AND DECIDES WHAT TO DO WITH IT. Static content it serves itself; anything else it forwards inward. So a failure here is total — nothing loads at all, which is the loudest and easiest case. THE MANAGED SERVERS ARE WHERE THE APPLICATION ACTUALLY RUNS, and there are several, each responsible for a different part — Lesson 2. Which is why failures here are PARTIAL: one part of the system…

In this module: Module 10 · WebLogic and the technology stack

1. 1What sits between the user and EBS
2. 2The admin server and the managed servers
3. 3Starting, stopping and the order
4. 4Reading a WebLogic log
5. 5Memory, and the server that keeps restarting
6. 6Certificates and HTTPS
7. 7Java versions and the technology stack
8. 8The load balancer, and who owns it
9. 9What breaks: three technology stack failures
10. 10Lab briefing · Follow one request all the way down