MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 10 · WebLogic and the technology stack

Lab briefing · Follow one request all the way down

Lesson 111 of 184 · 2 min

From a click to a database session and back, NAMING EVERY COMPONENT IT PASSED THROUGH and HOW YOU WOULD CHECK EACH ONE. The naming is the exercise, and it is harder than it sounds because most people can describe the stack in general and cannot say what it is on THIS estate. DO IT ON YOUR OWN SYSTEM AND WRITE THE ACTUAL VALUES, NOT THE GENERIC SHAPE. Which host the browser resolves to. Whether a load balancer is in the path and which nodes are in its pool — Module 2 Lesson 9's surprise, answered before it matters. The web server on each node, the managed server that serves this particular screen, and the database session underneath it. THEN, FOR EACH COMPONENT, WRITE THE ONE COMMAND OR ONE CHECK THAT ANSWERS "IS THIS WORKING". That column is the deliverable. Not "check WebLogic" but the exact way you would check this

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

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