MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities

What the application tier does

Lesson 34 of 184 · 2 min

Forms, self-service, the concurrent processing tier and the web layer. WHICH USERS NOTICE WHEN EACH ONE STOPS. The application tier is several components rather than one, and the useful way to hold them is by who complains when each fails — because that is how the problem actually arrives at you. THE WEB LAYER IS THE FRONT DOOR AND ITS FAILURE IS TOTAL. Nobody can reach anything, the login page does not load, and every user is affected simultaneously. It is the loudest failure and therefore the easiest: it is reported within a minute and there is no ambiguity about what is broken. SELF-SERVICE IS THE HTML-BASED APPLICATION AND ITS FAILURE IS PARTIAL, WHICH MAKES IT HARDER. Users can log in and some screens work while others do not. The report you get is "the system is broken" from one person and "it is fine" from the person next to

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 4 · The application tier and the AD utilities

  1. 1What the application tier does
  2. 2Starting and stopping the services
  3. 3adadmin, and what it is for
  4. 4Compiling and generating
  5. 5adctrl and the concurrent managers
  6. 6Reading an AD log
  7. 7Worker processes, and the one that failed
  8. 8Custom top, and where your code belongs
  9. 9What breaks: three application-tier failures
  10. 10Lab briefing · Operate the tier by hand