Migrate Oracle SOA Cloud Service

You can migrate Oracle SOA Cloud Service applications to an Oracle SOA Suite on Marketplace or Oracle SOA Cloud Service instance in Oracle Cloud Infrastructure. Oracle recommends that you migrate to Oracle SOA Suite on Marketplace.

Caution

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

Prerequisites

Ensure that you complete the prerequisites to set up and use Application Migration. See Prerequisites. Additionally, complete the following tasks before you migrate Oracle SOA Cloud Service applications to Oracle Cloud Infrastructure.

  • Identify if you want to migrate your application to an Oracle SOA Suite on Marketplace or Oracle SOA Cloud Service instance in the target environment. Oracle recommends that you migrate to an Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure.
  • In the Oracle SOA Cloud Service Console in the source environment, click an instance name to view instance details, and then note down the following information:
    • Service Type: Identify the service type of the Oracle SOA Cloud Service application that you want to migrate. Application Migration supports the migration of Oracle SOA Cloud Service applications have the service type SOA with SB & B2B Cluster.

      Oracle SOA Cloud Service has three service types: Business Activity Monitoring, MFT Cluster, and SOA with SB & B2B Cluster. You can't use Application Migration to migrate Oracle SOA Cloud Service applications with service types Business Activity Monitoring or MFT Cluster.

    • Version: If you are migrating to an Oracle SOA Suite on Marketplace instance in the target environment, identify the Oracle SOA Cloud Service version in the source environment. Application Migration supports the migration of Oracle SOA Cloud Service applications which are at 12.1.3, 12.2.1.2, 12.2.1.3, or 12.2.1.4 version in the source environment. Application Migration migrates the application to Oracle SOA Suite on Marketplace version 12.2.1.4 in the target environment.

      If you are migrating your application to an Oracle SOA Cloud Service instance in the target environment, Application Migration migrates the application to Oracle SOA Cloud Service version 12.2.1.3.

    • Nodes: Identify if your Oracle SOA Cloud Service application contains a single node or multiple nodes in the source environment.
  • If your application contains a single node, ensure that you can SSH to that node. If your application contains multiple nodes, ensure that the SSH ports to the Managed Servers and the WebLogic Administration Server are open.

When you migrate your application to Oracle SOA Suite on Marketplace, Application Migration discovers the licensing type of the source instance and creates the target instance with the same licensing type. Only if B2B adapter is enabled on the source instance, Application Migration creates the target instance with a paid license even when you have BYOL in the source environment.

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

Create a Source

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Choose a compartment you have permission to work in (on the left side of the page). The page updates to display only the resources in that compartment. If you're not sure which compartment to use, contact an administrator. For more information, see Access Control.
  3. Click Create Source.
  4. Enter the required information.
    • Name: Enter a user-friendly name for the source environment.
    • Description: Optionally, provide a description to help you identify the source environment.
    • Compartment: Select the compartment where you want to create the source.
    • Source Type: Select Oracle Cloud Infrastructure - Classic.
    • Account: The name of your Oracle Cloud Infrastructure Classic account.

      If you are using a cloud account with Identity Cloud Service (IDCS), enter the service instance ID. For example, if Compute-567890123 is the account name of your Oracle Cloud Infrastructure Classic Compute service entitlement, then enter 567890123.

      If you are using a traditional cloud account, enter your identity domain ID.

    • Region: Select the Oracle Cloud Infrastructure Classic region from which you want to migrate your application.
    • Service Administrator Username: Enter the username of the administrator who has the SOA_Administrator role in your Oracle Cloud Infrastructure Classic account. This admin role is required for administering SOA cloud service.
    • Service Administrator Password: The password for the specified user.
    • Tags: Optionally, you can add tags. If you have permissions to create a resource, you also have permissions to add free-form tags to that resource. To add a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should add tags, skip this option (you can apply tags later) or ask your administrator.

  5. Click Create.

A source is created. The Work Requests page appears and it displays the status of the Create Source work request. To track the progress of the operation, you can monitor the associated work request. For more information, see Viewing the State of a Work Request. Application Migration attempts to connect to the source environment using the information you have provided. If the connection is successful, the status of the source changes from creating to active and the service fetches the list of applications in the source environment that can be migrated.

If Application Migration is unable to connect to the source environment, the status of the source changes from creating to inactive and the status of the Create Source work request changes to failed.

Next:

If the source is in the active state, click the source to view the list of applications. Identify an application that you want to migrate to Oracle Cloud Infrastructure, and then create a migration. You can only migrate an application which is in the Ready state. If the application is in any other state, you'll need to perform corrective actions. See To view a list of applications.

If the source is in the inactive state, click the Create Source work request to view the logs and errors to identify the issues. For example, you'll need to update the authorization details if the error message is, Failed to authorize customer in source environment. See To update authorization credentials for a source.

Create a Migration

Use a migration to migrate a single application to Oracle Cloud Infrastructure. If prompted, provide the credentials of the service administrator in the source environment. Application Migration uses this information to access the application and discover application artifacts and dependencies. For example, the WebLogic Server domain configuration and its data sources.

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Select the compartment that contains your source.
  3. Click Sources, and then select your source.

    You can migrate applications only from a source that is in the Active state.

    A list of applications is displayed.
  4. Click the Actions icon (three dots) for the application that you want to migrate, and then click Create Migration.
  5. On the Create Migration page, enter the required information:
    • Migration Name: A user-friendly name for the migration.
    • Description: Optionally, enter a description to help you identify the application being migrated.
    • Application Administrator Username: Enter the WebLogic administrator username. This user must have the service administrator role in the source environment.
    • Application Administrator Password: The password for the specified user.
    • Target Instance Type: Select Oracle SOA Cloud Service or Oracle SOA Suite on Marketplace to specify the type of target instance in Oracle Cloud Infrastructure. Oracle recommends that you select Oracle SOA Suite on Marketplace.
    • Use Existing Target Instance: Select this check box if you want to migrate your application to an existing instance in the target environment.

      If you don't select this option, Application Migration creates a new instance in the target environment to host the application that you want to migrate.

    • Tags: Optionally, you can add tags. If you have permissions to create a resource, you also have permissions to add free-form tags to that resource. To add a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should add tags, skip this option (you can apply tags later) or ask your administrator.

  6. Click Create to create a migration.

A migration is created. The migration is created in the same compartment where the source is located. The Work Requests page appears, and it displays the status of the Create Migration work request. To track the progress of the operation, you can monitor the associated work request. For more information, see Viewing the State of a Work Request. Initially, the state of the migration is Discovering, in which the Application Migration connects to the application with the supplied credentials and discovers the application artifacts. When the migration is created and application artifacts are successfully discovered, the status of the migration changes to Missing config fields and the Configure button is enabled.

Next: Use the Configure Migration wizard to provide information about the target environment. You can initiate the process to migrate an application using Application Migration only after you provide this information.

Configure and Migrate

The configuration information that you must provide for the migration depends on the type of the target instance and whether you want to migrate to an existing instance or create a new instance in Oracle Cloud Infrastructure. You can migrate your application to an Oracle SOA Suite on Marketplace or Oracle SOA Cloud Service instance. Oracle recommends that you migrate your application to Oracle SOA Suite on Marketplace.

Service configuration information to migrate to an existing Oracle SOA Suite on Marketplace instance

Ensure that you complete the following tasks before configuring your migration.

  • Identify an existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure or create a new instance to host the application that you want to migrate. This instance must be connected to a database in Oracle Cloud Infrastructure. Ensure that the database and the instance are in the same public or private subnet in Oracle Cloud Infrastructure. See Create and View Oracle SOA Suite on Marketplace Instances.
  • Note down the Resource Manager Stack OCID of the target instance. You'll need to provide this information while configuring the migration.
    1. Open the navigation menu. Under Solutions and Platform, go to Resource Manager and click Stacks.
    2. Select the compartment that contains the target stack to which you want to migrate your application.
    3. Click the stack's name to view the detail page for a stack, and then copy the OCID of the stack.
  • Create a secret which contains the private SSH key.

    Before creating the target instance, you'd have created a SSH public/private key pair. While creating the target instance, you had provided the public SSH key. While configuring the migration, you must provide the corresponding private SSH key. To provide the private SSH key, you must create a secret in Oracle Cloud Infrastructure. See Managing Secrets. After creating this secret, copy the OCID of this secret as you'll have to provide this information while configuring the migration.

  • Ensure that the target instance is available and is in the running state when you migrate your application.
  • Ensure that you configure and run the migration in the region where the target instance exists.

