MSAMM
Back to course

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

Custom top, and where your code belongs

Lesson 41 of 184 · 3 min

The convention that keeps customisations SURVIVING A PATCH, and what happens to code that ignored it. EBS reserves a place for your organisation's own code — a custom top — and it exists for one reason: patches replace Oracle's directories and do not touch yours. SO THE RULE IS SIMPLE AND ABSOLUTE: CUSTOM CODE GOES IN THE CUSTOM TOP, NEVER IN A PRODUCT DIRECTORY. A custom report, a custom package, a modified copy of a standard object — all of it belongs in your own tree, registered so the application can find it. WHAT HAPPENS TO CODE THAT IGNORED IT IS EXACTLY WHAT YOU WOULD EXPECT AND ARRIVES LATER THAN YOU WOULD EXPECT. It works, indefinitely, until a patch touches that product. Then the file is overwritten and the customisation is gone — not corrupted, not flagged: replaced by Oracle's version, silently, during a successful patch. AND THE DELAY IS…

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.

See the course and enrol9 free lessons

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