Configure Classic Migration Service and Migrate to Oracle SOA Cloud Service

Migrating to a New Oracle SOA Suite on Marketplace Instance

• Console
• CLI
• API

• 1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Migrations in the Classic Migration section to display the Migrations in compartment page and a list of migrations.
  2. Select the compartment from the Compartment menu that contains the migration that you want to configure.
  3. From the list of migrations, click the ellipsis at the end of the row containing your migration and click Configure to display the Configure Migration page for your migration.

     Alternatively, click the name of your migration from the list of migrations on the page to display the details page for that migration. Click the Configure button to display the Configure Migration page.

  4. In the Configure Service section, click Edit and enter the following information:
     • Availability Domain: Select the availability domain where you want to create the service instance that hosts the migrated application.
     • Select Virtual Cloud Network in compartment: Select the VCN where you want to create the service instance that hosts the migrated application. Click the Change Compartment link to select a different compartment.
     • Subnet: Select the public subnet where you want Classic Migration Service to create the target instance that hosts the migrated application.
     • System Database Administrator Username: The SYS database administrator. Provide this username while accessing the Oracle Cloud Infrastructure database system that is created in the target environment. Classic Migration Service 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 in length 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 user name (SYS, SYSTEM, and so on) or the word oracle either in forward or reversed order and regardless of casing.

     • Add SSH Public Key: Upload an SSH public key file or paste the SSH public key that you use to connect to the migrated instance and database in the target environment. Click the corresponding radio button, depending on your choice.
     • WebLogic Administrative User: Enter the name of the Oracle WebLogic administrator user for the target service instance.
     • WebLogic Administrative Password: Set the password for the Oracle WebLogic administrator for the target service instance.

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

  5. Click Configure to return to the Configure Migration page.
  6. Review the information you provided. Click Save and Run to start the migration.
  7. When prompted for confirmation, click Start.

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

  • View Oracle SOA Suite Instance Details
  • Access an Oracle SOA Suite Instance

  If the work request indicates that the stack creation failed, then 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, then 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.

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

  If the migration fails, then 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.

• Use the migrate-application command and required parameters to migrate the application:

  oci application-migration migration migrate-application [OPTIONS]

  For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

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

  If the migration fails, then 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.

• Run the MigrateApplication operation to migrate the application.

  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
        }
      }
    }
  }

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

  If the migration fails, then 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.