Oracle Apps DBA: Keeping E-Business Suite Alive · Module 2 · The stack you are responsible for
AutoConfig, and what it overwrites
Lesson 18 of 184 · 3 min
What it regenerates, in what order, and THE CUSTOMISATION THAT VANISHED because somebody put it in the wrong place. AutoConfig reads the context file and regenerates the configuration across the instance — environment files, server configuration, scripts, and the settings each component reads at startup. It runs on both tiers, and it is what makes a change to the context file take effect. IT REGENERATES FROM TEMPLATES, WHICH IS THE MECHANISM THAT MATTERS. Each generated file has a template behind it, and AutoConfig fills the template with values from the context file. So anything not in a template and not in the context file cannot survive — not because AutoConfig is destructive, but because it is producing the file from scratch and your addition is not part of the recipe. THAT IS THE VANISHED CUSTOMISATION, AND IT IS ALMOST ALWAYS SOMETHING REASONABLE. A line added to an environment file. A…
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 2 · The stack you are responsible for
- 1The two tiers, and why the split matters
- 2What is running right now
- 3The file system layout
- 4Environment files, and sourcing the right one
- 5The context file
- 6AutoConfig, and what it overwrites
- 7Ports, and the ones you will be asked about
- 8Logs: where they are and which one to open first
- 9What breaks: three architecture surprises
- 10Lab briefing · Map a running instance