1 Learn About Migrating to Oracle Cloud Infrastructure

These topics help you learn about the benefits to migrating your existing Oracle Java Cloud Service instances to Oracle Cloud Infrastructure, and also provide an overview of the migration process and tools.

Topics:

• Why Migrate to Oracle Cloud Infrastructure
• About the Migration Scope
• About Oracle WebLogic Server for Oracle Cloud Infrastructure
• Compare Oracle Cloud Infrastructure to Classic
• About Oracle Cloud Infrastructure Users and Groups
• About the Migration Task Flow
• About the Migration Tooling

Why Migrate to Oracle Cloud Infrastructure

Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions. You can gain several advantages by doing so.

In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations. Certain regions support the Oracle Cloud Infrastructure platform.

Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards. It provides more consistent performance and better features at lower costs. Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features. See Data Regions for Platform and Infrastructure Services.

You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure:

• Organize cloud resources into a hierarchy of logical compartments.
• Create fine-grained access policies for each compartment.

Oracle WebLogic Server for OCI allows you to quickly provision a WebLogic domain in Oracle Cloud Infrastructure and at the same time provides you the flexibility to customize your WebLogic domain. It also offers the following advantages over Oracle Java Cloud Service:

• Supports WebLogic Server major release versions after 12.2.1.4.0.
• Offers flexibility to add or remove patches.
• Allows managing the operating system or domain after provisioning, without any restrictions.
• Allows choosing any supported method to backup, scale, or patch a domain.
• Allows full customization of the Oracle-managed load balancer.
• Supports cloning instances.
• Includes optional autoscaling feature.
• Supports a documented disaster recovery process. See Oracle WebLogic Server for Oracle Cloud Infrastructure Disaster Recovery.
• Allows WebLogic Server domains without Java Required Files (JRF).
• Integrates with multiple Oracle Cloud Infrastructure services to monitor, trace, deploy, scale and autoscale your WebLogic domain, and other Oracle Cloud Infrastructure services to manage and patch your WebLogic domain resources.
• Offers the option to pay per OCPU/Hour for Oracle WebLogic Server for OCI images with the entitlement to install any Oracle WebLogic Server version.

To learn more, see Upgrade Your Classic Services to Oracle Cloud Infrastructure.

About the Migration Scope

Before you migrate your existing Oracle Java Cloud Service instances to Oracle Cloud Infrastructure, ensure that the service instance meets the prerequisites for the migration.

Oracle does not currently support the migration of Oracle Java Cloud Service instances that meet any of these conditions:

• The service instance includes multiple domain partitions.
• The service instance is running Oracle WebLogic Server 11g and includes Java Message Service (JMS) migratable targets.

This guide does not include detailed procedures on the configuration of basic Oracle Cloud Infrastructure security, network and storage resources that might be required to support your new WebLogic Server domain. Instead, this guide provides references to the Oracle Cloud Infrastructure documentation as appropriate.

Most service instances connect to one or more databases in order to access your application schemas. This guide does not include the detailed procedure for migrating these application databases from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure. One option is the Oracle Cloud Infrastructure Classic Database Backup Migration Tool, which uses Recovery Manager (RMAN). Another option is Oracle Data Guard. See Select a Method to Migrate Database Instances in Migrating Infrastructure Classic Workloads to Oracle Cloud Infrastructure.

About Oracle WebLogic Server for Oracle Cloud Infrastructure

Oracle WebLogic Server for Oracle Cloud Infrastructure is available as a set of applications in the Oracle Cloud Infrastructure Marketplace. After launching one of these applications, you use a simple wizard interface to configure and provision an Oracle WebLogic Server domain along with any supporting cloud resources like compute instances, networks and load balancers.

Note:

Oracle recommends migrating your existing domains in Oracle Java Cloud Service to Oracle WebLogic Server for Oracle Cloud Infrastructure.

After launching a domain using the Marketplace applications, you track and monitor its progress as a stack using Resource Manager in Oracle Cloud Infrastructure. A stack also provides a convenient method of deleting the cloud resources for a domain when you no longer require them.

Like Oracle Java Cloud Service, you can administer the domain and deploy Java EE applications to it just like on-premises domains. Use standard Oracle WebLogic Server tools like the administration console and WebLogic Scripting Tool (WLST). You can also administer the operating system on the compute instances using a secure shell (SSH) client and standard Linux tools.

The following table compares the functionality of Oracle Java Cloud Service to Oracle WebLogic Server for Oracle Cloud Infrastructure

Oracle Java Cloud Service	Oracle WebLogic Server for Oracle Cloud Infrastructure
Supports Oracle WebLogic Server 11g, 12.2.1.3, and 12.2.1.4 Also supports Oracle WebLogic Server 12.1.3	Supports Oracle WebLogic Server 11g, 12.2.1.3, and 12.2.1.4
Will not support major version new releases of Oracle WebLogic Server	Will support major version new releases of Oracle WebLogic Server
All domains include the Java Required Files (JRF) components and require a database	Create basic and JRF-enabled WebLogic Server 12c domains All WebLogic Server 11g domains are JRF-enabled and require a database
Must use Oracle Java Cloud Service to backup, scale, or patch a domain Certain changes to the operation system and domain are not supported (see Administration Best Practices)	Can choose any supported method to backup, scale, or patch a domain; the documentation provides recommendations and best practices No restrictions on changing the operating system or domain after provisioning
Can provision an Oracle-managed load balancer in Oracle Cloud Infrastructure, or a user-managed load balancer running Oracle Traffic Director	Can provision an Oracle-managed load balancer in Oracle Cloud Infrastructure
Limited customization of the Oracle-managed load balancer	Full customization of the Oracle-managed load balancer
Can use Oracle Identity Cloud Service for authentication A security application is created in Oracle Identity Cloud Service for each domain	Can use Oracle Identity Cloud Service for authentication Must create a confidential application in Oracle Identity Cloud Service prior to creating a domain Confidential application, enterprise application, and App Gateway are created in Oracle Identity Cloud Service for each domain

See About the Components of Oracle WebLogic Server for Oracle Cloud Infrastructure in Using Oracle WebLogic Server for Oracle Cloud Infrastructure.

Compare Oracle Cloud Infrastructure to Classic

This topic helps you get familiar with basic Oracle Cloud Infrastructure security, network, and storage concepts, and compare them to their equivalent concepts in Oracle Cloud Infrastructure Classic.

Cloud resources in Oracle Cloud Infrastructure are created in logical compartments. You also create fine-grained policies to control access to the resources within a compartment.

You create instances within an Oracle Cloud Infrastructure region. You also specify an availability domain (AD), if supported in the selected region. Oracle Cloud Infrastructure Classic does not use availability domains.

A virtual cloud network (VCN) is comprised of one or more subnets, and an instance is assigned to a specific subnet. In Oracle Cloud Infrastructure Classic, you assign instances to IP networks or the shared network. Typically, you create one subnet for the shared network, and create a separate subnet for each IP network in Oracle Cloud Infrastructure Classic. Note that unlike Oracle Cloud Infrastructure Classic, Oracle Cloud Infrastructure does not allow you to reserve IP addresses for platform services.

A subnet's security lists permit and block traffic to and from specific IP addresses and ports. In Oracle Cloud Infrastructure Classic, an instance's access rules provide similar capabilities, although security lists are configured at the subnet level.

Instances can communicate with resources outside of Oracle Cloud by using Oracle Cloud Infrastructure FastConnect, which provides a fast, dedicated connection to your on-premises network. This service is equivalent to Oracle Cloud Infrastructure FastConnect Classic. Alternatively, use IPSec VPN in Oracle Cloud Infrastructure as a replacement for VPN as a Service (VPNaaS) or Corente in Oracle Cloud Infrastructure Classic.

A bucket in Oracle Cloud Infrastructure Object Storage can be used to store files and share them with multiple instances. A user's generated authentication token (auth token) is required to access the bucket. Oracle Cloud Infrastructure Object Storage Classic provides the same service in Oracle Cloud Infrastructure Classic, but does not use auth tokens.

To learn more, see Key Concepts and Terminology in the Oracle Cloud Infrastructure documentation.

You can create rules that automatically scale an Oracle Java Cloud Service instance that's running in Oracle Cloud Infrastructure Classic. You must scale instances in Oracle Cloud Infrastructure manually.

About Oracle Cloud Infrastructure Users and Groups

Use the Identity and Access Management (IAM) system in Oracle Cloud Infrastructure to manage users, groups, and policies.

For example, the following Oracle Cloud Infrastructure policy grants members of the group MyGroup all privileges to all resources in the compartment MyCompartment:

Allow group MyGroup to manage all-resources in compartment MyCompartment

By default, this system is also configured to use Oracle Identity Cloud Service as a federated identity provider. Therefore, when you define policies in Oracle Cloud Infrastructure, you can reuse existing users and groups in Oracle Identity Cloud Service. You can either add users to a new group in Oracle Cloud Infrastructure, or map an existing Oracle Identity Cloud Service group to an Oracle Cloud Infrastructure group.

While policies control access to resources and services in Oracle Cloud Infrastructure, administrator roles control access to platform services. Assign Oracle Identity Cloud Service users and groups to administrator roles in order to grant them access to platform services.

