Running the estate design workshop

Who is in the room. The person who owns the organization's Oracle relationship. Someone from information security. Someone who can speak to data residency obligations. The identity or directory team. Not the EPM functional consultants. This is not their decision, and their presence usually pulls it toward business-process thinking — which is exactly the thinking that produces a domain per business process. Open with obligations, not architecture. "What are we legally required to do about where this data lives and who can reach it?" Everything else derives from the answer. The question sequence. One. Do you have an existing Oracle cloud account, and who administers it? Two. Are there data residency obligations, and written where? Three. Does your security policy require non-production identity to be separated from production? Four. Which identity provider does the organization use, and will EPM federate to it? Five. Who will administer identity for this estate,…

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