Overview of Application Migration

You can use Application Migration to migrate applications, such as Oracle Java Cloud Service, SOA Cloud Service, and Integration Classic applications, from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure.

Application Migration simplifies the migration of applications from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure. An application is a combination of deployable artifacts and the applied configuration, which can be exported from a service instance running in a source environment and imported into a compatible service instance running on Oracle Cloud Infrastructure.

Application Migration performs the following actions:

  1. Connects to a specified Oracle Cloud Infrastructure Classic source environment and authenticates with that source environment using the specified credentials.
  2. Displays a list of applications that can be migrated from the source environment. You can select the application that you want to migrate.
  3. Discovers the artifacts and configuration of the application selected for migration. You can configure this application and provide details required for the application to be set up in the target environment. When the configuration is complete, you can start the migration.
  4. Launches a service instance on Oracle Cloud Infrastructure to host the migrated application.
  5. Deploys the exported artifacts and specified configuration on the target instance in Oracle Cloud Infrastructure.

When you're satisfied that your application has been successfully migrated and works as expected, you can delete the corresponding application and associated resources in the source environment. Remember that if the migration results in any application-specific changes such as changes in IP addresses or DNS names, then you might need to update objects that reference those resources.

Workflow

If you're migrating your applications to Oracle Cloud Infrastructure using Application Migration, follow these tasks as a guide.

Task Description More Information
Complete the prerequisites Complete all the prerequisites in the source environment and gather the required information about the source environment. Prerequisites
Create a source in Application Migration Source refers to the source environment from which the application is migrated. The information that you provide while creating a source is used to discover the applications that you can migrate from the source environment. To create a source
List applications After creating a source, view the applications that you can migrate to Oracle Cloud Infrastructure. From the listed applications, select the application that you want to migrate. To view a list of applications that can be migrated
Create a migration in Application Migration. Migration represents the end-to-end workflow of moving an application from a source environment to Oracle Cloud Infrastructure. To create a migration
Start the migration Application Migration creates an instance in Oracle Cloud Infrastructure based on the configuration information you provide. After creating the instance, Application Migration exports application artifacts and its dependencies to Oracle Cloud Infrastructure. To start a migration
Complete the post-migration tasks After migrating the application, complete any post-migration tasks that are required for your application. Complete the post-migration tasks

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.
  • 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.

Also complete the following tasks based on the application that you are migrating:

  • For Oracle Platform Services services, see Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure.
  • For Oracle Java Cloud Service applications, complete the following tasks:
    1. Check if the name of the Oracle Java Cloud Service application that you want to migrate is more than 28 characters. Application Migration does not support the migration of Oracle Java Cloud Serviceapplications that have names greater than 28 characters. Before you migrate an Oracle Java Cloud Service application, rename the application so that the name has less than 28 characters.
    2. Identify the resources that are included in the WebLogic Server domains. Application Migration does not support the migration of WebLogic Server domains that include these types of resources:
      • Custom Identity or Trust Keystore
      • Foreign JNDI Provider
      • Foreign JMS Server
      • JMS Bridge Destination
      • Storage-and-Forward (SAF) Context
      • JavaMail Session
      • WebLogic Diagnostic Framework (WLDF) REST Notification Endpoint
      If your source Oracle Java Cloud Service application uses these resource types, then Oracle recommends using the Oracle Cloud Infrastructure Classic Java Migration Tool instead of Application Migration. See Migrate an Instance to Oracle Java Cloud Service Using Classic Tools.
    3. Identify the software release version of the source Oracle Java Cloud Service application. Application Migration supports the migration of source applications which have Oracle Java Cloud Service at release 16.4.5 or later and WebLogic Server at a supported release version.

      • To migrate to an Oracle WebLogic Server for Oracle Cloud Infrastructure instance in the target environment, ensure that the WebLogic Server of the source application is at 11.11.1.7, 12.2.1.3, or 12.2.1.4 version.
      • To migrate to an Oracle Java Cloud Service instance in the target environment, ensure that the WebLogic Server of the source application is at 11gR1, 12cR3, 12cRelease212, 12cRelease213, or 12cRelease214 version.

      Oracle recommends that you migrate your application to Oracle WebLogic Server for Oracle Cloud Infrastructure.

      If the WebLogic Server is at any other release version, you must upgrade to a supported release version, and then use Application Migration to migrate the application or use another tool to migration your application. To identify other migration tools that you can use to migrate Oracle Java Cloud Service applications, see About the Migration Tooling. For information about upgrading your Oracle Java Cloud Service instance to a supported release, see About Upgrading the WebLogic Server Release for an Oracle Java Cloud Service Instance.

    4. Identify whether your application data is stored in an on-premises database or in database instances that were created in Oracle Cloud Infrastructure Classic.
    5. If application data is stored in database instances that were created in Oracle Cloud Infrastructure Classic, you must migrate the application database to Oracle Cloud Infrastructure before migrating the application. See Migrate the Application Databases.
    6. Set up the required security rules in Oracle Cloud Infrastructure Classic to allow the target's subnet to communicate with the database ports. If the application data is stored in on-premises database, create a security rule to allow connections from the public IP range of the target's subnet. If you have migrated the database to Oracle Cloud Infrastructure, set up security rules to allow the target's subnet to access the application database.
    7. Gather information about the databases that you have migrated to Oracle Cloud Infrastructure. You'll need to provide this information while configuring the target environment. See Get Information About the Target Databases.
    8. If your source instance uses Oracle Identity Cloud Service for authentication, then create a new confidential application in Oracle Identity Cloud Service for the target domain.

      Identify the client ID and secret of the confidential application.

      You require this information only if you are migrating your application to an Oracle WebLogic Server for Oracle Cloud Infrastructure instance in Oracle Cloud Infrastructure. See Before You Begin with Oracle WebLogic Server for Oracle Cloud Infrastructure. You don't need this information if you are migrating to an Oracle Java Cloud Service in Oracle Cloud Infrastructure.

    9. Use Oracle Cloud Infrastructure Vault to encrypt the passwords that you need for the target domain.
      • WebLogic Server administrator password
      • Database administrator password
      • Client secret, if using Oracle Identity Cloud Service

      You require this information only if you are migrating your application to an Oracle WebLogic Server for Oracle Cloud Infrastructure instance in Oracle Cloud Infrastructure. See Before You Begin with Oracle WebLogic Server for Oracle Cloud Infrastructure. You don't need this information if you are migrating to an Oracle Java Cloud Service in Oracle Cloud Infrastructure.

  • For Oracle Process Cloud Service and Oracle Integration Cloud Service applications, see:
  • For Oracle Analytics Cloud - Classic, you must:
    • Plan your service on Oracle Cloud Infrastructure, migrate users and groups, reconfigure single-sign on, and integrate your identity provider. See Prepare to Migrate Oracle Analytics Cloud - Classic Instances.
    • Review all data connections used by the application. Ensure that they are accessible from Oracle Cloud Infrastructure. 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 you're currently using Oracle Analytics Cloud - Classic to analyze data in an Oracle Database on Oracle Cloud Infrastructure Classic, you must create a database instance on Oracle Cloud Infrastructure and migrate your data. See Select a Method to Migrate Database Instances.
  • For Oracle Integration, grant service administrator permissions for each service instance. For information about the permissions required for Oracle Integration, see Grant Access and Manage Security.

Next: After completing the prerequisites, provide information about the source environment to create an Application Migration source. See To create a source.

Supported Applications

Use Application Migration to migrate the following applications to Oracle Cloud Infrastructure:

  • Oracle Java Cloud Service
  • Oracle SOA Cloud Service
  • Oracle Analytics Cloud - Classic
  • Oracle Integration
  • Oracle Process Cloud Service
  • Oracle Integration Cloud Service

Supported Regions

Application Migration is available in:

  • Australia East (Sydney)
  • Australia South (Melbourne)
  • Brazil East (Sao Paulo)
  • Germany Central (Frankfurt)
  • Japan East (Tokyo)
  • Netherlands Northwest (Amsterdam)
  • UK South (London)
  • US East (Ashburn)
  • US West (Phoenix)

Service Limits

Application Migration has various default limits. When you create a source or migration in Application Migration, the system ensures that your request is within the bounds of your limit. The limit that applies to you depends on your subscription.

The following limits apply to Application Migration resources, such as source and migration. These limits apply to resources in each region.

Resource

Monthly Universal Credits

Pay-as-You-Go or Promo

Total sources 100 50
Total migrations 100 50
Total active migrations 10 5
Total Oracle Java Cloud Service migrations 30 10
Total Oracle SOA Cloud Service migrations 30 10
Total Oracle Integration Classic migrations 30 10
Total Oracle Integration Cloud Service migrations 30 10
Total Oracle Process Cloud Service migrations 30 10
Total Oracle Analytics Cloud Service migrations 30 10

You can submit a request to increase the service limits for Application Migration resources. See Requesting a Service Limit Increase.

