Oracle Cloud Infrastructure Documentation

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 an application to an existing target instance, then you might have completed some of the following steps 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 the 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 an 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 the 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 an application, you must manually migrate Oracle Platform Security Services policies and keystores. See Move OPSS Data for more information.

  2. If the 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 might 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 other post-migration tasks as discussed in Complete the Post-Migration Tasks.