Migrate Oracle SOA Cloud Service

Migrate Oracle SOA Cloud Service application to a new or existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure.

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.

Plan the Migration

Ensure that you complete the prerequisites to set up and use Classic Migration Service. See Before You Begin. Additionally, complete the following tasks before you migrate Oracle SOA Cloud Service applications to 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 the service type, version, and number of nodes, which is information you need to plan your migration.

  • Service Type: Oracle SOA Cloud Service includes three service types: Business Activity Monitoring, Managed File Transfer (MFT) Cluster, and SOA with SB & B2B Cluster. Classic Migration Service supports the migration of Oracle SOA Cloud Service applications that have either the MFT Cluster or SOA with SB & B2B Cluster service type. You cannot use Classic Migration Service to migrate Oracle SOA Cloud Service applications that have the Business Activity Monitoring service type.
  • Public or private subnet: Choose whether you want your target instance to be created in a public or private subnet. When the target instance is in a public subnet, you can send your network traffic over the internet.

    When your target instance is in a private subnet, 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.

  • New or existing target instance: Choose whether you want to use Classic Migration Service to migrate your application to an existing target instance or create a target instance in Oracle Cloud Infrastructure.

    If you are using Classic Migration Service to create a target instance and migrate your application, then Classic Migration Service creates the target instance in a public subnet. It does not create the target instance in a private subnet.

    Note

    To migrate your application to a private subnet using Classic Migration Service, you must create Oracle SOA Suite on Marketplace in a private subnet and then use Classic Migration Service to migrate your application to the existing target instance.
  • Version: Ensure that Oracle SOA Cloud Service is at a supported version in the source environment.

    If your application is not at a supported version, then upgrade your application to a supported version and then use Classic Migration Service to migrate your application.

    The following table lists the versions of the source and target instance that Classic Migration Service supports. If you want to migrate your applications to an existing target instance, then use this information to create your target Oracle SOA Suite on Marketplace instance.

    Source Type Supported Versions in Source Environment Existing Target Version New Target Version
    Oracle SOA Cloud Service with SB & B2B Cluster
    • 12.2.1.2
    • 12.2.1.3
    • 12.2.1.4
    12.2.1.4

    Release version: 12.2.1.4

    Package version: 20.4.2

    Oracle SOA Cloud Service with MFT cluster

    Release version: 12.2.1.4

    Package versions:

    Release version: 12.2.1.4

    Package version: 20.4.2

    Classic Migration Service supports only 12.2.1.4 version with package version 20.3.3 in the target environment. If your application is at a supported version, such as 12.2.1.3 in the source environment, then Classic Migration Service automatically upgrades it to version 12.2.1.4 as part of the migration process.

  • Metadata: Classic Migration Service supports migration of the following metadata for Oracle SOA Cloud Service with SB & B2B Cluster:

    • LDAP data: LDAP data includes the Oracle WebLogic Server specified user, group, enterprise role, and security policies (predefined Oracle WebLogic configurations and configurations that users have added to internal LDAP). If you are migrating to an existing target instance, then any existing LDAP configuration data on the target instance is overwritten.
    • OWSM policies: If you are migrating to an existing target instance, then any existing custom OWSM policies on the target instance are overwritten.
    • Common resource configurations:
      • Custom JDBC system resources
      • Foreign JNDI providers
      • File stores
      • JDBC stores
      • JMS servers
      • JMS system resources or JMS modules
      • Resource adapters

      When you are migrating to an existing target instance and the resource already exists, Classic Migration Service does not import that resource.

    • Oracle Enterprise Scheduler metadata: Classic Migration Service migrates the metadata for the EssNativeHostingApp and ESSAPP applications. The metadata includes job definitions, schedules, and job requests. If you are migrating to an existing target instance, then any existing Oracle Enterprise Scheduler metadata on the target instance is overwritten.
      Note

      • Classic Migration Service migrates job requests to the target instance but does not submit the job requests immediately. Classic Migration Service generates a script that you must run when the target SOA instance is ready for production use. The script includes only the job requests that have non-recurring schedules. You must migrate job requests with a recurring schedule, manually. See Complete Post-Migration Tasks for instructions to run this script.

      • Using Classic Migration Service to migrate Oracle Enterprise Scheduler metadata does not migrate shared artifacts, if any exist. Instead, you must migrate this information, manually. See Application Export Commands for information about exporting the shared artifacts and Import Application Metadata for information about importing the metadata.
    • B2B metadata: If you are migrating to an existing target instance, then any existing B2B metadata on the target instance is overwritten.
    • Oracle Service Bus (OSB) project data: If you are migrating to an existing target instance, then any existing Oracle Service Bus project data on the target instance is overwritten.
    • SOA composite application data: Includes SOA projects, applications, partitions, SOA infrastructure metadata, and token configuration.

      If you are migrating to an existing target instance, then any existing data on the target instance is overwritten, with the exception of the default partition, which is named partition. The default partition is not overwritten, but the composites contained in the default partition are overwritten.

    Classic Migration Service supports the migration of following metadata for Oracle SOA Cloud Service with MFT cluster:

    • Oracle Web Services Manager (OWSM) policies: If you are migrating to an existing target instance, then any existing custom OWSM policies on the target instance are overwritten.
    • MFT configuration data (including keystores and keys): If you are migrating to an existing target instance, then any existing data on the target instance is overwritten.
    • LDAP data: LDAP data includes the Oracle WebLogic Server-specified user, group, and enterprise role and security policies (predefined Oracle WebLogic configurations and configurations that users have added to internal LDAP). If you are migrating to an existing target instance, then any existing LDAP configuration data on the target instance is overwritten.
    • Oracle Platform Security Services data: Credentials store, Oracle Platform Security Services policies, and keystores. Credentials store includes Credential Store Framework keys.

      While migrating Oracle SOA Cloud Service with MFT cluster, Classic Migration Service migrates the credentials but does not migrate Oracle Platform Security Services policies and keystores. After migrating your application, you must manually migrate Oracle Platform Security Services policies and keystores.

      If you are migrating Oracle Platform Security Services credentials to an existing target instance, then any existing data on the target instance is overwritten.

      If you are migrating to an existing instance in Oracle Cloud Infrastructure, then migrate Oracle Platform Security Services policies and keystores to the existing target instance before migrating the application. If you are migrating to a new instance, then you can migrate the Oracle Platform Security Services policies and keystores after migrating the application.

    If your source environment contains Oracle Platform Security Services data, then Classic Migration Service does not migrate the data. After migrating your application, you must manually migrate Oracle Platform Security Services data.

  • Nodes: Determine the number of nodes that the Oracle SOA Cloud Service application contains in the source environment.

    If you are using Classic Migration Service to automatically create an instance in the target environment and migrate your application, then Classic Migration Service detects the number of nodes that are available in the source application and automatically creates an instance with the same number of nodes in the target environment.

    If you are migrating a multi-node Oracle SOA Cloud Service application to an existing target instance, then ensure that the target instance also has multiple nodes. The following table provides details about the required mapping between the node types of the source and target instances.

    Node Type of Source Instance Node Type of Target Instance
    Single Single
    Multi-node Multi-node
    Multi-node with Oracle Traffic Director Multi-node with Oracle Cloud Infrastructure Load Balancing service, if your target instance is Oracle SOA Suite on Marketplace
    Multi-node with Oracle Traffic Director Multi-node with Oracle Traffic Director, if your target instance is Oracle SOA Cloud Service

    If your application contains a single node, then ensure that you can SSH to that node. If your application contains multiple nodes, then ensure that the SSH ports to the managed servers and the Oracle WebLogic Administration Server are open.

  • Database: If you are using Classic Migration Service to automatically create a database instance in the target environment and migrate your application, then Classic Migration Service creates an Oracle Cloud Infrastructure database instance. If you are using Classic Migration Service to migrate your application to an existing Oracle SOA Suite on Marketplace instance in the target instance, then you can associate an existing Oracle Cloud Infrastructure database or an Oracle Autonomous Transaction Processing database instance with the target instance. For information about creating a database, see Create an Oracle Database for Oracle SOA Suite on Marketplace. To configure the existing target database, see Configure the Database.
  • Licensing: When you migrate your application to Oracle SOA Suite on Marketplace, Classic Migration Service discovers the licensing type of the source instance and creates the target instance with the same licensing type. If the B2B adapter is enabled on the source instance, then Classic Migration Service creates the target instance with a paid license even when you have BYOL in the source environment.

Next: After planning your migration, provide information about the source environment to create a Classic Migration Service source.

Prepare the Target Environment

Prepare to migrate to a new Oracle SOA Suite on Marketplace instance

In Oracle Cloud Infrastructure, identify a compartment where you want to migrate your application. The compartment must contain a VCN and at least one subnet. To create a compartment, see Design the Oracle Cloud Infrastructure Network.

Prepare to migrate to an existing Oracle SOA Suite on Marketplace target instance

Before you migrate an Oracle SOA Cloud Service Classic instance to an Oracle Cloud Infrastructure region, you must create the required infrastructure and database resources.

  1. Identify an existing Oracle SOA Suite on Marketplace instance in Oracle Cloud Infrastructure or create an instance to host the application that you want to migrate. To create an Oracle SOA Suite on Marketplace instance, see Provision an Oracle SOA Suite on Marketplace Instance.
  2. Identify the number of nodes in the source instance. The target instance must have the same number of nodes as the source instance.
  3. The existing target instance must be connected to a database in Oracle Cloud Infrastructure. Ensure that the database and the instance are in the same subnet in Oracle Cloud Infrastructure. For details about creating a database that is associated with an Oracle SOA Suite on Marketplace instance in the target environment, see Create an Oracle Database for Oracle SOA Suite on Marketplace.
  4. Ensure that the target instance is available and is in the running state when you migrate your application.
  5. Complete all the steps mentioned in Before You Migrate Using the Application Migration Service.

Create a Source

Before you create a source, ensure that you select the correct region in Oracle Cloud Infrastructure Console. This is the target region to which you want to migrate the application. For example, if you selected Australia South (Melbourne) as your region in Oracle Cloud Infrastructure Console, then you can migrate from certain Oracle Cloud Infrastructure Classic regions to Oracle Cloud Infrastructure region, Australia South (Melbourne). In the preceding example, you cannot migrate from US- East, Oracle Cloud Infrastructure Classic region, to Australia South (Melbourne), Oracle Cloud Infrastructure region. When you create a source, the Region drop-down list displays only those Oracle Cloud Infrastructure Classic regions from which you can migrate applications to the current region that you have selected in Oracle Cloud Infrastructure Console.
  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Choose a compartment from the Compartment drop-down in which you have permission to work. The page updates to display only the resources in that compartment. If you are not sure which compartment to use, then contact an administrator. For more information, see Access Control.
  3. Click the Create Source button.
  4. Enter the following 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.
    • From the Source type drop-down, select one of the following and provide the corresponding information:
      • Oracle Cloud Infrastructure - Classic

        Account: The name of your Oracle Cloud Infrastructure Classic account.

        Region: Select the Oracle Cloud Infrastructure Classic region from which you want to migrate your application. Only the source regions and legacy zones from which you can migrate your applications using Classic Migration Service display. If you do not see a source region where your Oracle Cloud Infrastructure Classic account exists, then create a service request using My Oracle Support.

        Choose an authentication method, either Access token (the more secure choice) or User credentials. If you select Access token, then you must provide a client-specific URL endpoint and an OAuth access token for the PaaS Service Manager application.

        If you select User credentials, then you must provide the service administrator username and password.

      • Internal Compute

        Account: The name of your Oracle Cloud Infrastructure Classic account.

        Provide the service administrator username and password.

      • Oracle Cloud@Customer

        Account: Enter the service instance ID for your Oracle Cloud@Customer with Identity Cloud Service account.

        Provide the service administrator username and password.

      • Imported

        To create an imported source, you must use the export tool to create a file containing the application you want to migrate, and then upload the file to the Console. See Classic Migration Service Export CLI Tool for more information about the export tool.

        Select the bucket that contains the source information. Click the Change Compartment link to select the compartment that contains the required bucket, if necessary.

    • Tags: Optionally, you can add tags. If you have permissions to create a resource, then 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, then 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. Classic Migration Service 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 Classic Migration Service 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.

