C Migrate Oracle Content and Experience to 2nd-Generation Oracle Cloud Infrastructure (OCI)

If you have Oracle Content and Experience instances that aren't running on the 2nd-generation Oracle Cloud Infrastructure (OCI) natively (that is, using Infrastructure Console to manage service instances), then Oracle recommends that you migrate those instances to this new native OCI environment. This will ensure that you’ll enjoy the benefits and advances of Oracle’s cloud platform in the future.

Note:

The only automated migration path currently supported is from Oracle Content and Experience on OCI Classic. Automated migration from other deployment environments will be supported at a later date. For instances with limited data and files, a manual migration may be an option. Sign in to your Oracle Support account, and see Migrating Legacy Oracle Content & Experience Cloud to Oracle Cloud Infrastructure (OCI).

Migration isn't automatic; you’ll need to perform a few steps:

Oracle Support will work with you to schedule the migration.

  1. Create a new instance of Oracle Content and Experience on OCI with Infrastructure Console. This will be the target instance your data will be migrated to.

    Note:

    You don't need to set up users and groups because they already exist in IDCS, and the application roles will be automatically assigned to the target instance during migration.
  2. Prepare for migration by collecting information you'll need for your service request and creating a list of any integrations you have for steps you'll need to take after migration.
  3. Submit a migration service request, and confirm the date and time of your migration.
  4. Watch the progress of the migration. Your service request will be updated as your migration progresses, and when it's done, you'll be asked to verify that your new instance is working as expected.
  5. Finalize the migration by completing any steps necessary to migrate any integrations that your instance has with other services or applications.

Prepare for the Migration

  • Make a note of the URL of the new instance (the target) you created, to include it in your migration request.
  • Make a note the URL of your old instance (the source), to include it in your migration request.
  • Make an inventory of all integrations that your old instance has with any other services or applications, either directly or through REST API calls. If there are any such integrations, then you’ll need to take some actions after the migration.

Submit a Migration Service Request

When you’re ready for your migration, you must submit a migration request to get the process started:

  1. Sign in to Oracle Cloud Support.
  2. Create a new service request.
  3. For the Problem Type, select Service Instance Migration, then choose From OCI-Classic to OCI-Native.
  4. Provide the following information in your service request:
    • The URL of your source instance (the instance you’re migrating from)
    • The URL of your target instance (the instance you’re migrating to)
    • If you use Akamai delivered by Oracle, mention that so we can update the URLs in your Akamai configuration after migration
  5. Provide the preferred date you would like migration to start.
  6. Submit your service request.

    After Oracle Support receives your migration service request, we'll schedule your migration based on the date you requested, and the service request will be updated with the date and time your migration will start.

  7. Confirm in the service request that you approve the migration start date and time.

Updates will be made to the service request to show how the migration is progressing. The data migration will be done at the back end; no action is required at your end other than to keep up with any service request updates, and to validate the migration after it's done.

The Migration Process

Here's what happens during the migration:

  1. Oracle Support updates the service request when migration begins.

    Important:

    At this point, you must not make any changes to your old (source) instance. Any changes made after migration starts won't be migrated to your new instance.
  2. Your content and configuration data is exported from your old instance (the source), and imported into your new instance (the target).
  3. When the migration is functionally ready, Oracle Support updates the service request, and you're asked to validate your new instance to make sure everything is working as expected.
  4. If you find any problems, note them in the service request. Oracle Support will work to resolve the issues, and will let you know through the service request when the instance is ready for validation.
  5. When everything is working as expected, note in the service request that you accept the migrated instance.

Note:

The old instance will remain up for a while in case you need to refer back to it for any reason. After that time the instance will be terminated.

Finalize the Migration

If your old instance integrated or communicated with other services or applications, either directly or through REST API calls, you might need to perform post-migration tasks.

The following items apply service-wide:

  • Credentials aren't migrated, so you'll need to reconfigure user credentials for all integrations that use them.
  • The Oracle Content and Experience URL pattern is different, so you'll need to update the URLs in your integrations that use them.

    The old URLs used the following pattern:

    https://<service-name>-<account-name>.<region>.oraclecloud.com/documents

    The new URLs used the following pattern:

    https://<service-name>-<account-name>.<service-type>.ocp.oraclecloud.com/documents

Integration Things to Do After Migration
Oracle Integration
  • Reconfigure credentials.
  • Update Oracle Content and Experience URLs in Oracle Integration Cloud.
Oracle Commerce Cloud
  • Reconfigure credentials.
  • Update Oracle Content and Experience URLs in Oracle Commerce Cloud.
Oracle Process Cloud Service
  • Reconfigure credentials.
Oracle Eloqua Cloud Service
  • Reconfigure credentials.
Oracle Policy Automation
  • Reconfigure credentials.
Oracle Cobrowse Cloud Service
  • Reconfigure credentials.
Responsys
  • Reconfigure credentials.
Visual Builder Cloud Service (VBCS)
  • Reconfigure credentials.
  • Update Oracle Content and Experience URLs in VBCS components.
CDN/Akamai
  • If you use Akamai delivered by Oracle, we'll update the Oracle Content and Experience URLs in your Akamai configuration after you verify your migration. Otherwise, you must update the URLs in your CDN configuration yourself.
REST API calls
  • Update Oracle Content and Experience URLs in any REST API calls.
Client SDK/CLI usage
  • If the URL is persisted/cached locally on the client side, then update Oracle Content and Experience URLs in the configuration.
Connectors
  • Reconfigure credentials.

Note:

Any bookmarks to content on your old instance will no longer work because the URL of your new instance has changed.