WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool

Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud.

This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations.

Supported WLS versions

---

Why Use WDT for Migration?

When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to:

• Discover and export domain configurations and application binaries.
• Create reusable models and archives for deployment in a target domain.

---

Key Pre-Requisites

1. Source System:
   An Oracle WebLogic Server with pre-configured resources such as:

   • Application deployments
   • JMS modules
   • Data sources
   • Other domain configurations

2. Target System:

   • Option A: Oracle Marketplace WebLogic Server
   • Option B: A new installation of WebLogic Server (plain vanilla setup)

---

Step 1: Install WDT

First, download and install WDT. The following commands demonstrate the installation process:

# Download the WebLogic Deploy Tool
curl -LO https://github.com/oracle/weblogic-deploy-tooling/
releases/download/release-4.3.1/weblogic-deploy.zip

# Unzip the downloaded file
unzip weblogic-deploy.zip

Ensure that the required dependencies are met on your system before proceeding.

After being unzipped, the software is ready to use, just set the JAVA_HOME environment variable to point to a Java 7 or higher JDK and the shell scripts are ready to run.

chmod +x weblogic-deploy/bin/*.sh

ls -lrt *.sh

Set MW_HOME, DOMAIN_HOME and JAVA_HOME variables:

Step 2: Run Discover Domain Script in Source Server to Discover the Source Domain Configuration

. setDomainEnv.sh  

weblogic-deploy/bin/discoverDomain.sh \
-oracle_home $MW_HOME \
-domain_home $DOMAIN_HOME \
-archive_file source.zip \
-model_file source.yaml \
-variable_file source.properties \
-java_home $JAVA_HOME

. setDomainEnv.sh 

weblogic-deploy/bin/discoverDomain.sh \ 

-oracle_home $MW_HOME \ 

-domain_home $DOMAIN_HOME \ 

-archive_file gibh-sample-webapp_19012025.zip \ 

-model_file gibh-sample-webapp_19012025.yaml \ 

-variable_file source.properties \ 

-java_home $JAVA_HOME

You can observe 3 Output files as below:

Outputs:

source.zip
source.properties
source.yaml

Step 3: Review Source.yaml, source.zip

Add required host entries in the new weblogic server /etc/hosts file to connect to DB and other servers as needed.

$ vi source.yaml

Edit source.yaml

• Remove Domain Section [domainInfo] only If Weblogic Domain Exists else put the weblogic username and password as required.
  
  
  
• Remove topology section [topology:] only If Weblogic Domain Exists else put the weblogic username and password as required.
  
  
  
•  KEEP Resources: AND appDeployments: sections.Update values and path as required.
• Update Cluster or Target sections under Resources and appDeployments
• Update DB Details under JDBC Resources section in DB Connection details in source.yaml:
• Modify DB Connection details as per new Database Connection string in OCI

Note: Make sure you create ‘StagingMode: stage’ if it’s not present in yaml file. This is needed to make the App running state without restart of Admin Server.

Step 4: Edit Source.properties

Change to below:

- Remove AdminPassword and AdminUserName [belongs to Domain section of source.yaml]

- Remove SecurityConfig.xxx sections [belongs to topology section of source.yaml

Step 5:Validate the Generated Model and Archive

weblogic-deploy/bin/validateModel.sh \ 
-oracle_home /u01/app/oracle/middleware \ 
-model_file gibh-sample-webapp_19012025.yaml \ 
-archive_file gibh-sample-webapp_19012025.zip \ 
-variable_file source.properties

Step 6: As a final step, upload output file and Update Domain to Target Server:

Upload above generated source. scripts 

Upload install_wdt.sh script and update_domain_as_oracle_user.sh  from 

WDT Scripts to Target Server in OCI

Run Update Domain Script as mentioned below:

weblogic-deploy/bin/updateDomain.sh \ 
-domain_home /u01/data/domains/NEW_domain \ 
-oracle_home /u01/app/oracle/middleware \ 
-model_file gibh-sample-webapp_19012025.yaml \ 
-archive_file gibh-sample-webapp_19012025.zip \ 
-variable_file source.properties

if we are creating a new domain on target server then run createDomain.sh rather than updateDomain.sh

# Set Environment Variables 

export JAVA_HOME=/u01/app/oracle/jdk 
export MW_HOME=/u01/app/oracle/middleware 

# Create a New WebLogic Domain 

weblogic-deploy/bin/createDomain.sh \ 
-model_file gibh-sample-webapp_19012025.yaml \ 
-variable_file source.properties \ 
-oracle_home /u01/app/oracle/middleware \ 
-domain_parent /u01/data/domains \ 
-archive_file gibh-sample-webapp_19012025.zip

6. Review or Compare All Configurations from On-premise to Cloud and Start Services in OCI Weblogic Server. Change Java Heap memory as required and update the Datasource passwords.

Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment