The Clone Environment feature is a screen-based way to clone an environment and, optionally, identity domain artifacts (users and predefined roles). It is an alternative to writing an EPM Automate script to perform this operation.
Supported Cloning Scenarios
Cloning of environment is useful in migration scenarios, including the following:
- Production to test cloning
- Test to production cloning
Which Snapshot Can be Cloned?
This feature uses the current snapshot, named
Artifact Snapshot, created by the last daily maintenance.
If changes you made to the environment after the last daily maintenance must be present in the snapshot being cloned, run the runDailyMaintenance
EPM Automate command to regenerate
Handling Essbase Version During CloningIf there is a mismatch between the Essbase version in the source and target environment, the cloning process will change the Essbase version in the target environment to match that of the source environment.
Specifically, if the source environment uses Hybrid-enabled Essbase version while the target environment uses Non-Hybrid Essbase, the cloning process will update the target environment to use Hybrid-enabled Essbase. Conversely, if the source environment has Non-Hybrid Essbase and the target environment has Hybrid-enabled Essbase, the clone process updates the target environment to use the Essbase version that does not support Hybrid cubes.
Cloning of environments fails in these scenarios:
- Source is a legacy environment with Non-Hybrid Essbase and the target is an EPM Enterprise Cloud Service environment in which the Essbase version was downgraded to Non-Hybrid Essbase.
- Source is an EPM Enterprise Cloud Service environment Hybrid-enabled Essbase and the target is a legacy environment in which the Essbase version was upgraded to Hybrid-enabled Essbase.
When you clone an environment, Oracle Enterprise Performance Management Cloud automatically completes all the actions required to create an exact copy of the current application in a target environment. You may need to prepare the target environment before initiating this process, which may take some time to complete. Some considerations include the following:
- Creating and archiving the latest backup snapshot of the target environment. The cloning process does not delete existing snapshots or the files in the inbox and outbox of the target environment.
Artifact Snapshotexists in the target environment, the clone process renames it as
Artifact Snapshot_DATE_TIME; for example,
- Initiate the cloning process after the scheduled daily maintenance of the source and target environments. Be sure to allow sufficient time for the process to complete.
- The daily maintenance start time of the target environment is automatically reset to that of the source environment from which the snapshot was cloned. Use the setDailyMaintenanceStartTime EPM Automate command or the instructions in " Setting Service Maintenance Time " in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators to reset the maintenance start time of the target environment as desired.
Cloning of environments can be performed only by Service Administrators.
While cloning an environment, you have these options depending on the predefined role of the user account specified for the target environment:
Table 3-1 Available Clone Environment Options
|Predefined Role in the Target Environment||Available Clone Options|
|Service Administrator||Clone the application artifacts. Cannot clone users and predefined roles.|
|Service Administrator and Identity Domain Administrator||Clone the application artifacts, and, optionally, clone users and predefined roles.|
To clone an environment:
- Sign in to the environment that you want to clone. You should sign in as a Service Administrator or as a Service Administrator, who also has the Identity Domain Administrator predefined role.
Complete a step:
Planning, Financial Consolidation and Close, Tax Reporting, and Account Reconciliation: Click Tools, and then Clone Environment.Narrative Reporting only: Click Appearance, and then Clone Environment.Profitability and Cost Management only: Click Application, and then Clone Environment.
In Target URL, enter the URL of the environment that will become the cloned environment; for example,
- In Username, enter the user name of a Service Administrator who may also have the Identity Domain Administrator predefined role.
- In Password, enter the password of the user specified in Username.
Optional: Select the Users and Predefined Roles check box to clone users and their assigned predefined roles to the target environment.
Cloning of users and roles works only if, in Username, you specified the user name of a Service Administrator who also has the Identity Domain Administrator role in the target environment.
- Click Clone to initiate the process.