Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack
The load balancer, and who owns it
Lesson 109 of 184 · 2 min
What it changes about diagnosis, and THE QUESTION TO ASK THE NETWORK TEAM when ONLY SOME USERS ARE AFFECTED. A load balancer sits in front of the application tier and distributes requests across nodes, and it changes diagnosis in one specific and important way. IT MAKES "SOME USERS ARE AFFECTED" A DIFFERENT SENTENCE FROM WHAT IT USUALLY MEANS. Without one, a partial symptom points at a specific population — a department, a responsibility, a browser. With one, it may simply mean that half the traffic is going to a node that is unwell, and the affected users have nothing in common at all except which node they happened to reach. THE TELL IS EXACTLY THAT: THE AFFECTED USERS HAVE NO COMMON PROPERTY, AND THE SAME PERSON MAY BE FINE ON A SECOND ATTEMPT. One node is broken, the balancer keeps sending a share of traffic to it, and the experience…
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