MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 16 · Environments: what test must not have

Access, per environment

Lesson 167 of 184 · 3 min

Who may reach which, and why DEVELOPER ACCESS TO PRODUCTION is the request that needs A WRITTEN ANSWER. Access should differ by environment, and in most estates it does not — which means the environments are separate in name and not in exposure. THE PRINCIPLE IS THAT ACCESS SHOULD MATCH WHAT THE ENVIRONMENT IS FOR. Development is where things are built, so developers need broad access there and it costs nothing. Production is where the business runs, so access is narrow and every grant is a decision. AND THE PART PEOPLE MISS IS THAT TEST AND TRAINING HOLD PRODUCTION'S DATA. Lesson 2's third item — so "it is only test" is a statement about the system's purpose rather than about what it contains. Broad access to an unmasked test environment is broad access to every salary in the business, arrived at without anybody deciding it. DEVELOPER ACCESS TO PRODUCTION 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.

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 · Environments: what test must not have

  1. 1How many environments, and why
  2. 2What test must not haveFree preview
  3. 3Masking, and its limits
  4. 4Refresh cadence, and who decides
  5. 5Keeping environments comparable
  6. 6Access, per environment
  7. 7Documenting an estate
  8. 8What breaks: three environment failures
  9. 9Lab briefing · Write the handover pack
Access, per environment — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM