Oracle Cloud Infrastructure Documentation

Migrate Oracle Java Cloud Service

Migrate Oracle Java Cloud Service applications from Oracle Cloud Infrastructure Classic and Oracle Cloud@Customer to an existing or new Oracle WebLogic Server for Oracle Cloud Infrastructure instance.

For information about Oracle WebLogic Server for Oracle Cloud Infrastructure, see About Oracle WebLogic Server for Oracle Cloud Infrastructure.

Caution

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

Plan the Migration

In the Oracle Java Cloud Service web console in the source environment, click an instance name to view instance details, and then note down the release version and number of nodes. You must have this information to plan your migration.

  • Version: Identify the software release version of the source Oracle Java Cloud Service application. Classic Migration Service supports migrating source applications that have Oracle Java Cloud Service release 16.4.5, or later, and Oracle WebLogic Server at a supported release version.

    To migrate to an Oracle WebLogic Server for Oracle Cloud Infrastructure instance, ensure that the Oracle WebLogic Server of the source application is at release 12.2.1.4.

    If Classic Migration Service does not support the Oracle Java Cloud Service version, then the application status displays as Unsupported on the Source details page.

    You must upgrade your application to a supported release version and then use Classic Migration Service (or another tool) to migrate the application. To identify other migration tools that you can use to migrate Oracle Java Cloud Service applications, see About the Migration Tooling. For information about upgrading your Oracle Java Cloud Service instance to a supported release, see About Upgrading the WebLogic Server Release for an Oracle Java Cloud Service Instance.

  • Existing or new target instance: Choose whether you want to migrate your application to an existing instance or create a new instance in the target environment.

    If you want to use Classic Migration Service to migrate your application to a private subnet, then you must create a new instance in a private subnet in the target environment and then use Classic Migration Service to migrate your application to the existing target instance.

  • Existing or new target database instance: Choose whether you want to use an existing database in the target environment or use Classic Migration Service to automatically create a database in the target environment.

Next: Gather information about the source environment.