In addition, applications that you migrate use resources that the Application Migration service creates, such as database instances, Oracle Java Cloud Service instances, SOA Cloud Service instances, Compute instances, and networking resources. These resources are also subject to their respective service limits. For more information about the service limits that apply to other resources, see Service Limits.

Service Events

Actions that you perform on sources and migrations in Application Migration emit events. You can define rules that trigger a specific action when an event occurs. For example, you might define a rule that sends a notification to administrators when someone migrates an application. See Overview of Events and Get Started with Events.

Source Event Types

This table lists the source events that you can reference.

Event Name Event Type
Source - Create Begin com.oraclecloud.applicationmigration.createsource.begin
Source - Create End com.oraclecloud.applicationmigration.createsource.end
Source - Update Begin com.oraclecloud.applicationmigration.updatesource.begin
Source - Update End com.oraclecloud.applicationmigration.updatesource.end
Source - Delete End com.oraclecloud.applicationmigration.deletesource.end
Source - Change Compartment com.oraclecloud.applicationmigration.changesourcecompartment

Example

This example shows information associated with the event Source - Create Begin.

{
  "eventType": "com.oraclecloud.applicationmigration.createsource.begin",
  "cloudEventsVersion": "0.1",
  "eventTypeVersion": "2.0",
  "source": "applicationmigration",
  "eventId": "<unique_ID>",
  "eventTime": "2019-12-13T05:51:25.412Z",
  "contentType": "application/json",
  "data": {
    "compartmentId": "ocid1.compartment.oc1..<unique_ID>",
    "compartmentName": "example-compartment",
    "resourceName": "example-source",
    "resourceId": "ocid1.amssource.oc1..<unique_ID>",
    "availabilityDomain": "<availability_domain>",
    "freeFormTags": {
      "Department": "Finance"
    },
    "definedTags": {
      "Operations": {
        "CostCenter": "42"
      }
    },
    "additionalDetails": {}
  }
}

Migration Event Types

This table lists the migration events that you can reference.

Event Name Event Type
Migration - Create Begin com.oraclecloud.applicationmigration.createmigration.begin
Migration - Create End com.oraclecloud.applicationmigration.createmigration.end
Migration - Update Begin com.oraclecloud.applicationmigration.updatemigration.begin
Migration - Update End com.oraclecloud.applicationmigration.updatemigration.end
Migration - Migrate Application End com.oraclecloud.applicationmigration.migrateapplication.end
Migration - Delete End com.oraclecloud.applicationmigration.deletemigration.end
Migration - Change Compartment com.oraclecloud.applicationmigration.changemigrationcompartment

Example

This example shows information associated with the event Migration - Create Begin:

{
  "eventType": "com.oraclecloud.applicationmigration.createmigration.begin",
  "cloudEventsVersion": "0.1",
  "eventTypeVersion": "2.0",
  "source": "applicationmigration",
  "eventId": "<unique_ID>",
  "eventTime": "2019-12-13T05:51:25.412Z",
  "contentType": "application/json",
  "data": {
    "compartmentId": "ocid1.compartment.oc1..<unique_ID>",
    "compartmentName": "example-compartment",
    "resourceName": "example-migration",
    "resourceId": "ocid1.amsmigration.oc1..<unique_ID>",
    "availabilityDomain": "availability_domain",
    "freeFormTags": {
      "Department": "Finance"
    },
    "definedTags": {
      "Operations": {
        "CostCenter": "42"
      }
    },
    "additionalDetails": {}
  }
}

Ways to Access Oracle Cloud Infrastructure

You can access Oracle Cloud Infrastructure using the Console (a browser-based interface) or the REST API. Instructions for the Console and API are included in topics throughout this guide. For a list of available SDKs, see Software Development Kits and Command Line Interface.

To access the Console, you must use a supported browser. You can use the Console link at the top of this page to go to the sign-in page. You are prompted to enter your cloud tenant, your username, and your password.

Application Migration also supports private access from Oracle Cloud Infrastructure resources in a VCN through a service gateway. A service gateway allows connectivity to the Application Migration public endpoints from private IP addresses in private subnets. Set up a service gateway if you are using the REST API or CLI to access Oracle Cloud Infrastructure. If you are using the console to access Oracle Cloud Infrastructure, you need not set up a service gateway. You can optionally use IAM policies to control which VCNs or ranges of IP addresses can access Application Migration. See Access to Oracle Services: Service Gateway for details.

For general information about using the API, see REST APIs.

Authentication and Authorization

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

An administrator in your organization needs to set up groups, compartments, and policies that control which users can access which services, which resources, and the type of access. For example, the policies control who can create users, create and manage the cloud network, and launch instances. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see Policy Reference.

If you’re a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.