Enter the required configuration values for the existing instance in the target environment.

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Select the compartment that contains the migration that you want to configure.
  3. Click Migrations, and then select your migration.
  4. Click Configure.
  5. In the Configure Service section, click Configure and enter the required information:
    • WebLogic Server Admin User Name: Enter the name of the WebLogic administrator user for the existing target instance.
    • WebLogic Server Admin Password: Enter the password for the specified user in plain-text format.
    • Resource Manager Stack OCID: Enter the resource manager stack OCID for the target instance.

      The target instance is provisioned as a Terraform stack using Resource Manager.

    • SSH Private Key Secret OCID: Enter the OCID of the secret that contains the private SSH key of the target instance.
  6. Click Configure to return to the Configure Migration page.
  7. Review the information you've provided. When you're ready, click Save and Run to start the migration immediately.
  8. When prompted for confirmation, click Start.
Example for ConfigurationField Reference

This is an example of the values you can provide for the serviceConfig field while migrating an Oracle SOA Cloud Service application to an existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure.

{
  "serviceConfig": {
    "WeblogicAdminUser": {
      "name": "WebLogic Admin User",
      "group": "Target SOA On Marketplace",
      "type": "user_name",
      "value": "weblogic",
      "description": "Weblogic Admin User",
      "isRequired": true,
      "isMutable": true
    },
    "rmStackOcid": {
      "name": "Resource Manager Stack Ocid",
      "group": "Target SOA On Marketplace",
      "type": "OCID",
      "value": "ocid1.unique_id",
      "description": "OCID of the Resource Manager stack which has precreated SOA Marketplace instance",
      "isRequired": true,
      "isMutable": true
    },
    "sshKeySecretOcid": {
      "name": "SSH Private Key Secret Ocid",
      "group": "Target SOA On Marketplace",
      "type": "OCID",
      "value": "ocid1.unique_id",
      "description": " The Secrets OCID that contains ssh private key for your weblogic admin instance",
      "isRequired": true,
      "isMutable": true
    },
    "WeblogicAdminPassword": {
      "name": "Weblogic Admin Password",
      "group": "Target SOA On Marketplace",
      "type": "password",
      "value": "xxxxxxx",
      "description": "Weblogic Admin Password",
      "isRequired": true,
      "isMutable": true
    }
  }
}
Service configuration information to migrate to a new Oracle SOA Suite on Marketplace instance

