Tasks to Perform After Cloning Environments

If you are no longer going to use the source environment after completing the cloning process, you need to perform some steps to ensure that your URLs, scripts, bookmarks, and so on set for the source environment work seamlessly for the cloned environment. You must complete the following for a smooth transition if you are migrating from Oracle Cloud Classic to OCI.

Announce the URL of the Environment to EPM Cloud Users

Service Administrators should notify Oracle Enterprise Performance Management Cloud users of the new URL of the environment, including the following:

• URL to access the environment See Sample EPM Cloud URLs in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.
• URLs to establish public and private Oracle Smart View for Office connections to the environment

In Oracle Cloud Classic to OCI cloning, the user names of EPM Cloud users remains the same as those in the source environment.

Modify EPM Automate and REST API Scripts

Modify the EPM Automate and REST API scripts that you plan to run against the cloned environment. These values must be modified:

• URL of the environment.
• Identity domain of the environment (you do not need to specify identity domain for OCI environments; it is optional for Oracle Cloud Classic environments).
• Password of the user if the password is different in the cloned environment.

Optionally Update Task Manager, Supplemental Data Manager, and Enterprise Journal Custom Report Queries

If required, update Task Manager, Supplemental Data Manager, and Enterprise Journal custom report queries, if any, in the cloned OCI environment. This update may be required because the internal IDs of objects such as tasks, Journals, and Attributes may change during the migration. This update may be required for cloned Planning, Planning Modules, Tax Reporting, and Financial Consolidation and Close environments.

Note:

Oracle-managed migration does not result in any change to the internal object IDs.

Update 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. See these information sources:.

• URL Syntax for Smart View Connections in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators
• "About Managing Connection URL Mappings" and "Updating Connection URL Mappings" in Oracle Smart View for Office User's Guide

Create New Vanity URLs

If your users use vanity URL to connect to the environments, create a new vanity URL or update the existing one to point to the URL of the cloned environment. See Using Vanity URLs in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

Change Bookmarks

Remind users to modify their bookmarks so that they point to the cloned environment.

Modify Integrated Business Process

Modify navigation flows by updating connections defined for integrated business processes to integrate the cloned environment into navigation flows.

Note:

If you are moving multiple instances in an integrated business process to a new domain, Single Sign On (SSO) between instances will not work until all instances are migrated.

Setup SSO

If you had setup SSO to authenticate the users and the migration resulted in a change in the identity domain being used, then you must reconfigure SSO. See Configuring Single Sign-On in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

Note:

You need not reconfigure SSO if you have done that as a prerequisite before cloning.

Reconfigure IP Allowlist

In the following conditions, you must reconfigure IP allowlists for your OCI environments using setIPAllowlist EPM Automate command. See Setting up Secure Access in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators:

• You are migrating to OCI environments
• You had setup IP allowlists for your Oracle Cloud Classic environments on the Service Details screen of My Services
• You have either not configured IP allowlists as a prerequisite before cloning or would like to make changes to the configuration after cloning

Reconfigure Integration Agent

Update the configuration for the Integration Agent to ensure that the cloned environment is properly integrated with it.

Update Integration with Other Services

If your source environment was integrated with other services, review the integration settings to ensure that the cloned environment is properly integrated with them.

Update IP Addresses

Update the configuration with new IP address in these cases:

• If you are using the IP address of the source EPM Cloud environment anywhere (for example, you have added it in your proxy configuration as an allowed outgoing IP address).

  Then, find the IP address of the target environment using nslookup or ping and update.

• If you are migrating from Classic to OCI environment and have added the outbound IP address of the Classic data center in the allow list of any other environment (for example, in a Fusion ERP environment).

  Then, change the IP address to the outbound IP address of the new OCI region. To get the outbound IP address of the OCI region where your environment is, refer to Outbound IP Addresses of EPM Cloud Data Centers and Regions in Oracle Enterprise Performance Management Cloud Operations Guide