Manage Migrations

This topic describes how to create and manage a migration.

Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

About Migrations

A migration represents the end-to-end workflow of moving an application from a source environment to Oracle Cloud Infrastructure. Each migration moves a single application from a specified source to a specified compartment in Oracle Cloud Infrastructure.

To perform a migration, you first create a migration source by specifying the source environment and providing credentials for Application Migration to access the source environment. Application Migration discovers the resources in the source environment.

After you've created a source, you can select the application that you want to migrate. Applications that can be migrated are listed on the Applications page for each source. Before you start the migration, you must provide application-specific information including a name for the migrated application in the target environment and user credentials to access the application in the source environment. Application Migration uses this information to access the application and export the complete domain configuration along with data sources and other dependencies. Application Migration uses this information to access the application and discover application artifacts and dependencies. For example, Application Migration access the Oracle Java the WebLogic Server domain configuration and its data sources.

Next, you create a migration. To create a migration, select a source environment and then select the application in that source environment that you want to migrate. After creating a migration, wait for Application Migration to complete the create migration work request which is associated with this task. The process of migrating the application to the target environment has not yet started.

Next, provide configuration information about the application in the target environment. Application Migration migrates the application to the target environment only after you provide this information. The Configure Migration wizard lets you specify information about the target environment and the application that you are migrating. The information that you must provide varies depending on the type of application that you are migrating.

Next, start the migration. Application Migration migrates the specified application from the source environment to Oracle Cloud Infrastructure.

The name of the migrated application is the same as its name in its source environment. If there are any dependencies, such as an associated database system, Application Migration creates an Oracle Cloud Infrastructure Database System. To name the database system, Application Migration suffixes db to the name of the application. Let's consider that you want to migrate an Oracle Java Cloud Service application named MyApp in the source environment. Application Migration creates the application with the same name, MyApp, in Oracle Cloud Infrastructure and the associated database system is named MyAppdb.

A migration is successful when:

  • The target service instance is started and is healthy.
  • The service instance has been configured with all the dependencies required by the application.
  • The application has been deployed to the service instance and is reported to be in a healthy state.

After a migration completes successfully, ensure that you validate the behavior of the application in terms of its business logic. Application Migration does not perform this validation.

If the migration fails, look at the work request errors and logs to diagnose the issues. After resolving the issues, you can restart the migration.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which you should work in.

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for Application Migration API resources, see Manage Service Access and Security.

Tagging Migrations

You can add tags to your resources to help you organize them according to your business needs. You can add tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

Using the Console

To create a migration
To configure a migration
To start a migration
To delete a migration
To manage tags for a migration
To move a migration to a different compartment

Provide Configuration Information

Configuration Information for Oracle Java Cloud Service
Configuration Information for Oracle SOA Cloud Service
Configuration Information for Oracle Analytics Cloud - Classic
Configuration Information for Oracle Integration, Oracle Process Cloud Service, and Oracle Integration Cloud Service

Complete the Post-Migration Tasks

After a migration completes successfully, ensure that you validate the behavior of the application in terms of its business logic. This validation isn't performed by Application Migration. Also complete the following post-migration tasks which are specific to the type of the migrated application.

  • For Oracle Process Cloud Service and Oracle Integration Cloud Service applications, see Complete the Post-Migration Tasks.
  • For Oracle Java Cloud Service applications, complete the following tasks:
    1. Identify and copy any files to your target Oracle Java Cloud Service instance that are not automatically managed by Application Migration. See Copy Supporting Files to the Target Instance.
    2. If you created any custom users, groups, roles, or policies in your source Oracle Java Cloud Service instance, then you must recreate them in Oracle Cloud Infrastructure or target environment. See Recreate Oracle Fusion Middleware Security Resources.
    3. If your source Oracle Java Cloud Service instance uses Oracle Identity Cloud Service for authentication, then you must migrate the administrator roles and web tier policy to the target instance. See Migrate Oracle Identity Cloud Service Roles and Policies.
    4. Test your application thoroughly, and then perform cleanup and other optional configuration tasks. See Complete the Post-Migration Tasks.
  • For Oracle Analytics Cloud - Classic, update database connection string if required and verify that you can connect to the database from the target environment. Complete the following steps:
    1. If you're using Developer Client Tool for Oracle Analytics Cloud to manage data models in the source environment and if the connect string for the new database is different, then you must reconfigure the database connection information. See Edit Connections and Upload Data Model.
    2. If you're using Oracle Analytics Cloud - Classic to analyze data in an Oracle Database on Oracle Cloud Infrastructure Classic in the source environment, you must have moved your data to a database on Oracle Cloud Infrastructure before you migrated your Oracle Analytics Cloud - Classic application. After migrating the application, reconfigure the database connection to point to the new database. See Move Data from Oracle Cloud Infrastructure - Classic.
    3. If you whitelisted the IP or endpoint of your Oracle Analytics Cloud - Classic instance on Oracle Cloud Infrastructure Classic, you must perform this task again for the new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure. See Whitelist IPs for the New Service.
    4. If your organization changes the target database for replication, migrate the current data to the new database, and reconfigure your connections to replicate to your new database. See Move Replicated Data to a Different Target Database.
    5. Take some time to review various settings on the target instance and reconfigure if required. See Configure Service Settings.
    6. Reactivate delivery schedule. See Restore and Enable Delivery Schedules.
    7. Test your application thoroughly, and then perform cleanup and other optional configuration tasks. See Complete Post-Migration Tasks.