As part of the migration process, Application Migration creates a new Oracle SOA Suite on Marketplace instance in 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 SOA 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.

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Select the compartment that contains the migration that you want to configure.
  3. Click Migrations, and then select your migration.
  4. Click Configure.
  5. In the Configure Service section, click Configure and enter the required information:
    • Availability Domain: Select the availability domain where you want the service instance to be created. This instance hosts the migrated application.
    • Virtual Cloud Network: Select the VCN where you want to create the service instance that hosts the migrated application.
    • Subnet: Select the subnet where you want to create the service instance that hosts the migrated application.
    • System Database Administrator Username: The SYS database administrator. You'll provide this username while accessing the Oracle Cloud Infrastructure Database System that is created in the target environment. Application Migration populates the value for this field. Do not change this value.
    • System Database Administrator Password: Set a password for the SYS database administrator.

      The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the username (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.

    • SSH Key: Upload or paste the public SSH key that you'll use to connect to the migrated instance and database in the target environment.
    • WebLogic Administrative User: Enter the name of the WebLogic administrator user for the target service instance.
    • WebLogic Administrative Password: Set the password for the WebLogic administrator for the target service instance.

      The password must start with a letter, is between 8 and 30 characters long, contain at least one number, and, optionally, any number of the special characters ($ # _).

  6. Click Configure to return to the Configure Migration page.
  7. Review the information you've provided. When you're ready, click Save and Run to start the migration immediately.
  8. When prompted for confirmation, click Start.

The target domain is provisioned as a Terraform stack using Resource Manager. To access the new domain, see these topics:

If the work request indicates that the stack creation failed, use Resource Manager to view the log files. See Stack Creation Failed.

If the work request indicates that the import step of the migration failed, you can get additional information by connecting to the first node in the target domain.

After correcting any problems, you can run the migration again.

Example for ConfigurationField Reference

This is an example of the values you can provide for the serviceConfig field while migrating an Oracle SOA Cloud Service application to a new Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure.

{
  "configuration": {
    "serviceConfig": {
      "subnetId": {
        "name": "Subnet ID",
        "group": "Target SOA On Marketplace",
        "type": "subnet",
        "value": "ocid1.subnet.oc1.iad.unique_id",
        "description": "Subnet ID",
        "isRequired": true,
        "isMutable": true
      },
      "soacsPublicKey": {
        "name": "Public Key",
        "group": "Target SOA On Marketplace",
        "type": "text",
        "value": "ssh-rsa AAAAB...",
        "description": "Authorize this Public Key",
        "isRequired": true,
        "isMutable": true
      },
      "availabilityDomain": {
        "name": "Availability Domain",
        "group": "Target SOA On Marketplace",
        "type": "ad",
        "value": "HeYD:US-ASHBURN-AD-1",
        "description": "Availability Domain",
        "isRequired": true,
        "isMutable": true
      },
      "WeblogicAdminUser": {
        "name": "WebLogic Admin User",
        "group": "Target SOA On Marketplace",
        "type": "user_name",
        "value": "weblogic",
        "description": "Weblogic Admin User",
        "isRequired": true,
        "isMutable": true
      },
      "soacsDBPassword": {
        "name": "Database Password",
        "group": "Target SOA On Marketplace",
        "type": "password",
        "value": "xxxxxxxx",
        "description": "Database Password (used by SYS, SYSTEM and PDB Admin)",
        "isRequired": true,
        "isMutable": true
      },
      "WeblogicAdminPassword": {
        "name": "Weblogic Admin Password",
        "group": "Target SOA On Marketplace",
        "type": "password",
        "value": "xxxxxxxx",
        "description": "Weblogic Admin Password",
        "isRequired": true,
        "isMutable": true
      },
      "soacsDBUser": {
        "name": "Database User",
        "group": "Target SOA On Marketplace",
        "type": "user_name",
        "value": "SYS",
        "description": "Database User",
        "isRequired": true,
        "isMutable": false
      }
    }
  }
}
Service configuration information to migrate to an existing Oracle SOA Cloud Service instance

Application Migration migrates your application to an existing Oracle SOA Cloud Service instance in the target environment.

Enter the required configuration values for the existing target instance.

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Select the compartment that contains the migration that you want to configure.
  3. Click Migrations, and then select your migration.
  4. Click Configure.
  5. In the Configure Service section, click Configure and enter the required information:
    • WebLogic Server Admin User Name: Enter the name of the WebLogic administrator user for the existing target instance.
    • WebLogic Server Admin Password: Enter the password for specified user in plain-text format.
    • Target Service Name: Enter the name of the Oracle SOA Cloud Service instance in the target environment to which you want to migrate your application.
    • PaaS Administrator Username: Enter the name of the user who has the SOA_Administrator service entitlement in the target environment. Application Migration uses these credentials to access Oracle PaaS Service Manager, and then import the application artifacts to Oracle Cloud Infrastructure.
    • PaaS Administrator Password: Enter the password for the specified user.
    • PaaS Target Identity Domain: 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, and has the format idcs-string-of-letters-and-numbers (for example, idcs-98888f7964454b658ac6d2f625b29030).

      You need to specify a value for this field only if you are migrating your applications to an Oracle Cloud Infrastructure region that isn't in your geographical home region. See Considerations.

  6. Click Configure to return to the Configure Migration page.
  7. Review the information you've provided. When you're ready, click Save and Run to start the migration immediately.
  8. When prompted for confirmation, click Start.
Example for ConfigurationField Reference

This is an example of the values you can provide for the serviceConfig field while migrating an Oracle SOA Cloud Service application to an existing Oracle SOA Cloud Service instance in Oracle Cloud Infrastructure.

{
  "serviceConfig": {
    "WeblogicAdminUser": {
      "name": "WebLogic Admin User",
      "group": "Target SOA Cloud Service",
      "type": "user_name",
      "value": "weblogic",
      "description": "Weblogic Admin User",
      "isRequired": true,
      "isMutable": true
    },
    "paas/password": {
      "name": "PaaS Administrator Password",
      "group": "PaaS Service Manager",
      "type": "password",
      "value": "*********",
      "description": "Password associated with the specified username.",
      "isRequired": true,
      "isMutable": true
    },
    "WeblogicAdminPassword": {
      "name": "Weblogic Admin Password",
      "group": "Target SOA Cloud Service",
      "type": "password",
      "value": "**************",
      "description": "Weblogic Admin Password",
      "isRequired": true,
      "isMutable": true
    },
    "targetServiceName": {
      "name": "Target Service Name",
      "group": "Target SOA Cloud Service",
      "type": "text",
      "value": "unique-target-instance-name",
      "description": "SOACS Precreated Target Instance Name",
      "isRequired": true,
      "isMutable": true
    },
    "paas/user": {
      "name": "PaaS Administrator Username",
      "group": "PaaS Service Manager",
      "type": "user_name",
      "value": "joe",
      "description": "Username for the account.",
      "isRequired": true,
      "isMutable": true
    },
    "paas/identity_domain": {
      "name": "PaaS Identity Domain",
      "group": "PaaS Service Manager",
      "type": "text",
      "value": "idcs-unique_ID",
      "description": "PSM Identity Domain associated with the account",
      "isRequired": false,
      "isMutable": true
    }
  }
}
Service configuration information to migrate to a new Oracle SOA Cloud Service instance

As part of the migration process, Application Migration creates a new Oracle SOA Cloud Service instance in 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 SOA 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.

Enter the required configuration values for the new target instance.

  1. Open the navigation menu. Under Solutions and Platform, click Application Migration.
  2. Select the compartment that contains the migration that you want to configure.
  3. Click Migrations, and then select your migration.
  4. Click Configure.
  5. In the Configure Service section, click Configure and enter the required information:
    • Availability Domain: Select the availability domain where you want the service instance to be created. This instance hosts the migrated application.
    • Virtual Cloud Network: Select the VCN where you want to create the service instance that hosts the migrated application.
    • Subnet: Select the subnet where you want to create the service instance that hosts the migrated application.
    • System Database Administrator Username: The SYS database administrator. You'll provide this username while accessing the Oracle Cloud Infrastructure Database System that is created in the target environment. Application Migration populates the value for this field. Do not change this value.
    • System Database Administrator Password: Set a password for the SYS database administrator.

      The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters. The special characters must be _, #, or -. The password must not contain the username (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.

    • SSH Key: Upload or paste the public SSH key that you'll use to connect to the migrated instance and database in the target environment.
    • WebLogic Administrative User: Enter the name of the WebLogic administrator user for the target service instance.
    • WebLogic Administrative Password: Set the password for the WebLogic administrator for the target service instance.

      The password must start with a letter, is between 8 and 30 characters long, contain at least one number, and, optionally, any number of the special characters ($ # _).

    • Cloud Storage Container for SOACS Backups: Enter the path to an existing Oracle Cloud Infrastructure Object Storage bucket or container which you want to use to provide storage for your Oracle SOA Cloud Service instance backups. Use the following URL form to specify the bucket:
      https://swiftobjectstorage.<region>.oraclecloud.com/v1/<ObjectStorageNamespace>/<container>

      For example:

      https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/acme/mycontainer

      See Object Storage Service API.

      Note

      Do not use the same bucket for each service instance.

      Ensure that you meet the prerequisites when you create the bucket. See Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure.

    • Cloud Storage User: Enter the username, who has the required permissions, to access Oracle Cloud Infrastructure Object Storage.

      If your tenancy is federated with Oracle Identity Cloud Service, provide the username in the format: tenancy-name/oracleidentitycloudservice/username. Otherwise, use the format: tenancy-name/username. Where, the tenancy-name is the name of the tenancy where you want to create the Oracle SOA Cloud Service instance and the username that you specify has access to the tenancy.

    • Cloud Storage Auth Token: Enter the authentication token generated for the Oracle Cloud Infrastructure Object Storage user. See Getting an Auth Token.
    • PaaS Administrator Username: Enter the name of the user who has the SOA_Administrator service entitlement in the target environment. Application Migration uses these credentials to access Oracle PaaS Service Manager, create an instance, and then import the application artifacts to Oracle Cloud Infrastructure.
    • PaaS Administrator Password: Enter the password for the specified user.
    • PaaS Target Identity Domain: 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, and has the format idcs-string-of-letters-and-numbers (for example, idcs-98888f7964454b658ac6d2f625b29030).

      You need to specify a value for this field only if you are migrating your applications to an Oracle Cloud Infrastructure region that isn't in your geographical home region. See Considerations.

  6. Click Configure to return to the Configure Migration page.
  7. Review the information you've provided. When you're ready, click Save and Run to start the migration immediately.
  8. When prompted for confirmation, click Start.
Example for ConfigurationField Reference

This is an example of the values you can provide for the serviceConfig field while migrating an Oracle SOA Cloud Service application to Oracle Cloud Infrastructure.

{
  "configuration": {
    "serviceConfig": {
      "CloudStorageContainerSOA": {
        "description": "Object storage Bucket path or Container for storing Oracle SOA Cloud Service instance backups",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Cloud Storage Container for SOACS Backups",
        "isRequired": true,
        "type": "text",
        "value": ""
      },
      "CloudStoragePassword": {
        "description": "Auth token generated on Oracle Cloud Infrastructure for theObject Storage user",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Cloud Storage Password",
        "isRequired": true,
        "type": "password",
        "value": "*******"
      },
      "CloudStorageUser": {
        "description": "User name for the Oracle Cloud Infrastructure Object Storage user",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Cloud Storage User",
        "isRequired": true,
        "type": "user_name",
        "value": ""
      },
      "WeblogicAdminPassword": {
        "description": "Weblogic Admin Password",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Weblogic Admin Password",
        "isRequired": true,
        "type": "password",
        "value": "******"
      },
      "WeblogicAdminUser": {
        "description": "Weblogic Admin User",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "WebLogic Admin User",
        "isRequired": true,
        "type": "user_name",
        "value": "weblogic"
      },
      "availabilityDomain": {
        "description": "Availability Domain",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Availability Domain",
        "isRequired": true,
        "type": "ad",
        "value": "HeYD:US-ASHBURN-AD-1"
      },
      "soacsDBPassword": {
        "description": "Database Password (used by SYS, SYSTEM, and PDB Admin)",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Database Password",
        "isRequired": true,
        "type": "password",
        "value": "*******"
      },
      "soacsDBUser": {
        "description": "Database User",
        "group": "Target SOA Cloud Service",
        "isMutable": false,
        "name": "Database User",
        "isRequired": true,
        "type": "user_name",
        "value": "SYS"
      },
      "soacsPublicKey": {
        "description": "Authorize this Public Key for the DB and SOACS instances",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Public Key",
        "isRequired": true,
        "type": "text",
        "value": ""
      },
      "psmIdentityPassword": {
        "description": "PaaS Administrator Password",
        "group": "PSM",
        "isMutable": true,
        "isRequired": true,
        "name": "PaaS Administrator Password",
        "type": "password",
        "value": "xxxxxxx"
      },
      "psmIdentityUser": {
        "description": "PaaS Administrator Username",
        "group": "PSM",
        "isMutable": true,
        "isRequired": true,
        "name": "PaaS Administrator Username",
        "type": "user_name",
        "value": "psm_username"
      },
      "subnetId": {
        "description": "Subnet ID",
        "group": "Target SOA Cloud Service",
        "isMutable": true,
        "name": "Subnet ID",
        "isRequired": true,
        "type": "subnet",
        "value": "ocid1.subnet.oc1.iad.unique_id"
      }
    }
  }
}

Next: If the application is successfully migrated, a confirmation message is displayed. After the application is migrated to the target environment, complete the post-migration tasks.

If the migration fails, the status of the migration changes to Migration failed and the status of the migrate application work request is Failed. Click the Migrate Application work request to view the logs and errors to identify the issues. After resolving the issues, you can start the migration.

Complete Post-Migration Tasks

After a migration completes successfully, ensure that you validate the behavior of the application in terms of its business logic and complete other post-migration tasks. See Complete the Post-Migration Tasks.

Application Migration discovers the connection details for WebLogic JDBC data source and foreign JNDI provider that are associated with the application in the source environment. After migrating the application, you must validate the connections because these connections might not be accessible from the new environment.