Prepare to Migrate Applications

Identify information about your source and target environment.

Before You Begin

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

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

  • If you are migrating applications from Oracle Cloud@Customer, then contact My Oracle Support to enable Classic Migration Service in your source environment. This task is unnecessary if you are migrating applications from Oracle Cloud Infrastructure Classic.

  • 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 must be in the running state in the source environment.
  • For Oracle Platform Services, see Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure.

Application Migration Considerations

While planning your migration to Oracle Cloud Infrastructure, consider the items discussed in this section.

Migrated Artifacts

Classic Migration Service migrates application artifacts.

Classic Migration Service does not migrate the following:

  • Application data

    If your application has dependencies, such as an associated database system, then Classic Migration Service creates a connection between the migrated application in the target environment and a database in the target environment. Classic Migration Service does not 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 do not 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

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

    Classic Migration Service does not migrate custom load balancer configurations from the source environment. If you have custom load balancer configurations that must be migrated, then you must migrate the load balancer either before or after migrating the application.

  • Custom Oracle Identity Cloud Service applications, roles, and role membership

    If you have custom Oracle Identity Cloud Service entities that must be migrated, then you must 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 Classic Migration Service to migrate applications to other supported geographical regions. For example, if your home region is Ashburn and the target region is Frankfurt, then 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 do not have 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, then you do not have to provide the identity domain ID for the target environment.

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

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

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

    If your home region and the target region to which you want to migrate your applications are in different geographical regions, then 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-alphanumeric_string (for example, idcs-98888f7964454b658ac6d2f625b29030).

    You will have 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 Classic Migration Service Sources

In Classic Migration Service, a source refers to the environment from which the application is migrated. Classic Migration Service 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:

  • 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, then you must create one source to migrate Oracle Process Cloud Service applications and another source 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 Classic Migration Service 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 create 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 to identify the appropriate source environment when you have multiple sources defined. If required, then 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 Classic Migration Service to migrate your applications to a new or existing instance in the public subnet in Oracle Cloud Infrastructure. When the target instance has a public endpoint, you can send your network traffic over the internet.

When you set up a target instance with a private endpoint, network traffic does not go over the internet. Private access can be from hosts within your virtual cloud network (VCN) or your on-premise network.

Using Classic Migration Service, you cannot create a new target instance in a private subnet and migrate your applications. You can, however, create a target instance in a private subnet and then use Classic Migration Service to migrate your applications to the existing instance.

You can use Classic Migration Service to migrate Oracle Java Cloud Service, Oracle SOA Cloud Service, and Oracle Analytics Cloud - Classic applications to an existing target instance in a private subnet. You cannot use Classic Migration Service to migrate Oracle Integration, Oracle Process Cloud Service, or Oracle Integration Cloud Service applications to an existing instance in a private subnet.

  1. Create the target instance in a private subnet in the target environment.

    To migrate Oracle Java Cloud Service applications, create an Oracle WebLogic Server for Oracle Cloud Infrastructure instance in the private subnet.

    To migrate Oracle SOA Cloud Service applications, create an Oracle SOA Suite on Marketplace instance in the private subnet.

    To migrate Oracle Analytics Cloud - Classic applications, create an Oracle Analytics Cloud - Generation 2 instance in the private subnet.

  2. Use Classic Migration Service to migrate your applications to the existing instance in Oracle Cloud Infrastructure.

You do not have to set up any additional security rules for private subnets. For both public and private subnet targets, permit SSH on port 22 from a source within the subnet.

Select Oracle Cloud Infrastructure Shape

Identify compute shapes that provide similar IaaS resources in Oracle Cloud Infrastructure to the shapes that you are currently using for your service instances on Oracle Cloud Infrastructure Classic.

You must perform this task only if you are migrating your application to an existing target instance. Skip this step if you are using Classic Migration Service to create a new target instance, and then migrate your application.

A compute shape defines the IaaS resources, such as OCPUs and memory, that are available to a specific node in a service instance. Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic each has its own set of standard compute shapes. See:

  • About Shapes in Using Oracle Cloud Infrastructure Compute Classic
  • Compute Shapes in the Oracle Cloud Infrastructure documentation

To ensure that a migrated service instance has the same performance characteristics as the original instance, and can support an equivalent workload, choose Oracle Cloud Infrastructure shapes that most closely map to the Oracle Cloud Infrastructure Classic shapes that you specified when you created the instance.

You must also confirm that the chosen shapes are available in your Oracle Cloud tenancy. Oracle configures shape limits for an Oracle Cloud Infrastructure region or for a specific availability domain within a region. You can use the console to view the current shape limits for your tenancy and to request a limit increase, if necessary. See Service Limits in the Oracle Cloud Infrastructure documentation.

Design the Oracle Cloud Infrastructure Network

Before you migrate your service instances from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure, you must design and implement a virtual cloud network (VCN) to support your migrated service instances.

You can create new Oracle Cloud Infrastructure compartments, VCNs, and subnets for your service instances, or you can use those that already exist. See the following topics in the Oracle Cloud Infrastructure documentation:

Consider the following guidelines when you create or select a network for your service instances:

  • If instances communicate using the default shared network in Oracle Cloud Infrastructure Classic, then use a single subnet for these instances.
  • If instances are on separate IP networks in Oracle Cloud Infrastructure Classic, then use separate subnets for these instances.
  • A VCN must have an address range that includes all of the IP networks in Oracle Oracle Cloud Infrastructure Classic that need to communicate. Alternatively, configure peering between multiple VCNs.
  • A subnet must have at least the same number of addresses as the corresponding IP network in Oracle Cloud Infrastructure Classic.
  • If an instance was created in Oracle Cloud Infrastructure Classic without public IP addresses, then use a private subnet for this instance.
  • If custom access rules were created for an instance in Oracle Cloud Infrastructure Classic to control communication to or from the instance, then create a security list in Oracle Cloud Infrastructure and assign the security list to the appropriate subnets. To use custom security lists, you must assign the instance to a custom subnet, and not the default subnet.

Before you create service instances in Oracle Cloud Infrastructure that use your new network resources, you must create policies that grant your service access to these resources. See Prerequisites for Oracle Platform Services in the Oracle Cloud Infrastructure documentation.