4 Post-Migration

After successfully migrating your Oracle Java Cloud Service instances to Oracle WebLogic Server for OCI, perform the following post-migration tasks:

  • If you were using custom SSL certificates on Oracle Traffic Director (OTD), then set up SSL certificates on the OCI Load Balancer.
  • If you use a hosting provider to manage DNS make sure to reset the CNAME records at your hosting provider to point to the new IP addresses of the OCI load balancer and WebLogic VMs.
  • Verify that all the deployed applications are functioning as expected.

    If you have enabled Oracle WebLogic Server Administration Console communication, verify that you can access the WebLogic Server Administration Console. If your instance includes custom data sources that access your application databases, you can test database connectivity directly from the WebLogic Server Administration Console. Select a data source, click the Monitoring tab, and then click the Testing tab.

  • It is recommended that you stop your Oracle Java Cloud Service instance using the Oracle Java Cloud Service console. With the instance stopped you will not be charged for the Oracle Java Cloud Service instance. If you discover any issues with the Oracle WebLogic Server for OCI set up you can always switch back to the Oracle Java Cloud Service by starting it up again. See Before You Begin with Oracle WebLogic Server for OCI.
  • After monitoring the migrated Oracle WebLogic Server for OCI for a few days or weeks, if your applications are all running as expected, you should delete your Oracle Java Cloud Service instance. See Delete an Oracle Java Cloud Service Instance.
  • If you migrated your Oracle Java Cloud Service instance to Oracle WebLogic Server for OCI, and the WebLogic Server version that you migrated is 12.2.1.2 or 12.2.1.3, you must upgrade the WebLogic Server versions post-migration.
    • If the WebLogic Server version is 12.2.1.3, see Upgrade a Domain in Using Oracle WebLogic Server for OCI.
    • If the WebLogic Server version is 12.2.1.2, see Upgrade a Domain.