OCI Gen2 Migration for EPM cloud
Over time, by end of 2023, Oracle plans to migrate all EPM Cloud instances in Classic commercial data centres to OCI.
All EPM cloud instances include new orders of EPM Standard Cloud Service and EPM Enterprise Cloud Service from commercial customers with existing EPM Cloud legacy subscriptions.
26% EPM cloud environments including new and migrated ones are already on OCI.
Oracle's data centres around the globe are standardizing on the OCI architecture which delivers greater performance and reliability.
Many features of EPM Cloud are available only in OCI.
There are two possible options for OCI migration.
1) Oracle
Managed Migration
2) Customer
Managed Migration
Oracle Managed Migration
Steps for Oracle Managed Migration
•
Oracle notifies all Service Administrators when
the OCI migration will occur for their Classic environments – at least 1 month
before the scheduled migration date. (email received on 9th Jan)
•
On the scheduled migration date, Oracle provides
new OCI environments equaling the current number of Classic environments.
– OCI
environments will have new service URLs. (with same domain name like classic
cloud URLs)
– Classic
environments continue to work at the same time.
•
Customer has 2 months to finish testing.
•
At the end of 2 months, Oracle migrates
application and all artifacts from classic cloud to OCI cloud (Test env on the
first Friday and PROD on the third Friday of month)
Customer Managed Migration
Steps for Customer Managed Migration
•
Customer creates an SR for OCI migration.
•
Flexibility to choose domain name, data centre
with CSV file in SR
•
Oracle provides new OCI environments equaling
the current number of Classic environments.
•
Customer has 6 months to finish testing.
•
Classic environments continue to work during
these 6 months.
•
Oracle will terminate the classic environments
after 6 months.
•
Customer can request termination of classic
environments via SR if their migration is finished before that.
Post migration steps (Customer Managed migration)
•
Service Administrator Tasks
– Announce
URLs of OCI environments to EPM cloud users.
– Modify
scripts to change URLs
– If
Navigation Flows are used, update Connections to change URLs (and possibly
passwords)
– If
EPM Agent is used, update its configuration to change URLs (and possibly
passwords)
– If
you have any other integrations, such as, with FDMEE or NetSuite, update them
to change URLs (and possibly passwords)
•
Individual user tasks
– Update
Smart View shared and private connections to change URLs
– Modify
bookmarks to point to the new URLs
The biggest advantage with customer managed migration is 1) flexibility to perform testing over a period of 6 months and 2) choosing the
logical domain name.
E.g. Instead of “a123456”, domain name can be “customer1”
Steps to migrate applications and artifacts (Irrespective of ownership)
•
If Single Sign On (SSO) was setup in My Services
for Classic environments, re-configure it for IDCS for OCI environments
•
If IP allowlists were configured in My Services
for Classic environments, use EPM Automate command setIPAllowList to
re-configure them for the new OCI environments
•
Clone ONLY the application from each Classic
environment to corresponding OCI environment using Clone Environment – using
schedule and order of your choice
•
Complete the testing for all applications in 6
months
•
After successful testing, clone all artifacts
(application, users and their roles, data management records, audit history,
job console history, and stored snapshots and files) from the Classic
environments to corresponding OCI environments – using schedule and order of
your choice
We, at Brovanture, are helping our clients with both these
approaches. Give us a shout if you are on EPM cloud and want to understand more about it.
