MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 4 · Creating and Managing Environments

What an environment is

Lesson 41 of 201 · 1 min

An environment is an instance of Cloud EPM or Cloud EDM. It hosts one business process, has its own URL, its own data, its own maintenance window and its own backup. What it inherits from Module 3: its identity domain, its region, its compartment, its cloud account. What it owns itself: the application, the data, the appearance, the maintenance schedule, the snapshots. ONE ENVIRONMENT, ONE BUSINESS PROCESS. Third appearance in this course, deliberately. It is the fact that determines estate size — and therefore workload — so it is the fact worth over-teaching. And what "creating an environment" actually gives you: an empty instance. The business process comes in Module 5. One thing to carry forward: an environment's name is in its URL forever. Lesson 5 covers what that means, and by then it will be too late to change it, which is why it is being said now.

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, 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 · Creating and Managing Environments

  1. 1What an environment is
  2. 2Test and production
  3. 3Creating an environment
  4. 4Viewing and documenting the estate
  5. 5URL patterns: classic and OCIFree preview
  6. 6Vanity URLs
  7. 7Granting console access to service administrators
  8. 8Retiring environments
  9. 9What breaks
  10. 10Lab: build the estate and give it a register