1. Migrate your on-premises Oracle WebLogic Server workloads to the cloud
  2. Plan Your Migration

Plan Your Migration

Assess your requirements and understand the process variations.

Assess Requirements

To help ensure that you deploy the right infrastructure, consider your requirements.

  • Domain type: When using the WebLogic Server implementations from the Oracle Cloud Marketplace, it is important that you provision a WebLogic domain that matches your on-premises domain type.

    If the domain you migrate from is not a Java required file (JRF) domain, the stack provisions a non-JRF domain and you can deploy data sources in the WebLogic domain at a later step.

    If the domain you migrate from is a Java required file (JRF) domain, you must provision a database before you deploy the WebLogic Server stack and then specify that you are creating a JRF domain during stack deployment.

    If the source domain contains the following data sources, then provision the domain as a JRF domain:

    • jdbc/LocalSvcTblDataSwrce
    • jdbc/mds/owsm
    • jdbc/AuditAppendDataSource
    • jdbc/AuditViewDataSource
    • jdbc/OpssDataSource
    • jdbc/WLSSchemaDataSource

  • Data sources: Identify the non-JRF data sources to migrate. These are the application databases that you must provision and migrate.

  • Servers and nodes: On-premises installations of WebLogic Server may provision several managed servers per virtual machine (node). In a cloud environment where cost is linear with CPU count, deploying a single managed server per virtual machine (VM) sized for the expected load, ensures better redundancy and increased availability. The Oracle Cloud Marketplace stack provisions one managed server per node. Select the number of nodes during provisioning to match the number of managed servers on-premises. Size the virtual machine shape for the workload expected for a single managed server.

    Note:

    If you choose the path to update existing domain deployment tooling, and your on-premises deployment assumes multiple managed servers per machine, you may choose to provision only as many nodes as machines in your deployment. Choose a VM shape that can support the expected load of the multiple managed servers in order to reproduce the same topology at the expense of the extra resilience and increased availability.

    Also manually add extra load balancer backends after the stack is deployed to direct traffic to the additional ports used by the additional managed servers.

  • WebLogic services: If you use other services on-premises deployment, assess which services to migrate. If any of the services have external dependencies deployed on-premises, you must configure access to those from Oracle Cloud Infrastructure or plan a migration of the services to Oracle Cloud Infrastructure outside of the WebLogic migration.

Process Overview

The migration process is different depending on whether you need a Java required file (JRF) domain or a non-JRF domain.

For a JRF domain, you must provision a virtual cloud network (VCN) with a private subnet, and provision a database as the JRF datastore before you deploy the Oracle Cloud Marketplace stack. The Oracle Cloud Marketplace stack can deploy the other subnets for the virtual machine (VM) instances and load balancers.

For a non-JRF domain (where a database is not required at the time of provisioning), the Oracle Cloud Marketplace stack can create the necessary VCN and all subnets. You can add a private subnet for application databases to the existing VCN after provisioning the stack.

  1. Perform preliminary tasks to set up the environment for both types of domains:

    1. Create a compartment on Oracle Cloud Infrastructure.

    2. Create a vault and key.

    3. Create a secret for your WebLogic password.

  2. Perform preliminary tasks for a Java required file (JRF) domain:

    You can use the networking quickstart option to setup a VCN with the necessary gateways, both public and private subnets, routing tables, and security lists. You can optionally create additional private subnets if needed.

    You can also manually create the VCN and the specific resources you need:

    1. Create a virtual cloud network (VCN).

    2. Define security lists and routing tables on the database subnet to allow access from the other subnets.

    3. Create a private subnet.

    4. Create an internet gateway.

    Whether you create the VCN manually or using the wizard, you must also do the following:

    1. Add security rules the to database subnet security list to allow access from other subnets and from on-premises connections.
    2. Provision a database as the JRF datastore.
    3. Create a secret for the database SYS password.

  3. Deploy the WebLogic Server installation with the Oracle Cloud Marketplace stack.

    Select the option to provision a JRF domain if needed, and enter the information for the previously provisioned operational (JRF) database.

  4. Provision the necessary application databases on Oracle Cloud Infrastructure and migrate on-premises databases to the Oracle Cloud Infrastructure application databases.
  5. Migrate workloads using one of the following methods:
    1. Migrate workloads manually using the WebLogic Administrator Console to deploy resources and one of the following methods to deploy applications:
      • WebLogic Administrator Console
      • JDeveloper deployment tools
    2. Migrate workloads using WebLogic Deploy Tooling (WLDT).
    3. Migrate workloads using the WebLogic Scripting Tool by targeting existing application deployment scripts to the new domain.