Four worked estate structures

Four scenarios, and they get harder. One. Single-country organization, one business process, test and production. One cloud account, one identity domain, one region, two environments. The base case — shown to make the point that simple is correct when the facts are simple. There is no credit for complexity. Two. Multi-business-process finance estate, one country. One domain, six environments, one region. Which demonstrates the thing people most often get wrong: more environments does not mean more domains. Three. Multinational with a residency constraint. Two regions, because the law says so. And then the identity question that follows: one domain spanning both, or one per region? This is the genuinely hard one, and it is worked properly rather than asserted. Four. An organization with an existing Oracle estate. EPM joining a cloud account that already hosts other Oracle services — the identity federation opportunity, the governance complication, and the question of…

In this module: Module 3 · Cloud Account, Identity Domains and Regions

1. 1What we are building
2. 2The decisions you cannot undo
3. 3The identity object model
4. 4Identity domains — the central decision
5. 5Regions and data residency
6. 6Compartments
7. 7Running the estate design workshop
8. 8Four worked estate structures
9. 9Activating: creating a new cloud account
10. 10Activating: adding to an existing account
11. 11Touring the Oracle Cloud Console
12. 12Enabling multifactor authentication
13. 13Subscribing to and replicating regions
14. 14Creating a compartment
15. 15Creating an identity domain
16. 16Identity domain administrators
17. 17What breaks
18. 18Lab briefing: Northwind Group
19. 19Lab solution walkthrough