Post-Cloning Environment Tasks

Limit Access to Source Environment

After cloning, you should consider allowing only one or two users to access the source environment and consider disabling the rest of the users.

Notify NetSuite EPM Cloud users of the new URLs of the cloned environment

Notify the NetSuite EPM Cloud users of the new URLs of the cloned environment:

• The URL to access the NetSuite EPM Cloud environment. For more information about these unique URLs, see Sample EPM Cloud URLs in the Oracle Help Center.

• The URLs to establish the public and private Oracle Smart View for Office connections to the 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. You must modify these values:

• The URL of the environment.

• The Password of the user if the password is different in the cloned environment.

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 in the cloned environment. This update may be required because the internal IDs of objects (such as tasks, Journals, and Attributes) may change during the migration.

Applies to: NetSuite Planning and Budgeting, NetSuite Tax Reporting, and NetSuite Close Management and Consolidation.

Update Smart View URLs

Update the following Smart View URLs:

• Modify the public and private connection Smart View URLs so that they point to the cloned environment. See URL Syntax for Smart View Connections in the Oracle Help Center.

• Update connection URLS, as needed. See About Managing Connection URL Mappings and Updating Connection URL Mappings in the Oracle Help Center.

Create New Vanity URLs

If your users use a vanity URL to connect to the environments, then create a new vanity URL. Alternatively, update the existing one to point to the URL of the cloned environment. See Using Vanity URLs in the Oracle Help Center.

Update Bookmarks

Remind users to change their bookmarks so that the bookmarks direct to the cloned environment.

Set Up Connection Between NetSuite and Target Environment

If you move many instances in an integrated business process to a new domain, please note that Single Sign On (SSO) will not work until all instances are migrated.

If you previously configured NetSuite to run jobs through the NetSuite interface, you must configure the connection to direct to the new target environment. For more information, see the following help topics:

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.

Reconfigure SSO for Target Environment

If you previously set up Single Sign-On (SSO) to authenticate users in the source environment, then configure SSO in the new target environment. This action is required to ensure that users can log in. For more information, see Configuring Single Sign-On in the Oracle Help Center.

Reconfigure IP Allowlist

If you meet any of the following conditions, you must reconfigure the IP allowlists for your OCI environments by using the setIPAllowlist EPM Automate command:

• You are migrating to OCI environments.

• You have either not configured the IP allowlists as a prerequisite before cloning or would like to make changes to the configuration after cloning.

For detailed information about how to use this EPM Automand command, see the help topic setIPAllowlist in the Oracle Help Center.

Update IP address

You must update your IP address if you used the IP address of the source NetSuite EPM Cloud environment anywhere. For example, you have added it in your proxy configuration as an allowed outgoing IP address. You can find the IP address of the target environment by using nslookup. Alternatively, ping the IP address and update it.

Related Topics