• Common Policies in the Oracle Cloud Infrastructure documentation
• Federating with Oracle Identity Cloud Service in the Oracle Cloud Infrastructure documentation
• Add Users, Assign Policies and Roles in Getting Started with Oracle Cloud

About the Migration Task Flow

Get an overview of the process that you use to migrate your existing Oracle Java Cloud Service instances to Oracle Cloud Infrastructure.

The process varies depending on the target service and the selected tools.

• Migrate to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Application Migration Service
• Migrate to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Classic Tools
• Migrate to Java Cloud Service Using Application Migration Service
• Migrate to Java Cloud Service Using Classic Tools

Migrate to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Application Migration Service

Use Application Migration in Oracle Cloud Infrastructure to migrate service instances to Oracle WebLogic Server for Oracle Cloud Infrastructure.

Application Migration does not support the migration of WebLogic Server domains that include these types of resources:

• Custom Identity or Trust Keystore
• Foreign JNDI Provider
• Foreign JMS Server
• JMS Bridge Destination
• Storage-and-Forward (SAF) Context
• JavaMail Session
• WebLogic Diagnostic Framework (WLDF) REST Notification Endpoint

If your source Oracle Java Cloud Service instance uses these resource types, then Oracle recommends using the Oracle Cloud Infrastructure Classic Java Migration Tool instead of Application Migration. See Migrate to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Classic Tools.

The following diagram shows the migration topology for a Oracle Java Cloud Service instance using Application Migration. The migration target is a domain created with Oracle WebLogic Server for Oracle Cloud Infrastructure.

Description of the illustration jcs_diagram_migrate_wls_oci_ams.png

At a high level, the migration process is comprised of these tasks:

1. Prepare for the migration and perform any prerequisite tasks in Oracle Cloud Infrastructure.
2. Migrate any application databases in Oracle Cloud Infrastructure Classic regions to Oracle Cloud Infrastructure Database.
3. Use Application Migration to identify the source Oracle Java Cloud Service instance.
4. Use Application Migration to create and start a migration for the source Oracle Java Cloud Service instance.

   Application Migration exports the domain configuration and applications from your source instance, creates a database, creates a new domain with Oracle WebLogic Server for Oracle Cloud Infrastructure, and imports the domain configuration and applications to the target domain.

5. Test your applications on the target domain, and perform any other post-migration tasks.

See Migrate an Instance to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Application Migration Service.

Migrate to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Classic Tools

Use the Oracle Cloud Infrastructure Classic Java Migration Tool to migrate service instances to Oracle WebLogic Server for Oracle Cloud Infrastructure.

The following diagram shows the migration topology for a Oracle Java Cloud Service instance. The migration target is a domain created with Oracle WebLogic Server for Oracle Cloud Infrastructure.

Description of the illustration jcs_diagram_migrate_wls_oci.png

At a high level, the migration process is comprised of these tasks:

1. Prepare for the migration and perform any prerequisite tasks in Oracle Cloud Infrastructure.
2. Create an Oracle Cloud Infrastructure Database for the required infrastructure schemas, or use an existing Oracle Cloud Infrastructure Database.
3. Migrate any application databases in Oracle Cloud Infrastructure Classic regions to Oracle Cloud Infrastructure Database.
4. Create a migration controller instance, Control-S, in your Oracle Cloud Infrastructure Classic account. The Oracle Cloud Infrastructure Classic Java Migration Tool is installed on this compute instance.
5. Use the Oracle Cloud Infrastructure Classic Java Migration Tool to export the domain configuration, applications and other supporting files from your source Oracle Java Cloud Service instance.
6. Create the target domain using Oracle WebLogic Server for Oracle Cloud Infrastructure.
7. Use the Oracle Cloud Infrastructure Classic Java Migration Tool to import the domain configuration and applications to your target in Oracle Cloud Infrastructure.
8. Test your applications on the target instance, and perform any other post-migration tasks.

See Migrate an Instance to Oracle WebLogic Server for Oracle Cloud Infrastructure Using Classic Tools.

Migrate to Java Cloud Service Using Application Migration Service

Use Application Migration in Oracle Cloud Infrastructure to migrate service instances to Oracle Java Cloud Service on Oracle Cloud Infrastructure.

Application Migration does not support the migration of WebLogic Server domains that include these types of resources:

• Custom Identity or Trust Keystore
• Foreign JNDI Provider
• Foreign JMS Server
• JMS Bridge Destination
• Storage-and-Forward (SAF) Context
• JavaMail Session
• WebLogic Diagnostic Framework (WLDF) REST Notification Endpoint

