PBCS : Pod Naming Conventions
(Doc ID 2783664.1)
Last updated on NOVEMBER 03, 2022
Applies to:
Oracle Enterprise Planning and Budgeting Cloud Service - Version 20.09.56 and laterInformation in this document applies to any platform.
Goal
The following list highlights the initial naming convention that was decided for all 12 Pods of the EPM system. There will be 4 Pods- Dev, Test, Training and Production- for each application (Planning, PCM and EDM).
Planning: epmpln-dev | epmpln-test | epmpln-train | epmpln
PCM: epmpcm-dev | epmpcm-test | epmpcm-train | epmpcm
EDM: epmedm-dev | epmedm-test | epmedm-train | epmedm
This would require an additional "-train" and "-dev" for the training and development pods. Is there a way to establish these names?
One workaround identified would be to create all pods with their own "test" pod, and disable them (keep as inactive).
Another workaround would require eliminating hyphens, but potentially keeping the rest of the naming convention the same.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |