URL patterns: classic and OCI

You will be sent URLs by users, consultants and support. Being able to read one tells you which environment, which account, which region, and which generation of platform you are looking at. The OCI pattern, component by component. Instance name. Cloud account name. Service. Data centre region. Domain. Application context. And the part to burn in. Test environments are distinguished by a suffix on the instance name. THIS IS HOW YOU TELL, AT A GLANCE, WHETHER SOMEBODY IS ABOUT TO DO SOMETHING TO PRODUCTION. The classic pattern, and its components: instance name, identity domain, family, data centre region. Some customers remain on the predecessor platform, so you will meet both. The application context. Legacy contexts still work; a unified context exists. Updating is optional. Know both, so you can read old bookmarks and old documentation. Per-business-process variations for private client connections — flagged here, built in Module 10. BEFORE YOU…

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