If your source Oracle Java Cloud Service instance uses these resource types, then Oracle recommends using the Oracle Cloud Infrastructure Classic Java Migration Tool instead of Application Migration. See Migrate to Java Cloud Service Using Classic Tools.

The following diagram shows the migration topology for a Oracle Java Cloud Service instance using Application Migration. The migration target is a new Oracle Java Cloud Service instance.

Description of the illustration jcs_diagram_migrate_oci_ams.png

At a high level, the migration process is comprised of these tasks:

1. Prepare for the migration and perform any prerequisite tasks in Oracle Cloud Infrastructure.
2. Migrate any application databases in Oracle Cloud Infrastructure Classic regions to Oracle Cloud Infrastructure Database.
3. Use Application Migration to identify the source Oracle Java Cloud Service instance.
4. Use Application Migration to create and start a migration for the source Oracle Java Cloud Service instance.

   Application Migration exports the domain configuration and applications from your source instance, creates a database, creates the target Oracle Java Cloud Service instance, and imports the domain configuration and applications to the target instance.

5. Test your applications on the target instance, and perform any other post-migration tasks.

See Migrate an Instance to Oracle Java Cloud Service Using Application Migration Service.

Migrate to Java Cloud Service Using Classic Tools

Use the Oracle Cloud Infrastructure Classic Java Migration Tool to migrate service instances to Oracle Java Cloud Service on Oracle Cloud Infrastructure.

The following diagram shows the migration topology for a Oracle Java Cloud Service instance. The migration target is a new Oracle Java Cloud Service instance.

Description of the illustration jcs_diagram_migrate_oci.png

At a high level, the migration process is comprised of these tasks:

1. Prepare for the migration and perform any prerequisite tasks in Oracle Cloud Infrastructure.
2. Create an Oracle Cloud Infrastructure Database for the required infrastructure schemas, or use an existing Oracle Cloud Infrastructure Database.
3. Migrate any application databases in Oracle Cloud Infrastructure Classic regions to Oracle Cloud Infrastructure Database.
4. Create a migration controller instance, Control-S, in your Oracle Cloud Infrastructure Classic account. The Oracle Cloud Infrastructure Classic Java Migration Tool is installed on this compute instance.
5. Use the Oracle Cloud Infrastructure Classic Java Migration Tool to export the domain configuration, applications and other supporting files from your source Oracle Java Cloud Service instance.
6. Use the Oracle Cloud Infrastructure Classic Java Migration Tool and Terraform to create the target Oracle Java Cloud Service instance.
7. Use the Oracle Cloud Infrastructure Classic Java Migration Tool to import the domain configuration and applications to your target Oracle Java Cloud Service instance.
8. Test your applications on the target instance, and perform any other post-migration tasks.

See Migrate an Instance to Oracle Java Cloud Service Using Classic Tools.

About the Migration Tooling

You can use various tools to automate many of the tasks involved in migrating an Oracle Java Cloud Service instance to Oracle Cloud Infrastructure.

Oracle WebLogic Server Deploy Tooling is an open-source project. It provides scripts that enable you to discover and export the configuration and application files from one Oracle WebLogic Server domain, and then import the configuration and applications into another existing domain.

Oracle WebLogic Server Deploy Tooling exports a domain configuration as a metadata file, and automatically excludes sensitive information like passwords. When updating a domain, you also provide a metadata file. This file needs to describe only the resources that you want to add or update. If an application is already deployed, the tool compares the binaries and determines whether the application needs to be redeployed.

Application Migration Service provides a simple, graphical interface for migrating Oracle Java Cloud Service instances. It is available from the Oracle Cloud Infrastructure console. It automates the discovery of Oracle Cloud Infrastructure Classic resources in your account and the recreation of these resources in Oracle Cloud Infrastructure. Application Migration Service creates the target Oracle Java Cloud Service instance or Oracle WebLogic Server for Oracle Cloud Infrastructure domain, and creates the required database. It also automates the installation and execution of the Oracle WebLogic Server Deploy Tooling on the source and target domains.

The Oracle Cloud Infrastructure Classic Java Migration Tool is included in a custom compute image named Oracle Cloud Infrastructure Classic Migration Tools. It is a collection of command line tools that have similar capabilities to Application Migration Service.

Note:

Unlike Application Migration Service, the Oracle Cloud Infrastructure Classic Java Migration Tool cannot create your target domain with Oracle WebLogic Server for Oracle Cloud Infrastructure. You must manually create the target domain using Oracle Cloud Infrastructure Marketplace.

See:

• Oracle WebLogic Server Deploy Tooling project on GitHub
• Overview of Application Migration in the Oracle Cloud Infrastructure documentation
• Review the List of Available Migration Tools in Migrating Infrastructure Classic Workloads to Oracle Cloud Infrastructure