Prepare to Migrate

Identify information about your source and target environment.

Prerequisites

Before you migrate your applications to Oracle Cloud Infrastructure, complete the following tasks.

  • Ensure that you have access to Application Migration. To enable access to Application Migration in your Oracle Cloud Infrastructure tenancy, contact your Oracle Cloud customer service representative.

  • You must have credentials with the required permissions for the applications that you want to migrate in both Oracle Cloud Infrastructure Classic and Oracle Cloud Infrastructure environments. For example, to migrate an Oracle Java Cloud Service application you must specify a user who has the JAAS JavaAdministrator role in Oracle Cloud Infrastructure Classic while creating a source, and while configuring the migration, you must specify a user who has the JaaS_Administrator service entitlement in Oracle Cloud Infrastructure. For information about the service administrator role that is specific to the application you want to migrate, see About Service Administrator Roles.
  • Set up an Oracle Cloud Infrastructure tenancy and ensure that the required networking configuration is complete.
  • Identify or create a compartment in Oracle Cloud Infrastructure to which you want to migrate the application.
  • Set up the required policies in Oracle Cloud Infrastructure. See Manage Service Access and Security.
  • Applications that you want to migrate should be in the running state in the source environment.
  • For Oracle Platform Services, see Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure.

Considerations

While planning your migration to Oracle Cloud Infrastructure, consider the following points.

Migrated Artifacts

Application Migration migrates application artifacts.

Application Migration doesn't migrate the following:

  • Application data is not migrated.

    If your application has dependencies, such as an associated database system, Application Migration creates a connection between the migrated application in the target environment and a database in the target environment. Application Migration doesn't migrate the application data that resides in the source database.

    Depending on where the data is stored, you might have to migrate the database to Oracle Cloud Infrastructure before you migrate the application. If your data is available in an on-premises database, then you don't have to migrate the database. If your data is available in an Oracle Cloud Infrastructure Classic database, then you must migrate the application database to Oracle Cloud Infrastructure before migrating the application.

  • Custom load balancer configurations are not migrated.

    If your application has a load balancer in the source environment, such as Oracle Traffic Director, then Application Migration creates a load balancer in the target environment and establishes a connection between the migrated application and the newly created load balancer.

    Application Migration doesn't migrate custom load balancer configurations from the source environment. If you have custom load balancer configurations that must be migrated, you'll need to migrate the load balancer either before or after migrating the application.

  • Custom Oracle Identity Cloud Service applications, roles, and role membership are not migrated.

    If you have custom Oracle Identity Cloud Service entities that must be migrated, you'll need to migrate the user information either before or after migrating the application.

Home Region and Geographical Regions

Identify your home region and the Oracle Cloud Infrastructure region to which you want to migrate your application. Home region refers to the region in which your Oracle Cloud Infrastructure account is provisioned.

In addition to your home geographical region, you can use Application Migration to migrate applications to other supported geographical regions too. For example, if your home region is Ashburn and the target region is Frankfurt, you can migrate your Oracle Cloud Infrastructure Classic applications from eucom-north-1 to target instances in the Frankfurt region. To migrate your applications to another geographical region, provide the identity domain ID for the target environment. You don't need to provide this information if you are migrating within a geographical region that contains your home region. For example, if you want to migrate your applications to Phoenix and your home region is Ashburn, you don't have to provide the identity domain ID for the target environment.

  1. Open the navigation menu. Under Governance and Administration, open the Administration menu, and then click Region Management.

    The Infrastructure Regions page displays your home region and the other regions that you have subscribed to in the target environment. You can migrate your application only to an Oracle Cloud Infrastructure region that you have subscribed to.

  2. Identify the Oracle Cloud Infrastructure region to which you want to migrate your application. Ensure that Application Migration is available in this region. See Supported Regions.
  3. If the home region and target region are in the same geographical region, skip this step.

    If your home region and the target region to which you want to migrate your applications are in different geographical regions, provide your Oracle Identity Cloud Service instance ID, which is also referred to as your tenant name. This ID is typically found in the URL you use to access the Oracle Identity Cloud Service console in the target environment, and has the format idcs-string-of-letters-and-numbers (for example, idcs-98888f7964454b658ac6d2f625b29030.

    You'll need to provide this information later.

Application Downtime

The migration process does not affect the availability of your existing application in Oracle Cloud Infrastructure Classic. The application continues to run and can serve client requests during this process.

After the application is migrated successfully, you can reroute clients to the migrated application in Oracle Cloud Infrastructure.

Number of Application Migration Sources

In Application Migration, a source refers to the environment from which the application is migrated. Application Migration supports migration from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure. A source connects an Oracle Cloud Infrastructure Classic account and region to Oracle Cloud Infrastructure.

You can create one or more sources depending on the following factors:

  • The region from which you want to migrate applications. If you want to migrate applications from more than one Oracle Cloud Infrastructure Classic account and region, then create multiple sources. For example, if you want to migrate applications from uscom-central-1 and uscom-east-1 to Oracle Cloud Infrastructure, then create a source for each region.
  • The type of application that you want to migrate. If you want to migrate Oracle SOA Cloud Service and Oracle Process Cloud Service applications, you must create one source to migrate Oracle Process Cloud Service applications and another to migrate Oracle SOA Cloud Service applications.
  • Roles associated with the service administrator credentials that you provide to access the source environment. If the service administrator username that you specify while creating an Application Migration source has the required roles to access multiple applications, then you can use a single source to migrate these applications. For example, if the service administrator that you specify while creating a source has both JaaS_Administrator and SOA_Administrator roles, then the source you've created retrieves details of both Oracle Java Cloud Service and Oracle SOA Cloud Service applications.

While creating a source, assign an appropriate name and provide a description. This helps you to identify the appropriate source environment when you have multiple sources defined. If required, enter the username and password of the administrator who has the service administrator role in your Oracle Cloud Infrastructure Classic account for the applications that you want to migrate.

Public or Private Subnets

You can use Application Migration to migrate your applications to a public subnet in Oracle Cloud Infrastructure.

Using Application Migration, you can't create a new Oracle WebLogic Server for Oracle Cloud Infrastructure or Oracle SOA Suite on Marketplace instance in a private subnet and migrate your applications. To migrate your applications to an Oracle WebLogic Server for Oracle Cloud Infrastructure or Oracle SOA Suite on Marketplace instance in a private subnet:

  1. Create the Oracle WebLogic Server for Oracle Cloud Infrastructure or Oracle SOA Suite on Marketplace instance in a private subnet in the target environment.
  2. Use Application Migration to migrate your applications to the existing instance in Oracle Cloud Infrastructure.