If the source is in the active state, then 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, then you must perform corrective actions. See To view a list of applications.

If the source is in the inactive state, then click the Create Source work request to view the logs and errors to identify the issues. For example, you must 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. Provide the credentials of the service administrator in the source environment. Classic Migration Service uses this information to access the application and discover application artifacts and dependencies, such as the Oracle WebLogic Server domain configuration and its data sources.

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Choose a compartment from the Compartment drop-down in which you have permission to work. The page updates to display only the resources in that compartment. If you are not sure which compartment to use, then contact an administrator. For more information, see Access Control.
  3. Click the Create Migration button to display the Create Migration dialog.

    Alternatively, you can access the Create Migration dialog from the details page of a source that contains the application that you want to migrate.

    Note

    You can migrate applications only from a source that is in the Active state.
    1. On the source details page, display a list of applications for the source by clicking Applications in the Resources section.
    2. Click the ellipsis at the end of the row containing the application that you want to migrate.
    3. Click Create Migration.
      Note

      Some fields are filled in, by default, on the Create Migration page, when you choose this workflow.
  4. On the Create Migration page, enter the following information:
    • In the Migration Name field, enter a user-friendly name for the migration.
    • Optionally, enter a description in the Description field to help you identify the application being migrated.
    • Application Administrator Username: Enter the Oracle WebLogic administrator username. This user must have the service administrator role in the source environment.
    • If applicable, then provide an Application Administrator Username and an Application Administrator Password in their respective fields.
    • Select either Oracle SOA Cloud Service or Oracle SOA Suite on Marketplace in the Target Instance Type section.
    • If the target instance exists, then select Use Existing Target Instance section.
    • Tags: Optionally, you can add tags. If you have permissions to create a resource, then 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, then skip this option (you can apply tags later) or ask your administrator.

  5. Click Create to create the migration.

Use the Configure Migration wizard to provide information about the target environment. You can initiate the process to migrate an application using Classic Migration Service 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 an 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 an 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 the Resource Manager stack OCID of the target instance. You must provide this information to configure the migration.
    1. Open the Oracle Cloud Infrastructure Console navigation menu and click Developer Services. In the Resource Manager section, click Stacks.
    2. Select the compartment that contains the target stack to which you want to migrate your application.
    3. Click the name of the stack to view the detail page for that stack and then copy the OCID of the stack.
  • Create a secret that contains the private SSH key.

    Before creating the target instance, you must first create an SSH public/private key pair. While creating the target instance, you provide 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 you create the secret, copy the OCID of the secret because it is required to configure 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 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. If necessary, then select the compartment from the Compartment drop-down 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:
    • Oracle WebLogic Server Administrator User Name: Enter the name of the Oracle WebLogic administrator user for the existing target instance.
    • WebLogic Server Admin Password: Enter the password for the specified user in plain-text format.
    • Target Service Name: Enter the existing Oracle SOA Cloud Service target instance name.
    • PaaS Administrator Username: Enter the username of a PaaS administrator who has access to the target Oracle Analytics Cloud instance in Oracle Cloud Infrastructure. Ensure that the user is assigned the AUTONOMOUS_ANALYTICS_ServiceAdministrator and AUTOANALYTICS_APPID_ROLE roles.
    • Name of the Secret OCID for PaaS Administrator Password in compartment: Select the secret in Oracle Cloud Infrastructure that contains the password for the specified PaaS administrator. Click the Change Compartment link to change compartments, if necessary.
    • Secret OCID for PaaS Administrator Password: Enter the OCID of the secret that contains the password for the specified PaaS administrator in Oracle Cloud Infrastructure. If you have already selected the name of the secret in the Name of the Secret OCID for PaaS Administrator Password field, then the OCID of the selected secret displays.
    • PaaS Identity Domain: Optionally, enter the PaaS Service Manager identity domain associated with the account.
  5. Review the information you provided. Click Save and Run to start the migration.
  6. When prompted for confirmation, click Start.
