Cloning Applications between
environments using Clone Environment option in Oracle EPM Cloud
Click on Navigate > Under Tools section > Click on
Clone Environment
Enter the details of your Target environment
where you need to clone this application
Target
environment URL, Target environment Username, Target environment Password
Roles Required
You must have
either a Service Administrator or a Service Administrator with Identity
Domain Administrator predefined role.
For Oracle Cloud
Classic to OCI cloning, you must sign in as a Service
Administrator, who also has the Identity Domain
Administrator predefined role to ensure that users and their roles are
cloned to the OCI environment.
For cloning artifacts,
you can choose the options as per your requirements
- Optional: Select the Users
and Predefined Roles check box to clone users and their
predefined role assignments.
If you are performing
an Oracle Cloud Classic to OCI migration, you must select
this check box.
- Optional: for environments other
than Oracle Enterprise Data Management Cloud and Narrative
Reporting only: Deselect the Data Management check
box if you do not want to clone Data Management records. Cloning
of Data Management records may take a long time if the staging
tables contain a very large number of records.
Clone Data Management records only
if both the source and target environments are on the same monthly update or
the target environment is one update newer than the source environment. For
example, you can clone 22.01 Data Management records to another 22.01
environment or to a 22.02 environment only.
- Optional:
for Planning, Planning Modules, Free Form, Financial
Consolidation and Close, and Tax Reporting only: Deselect
the Job Console check box if you do not want to clone Job
Console records.
- Optional:
for Planning, Planning Modules, and Free Form only: Deselect
the Application Audit check box if you do not want to
clone application audit records.
Note: Application audit data of Financial Consolidation and
Close, and Tax Reporting is, by default, included in the snapshot.
- Optional: Select the Stored
Snapshots and Files check box if you want to clone the contents
of inbox and outbox, and stored snapshots. This process may take a long
time depending on the number and size of stored snapshots and files in
inbox and outbox.
- Click Clone to
initiate the process.
Tasks to Perform
After Cloning Environments
1.
Daily Maintenance
Start Time
The daily maintenance start time of the target environment
is automatically reset to that of the source environment from which the
snapshot was cloned, ensure to change the time in the target environment
accordingly.
2.
Update EPM Automate Scripts
If you have written any script to perform an activity,
ensure the script is updated with the target environment URL with identity
domain name updated.
Also, if you are using native accounts then ensure password
is updated In the scripts.
3.
Smart View URLs
Modify the public and private connection Smart View URLs so that they point to the cloned environment.
Also, update connection URLS as needed.
4.
Integrated Business Process
a. Single
Sign On
If you are moving
multiple instances in an integrated business process to a new domain, SSO
between instances will not work until all instances are migrated.
If you had setup SSO
to authenticate the users and the migration resulted in a change in the identity domain being used, for example, after Oracle Cloud Classic to OCI migration, you must reconfigure SSO.
While cloning between
same domains SSO need not be reconfigured, instead update the PROD application in
the list.
b. Updating
Integrations and Connections details
There are places where
you need to update the connection details, like updating data management target
application connections, source system connections, ensure the URL`s, Usernames
and password are updated accordingly.
