MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 16 · Environment management: P2T, refreshes and what breaks

Preserving configuration across a refresh

Lesson 159 of 177 · 2 min

Configuration packages capture a great deal and not everything, and the gap is what has to be reapplied by hand. What packages generally capture: setup data defined through the setup tasks — the structured, exportable configuration the tooling knows about. WHAT MUST BE REAPPLIED BY HAND, because nothing captures it. Role assignments made in the target. Scheduled job definitions and their schedules, which is why a refresh silently stops a set of nightly jobs. Integration endpoints and credentials — Lesson 6, and the most urgent of these. Personalisations and sandboxes. And anything set through a screen that is not a setup task, which is a longer list than anybody expects and differs by module. THE PRACTICAL METHOD IS TO KEEP A "REAPPLY" LIST PER ENVIRONMENT, MAINTAINED AS YOU GO. Every time you configure something in test that did not come from a package, add a line. Written after the fact,…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, 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 16 · Environment management: P2T, refreshes and what breaks

  1. 1The environments, and what each is for
  2. 2What a P2T actually copies
  3. 3The checklist before anybody clicksFree preview
  4. 4Data masking and why it is not optional
  5. 5Preserving configuration across a refresh
  6. 6Integrations after a refresh
  7. 7Scheduling refreshes around a project
  8. 8What breaks: four refresh failures
  9. 9Lab briefing · Plan a refresh you could defend