Example for serviceConfig Field 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, Classic Migration Service creates an 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, then Classic Migration Service creates an Oracle Cloud Infrastructure database system. To name the database system, Classic Migration Service appends db to the name of the application. For example, if you want to migrate an Oracle SOA Cloud Service application named MyApp in the source environment, then Classic Migration Service 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 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. If necessary, then select the compartment from the Compartment drop-down 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:

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.

Example for serviceConfig Field 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
      }
    }
  }
}

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.

Complete Post-Migration Tasks

After a migration completes successfully, complete the post-migration tasks.

Classic Migration Service discovers the connection details for the Oracle WebLogic JDBC data source and the foreign Java Naming and Directory Interface (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.

If you have migrated your application to an existing target instance, then you may have completed some of the steps listed below as part of the prerequisites, in which case, you do not have to perform the steps again. For example, if you have already migrated Oracle Platform Security Services data manually to the target before starting the migration, then you do not have to repeat that procedure while performing the post-migration tasks.

  1. If your source environment is Oracle SOA Cloud Service with SB & B2B Cluster and it contains Oracle Platform Security Services data, then Classic Migration Service does not migrate the Oracle Platform Security Services data. After migrating your application, you must manually migrate Oracle Platform Security Services data. See Move OPSS Data for more information.

    Oracle Platform Security Services data consists of credentials, Oracle Platform Security Services policies, and keystores. If your source environment is Oracle SOA Cloud Service with MFT cluster and it contains Oracle Platform Security Services data, then Classic Migration Service migrates the credentials but does not migrate the Oracle Platform Security Services policies and keystores. After migrating your application, you must manually migrate Oracle Platform Security Services policies and keystores. See Move OPSS Data for more information.

  2. If your source environment is Oracle SOA Cloud Service with SB & B2B Cluster and it contains SOA composite application data, then Classic Migration Service migrates the SOA composite application data. SOA composite application data includes SOA projects, applications, partitions, SOA infrastructure metadata, and token configuration.

    After migrating the application, ensure that the migrated token configuration values are compatible with the target environment. If the migrated token values are not compatible, then update the token values in the target environment.

    Composites that use token configuration or a configuration plan that is specific to the source environment may not be migrated successfully to the target environment. Check the value of the token configuration and configuration plan in the target environment, update the values if required, and deploy the composite again to target.

  3. If the source instance included scheduled Oracle Enterprise Scheduler job requests, then Classic Migration Service creates a script to migrate the job requests to the target instance. If this script is not present on the target instance (in the location specified in the following procedure), then skip this step.
    Run the script, as follows:
    1. Use SSH to log into the target SOA instance VM.
    2. Change the user to oracle.
    3. Locate the submit_job_requests.py script in the /u01/soamig/date_time_stamp/import/ess directory. You can find the directory path, too, in the Ansible-import.log file included in the log of the migration job request in the Console. (Search for submit_job_requests.py in the Ansible-import.log file.)
    4. Update the script to replace password in the connect() command with your Oracle WebLogic Server administrator user password in plain text.
    5. Run the script:
      /u01/app/oracle/middleware/oracle_common/common/bin/wlst.sh submit_job_requests.py
    6. After all the jobs are submitted successfully and verified in the Enterprise Manager console, delete the script.
  4. After migrating to Oracle SOA Cloud Service with MFT cluster, you must tune MFT parameters to optimize performance. See Tuning MFT Parameters.
  5. Configure User Messaging Service in the target environment. See Configuring User Messaging Service Drivers.
  6. Ensure that you validate the behavior of the application in terms of its business logic and complete all post-migration tasks. See Complete the Post-Migration Tasks.