I recently tested a WebLogic Server 14c → 15c migration in a local Windows environment.
This article documents the actual lab approach I followed: backing up the existing Oracle Home, installing WebLogic 15c separately, moving the existing user_projects, and validating that the existing domain starts successfully on WebLogic 15c.
Environment used
Source: WebLogic Server 14.1.2.0.0
Target: WebLogic Server 15.1.1.0.0
OS: Windows
Domain: base_domain
Installation type: WebLogic Server only
No Forms, Reports, or other Fusion Middleware products
Oracle documents 14.1.2.0.0 → 15.1.1.0.0 as a supported WebLogic Server upgrade path.
- Check the Existing WebLogic Version
Before starting the migration, verify the current WebLogic installation.
For example:
cd C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin
java -cp ..\lib\weblogic.jar weblogic.version
The source environment should show:
WebLogic Server 14.1.2.0.0
Also verify the JDK:
java -version
Document the current:
WebLogic version
JDK version
Oracle Home
Domain Home
AdminServer
Managed Servers
Node Manager
Applications
This gives you a baseline before the upgrade.
- Stop the Existing WebLogic Environment
Before taking the backup, stop:
Node Manager
AdminServer
Managed Servers
Make sure no WebLogic/Java processes are still using the Oracle Home.
On Windows:
tasklist | findstr /I "java"
This is important because running processes can lock files and prevent you from renaming or backing up the Oracle Home.
- Take a Backup of the Existing Oracle Home
I kept the existing 14c installation as a backup.
For example:
C:\Oracle\Middleware\Oracle_Home
was backed up as:
C:\Oracle\Middleware\Oracle_Home_14c_BKP
The backup gives you a rollback point if something goes wrong during testing.
- Take a Backup of user_projects
The WebLogic domain contains environment-specific configuration.
For example:
Oracle_Home_14c
└── user_projects
└── domains
└── base_domain
I also preserved the existing user_projects directory.
This is important because the Oracle Home contains the WebLogic software, while user_projects contains the domain and its environment-specific configuration.
- Install WebLogic Server 15c
Next, install WebLogic Server 15.1.1.0.0 into a new Oracle Home.
For example:
C:\Oracle\Middleware\
│
├── Oracle_Home_14c_BKP
│
└── Oracle_Home
The new Oracle_Home contains WebLogic 15c, while Oracle_Home_14c_BKP preserves the previous environment.
For the generic installer, Oracle provides:
fmw_15.1.1.0.0_wls_generic.jar
The WebLogic 15.1.1 installation documentation should be checked for the currently supported JDK and installation requirements.
- Verify WebLogic 15c
After installation, verify the new WebLogic version:
cd C:\Oracle\Middleware\Oracle_Home\wlserver\server\bin
java -cp ..\lib\weblogic.jar weblogic.version
Expected result:
WebLogic Server 15.1.1.0.0
Also check:
java -version
At this point, we have:
14c
│
└── Oracle_Home_14c_BKP
15c
│
└── Oracle_Home
- Move the Existing user_projects
For my lab test, I copied the existing user_projects from the 14c backup into the new WebLogic 15c Oracle Home.
Source:
C:\Oracle\Middleware\Oracle_Home_14c_BKP\user_projects
Destination:
C:\Oracle\Middleware\Oracle_Home\user_projects
Using ROBOCOPY:
robocopy "C:\Oracle\Middleware\Oracle_Home_14c_BKP\user_projects" "C:\Oracle\Middleware\Oracle_Home\user_projects" /E
After the copy, verify:
dir C:\Oracle\Middleware\Oracle_Home\user_projects\domains
You should see:
base_domain
Then:
dir C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain
- Start WebLogic Using the 15c Installation
Now use the domain under the new Oracle Home.
For example:
cd C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin
startWebLogic.cmd
Monitor the AdminServer log.
The important confirmation is:
Server state changed to RUNNING
Once AdminServer reaches RUNNING, the WebLogic 15c domain is successfully starting in the lab environment.
- Verify the AdminServer
Check the configured listen address and port.
For example:
AdminServer
|
└── 10.250.109.98:7001
You can test the server with:
or:
http://:7001
- Start the Managed Servers
After AdminServer is running, start the Managed Servers.
Example:
AdminServer
|
├── ManagedServer1
├── ManagedServer2
└── ManagedServer3
Verify that each server reaches:
RUNNING
Check the server logs for:
Startup errors
Data Source failures
JMS failures
Security errors
Deployment failures
- Validate the Existing Applications
After the servers are running, validate the applications that existed in the 14c environment.
Check:
✓ Application state
✓ WAR/EAR deployments
✓ Context roots
✓ JDBC Data Sources
✓ JMS
✓ Security
✓ SSL
✓ REST/SOAP services
✓ External integrations
Don't assume application compatibility simply because the WebLogic server starts successfully.
WebLogic Server 15.1.1 uses Jakarta EE 9.1, so applications from earlier environments should be evaluated for compatibility and may require modification/recompilation.
- An Important Observation From My Lab
In this particular lab test, I did not run the Reconfiguration Wizard.
My test flow was:
WebLogic 14c
↓
Backup Oracle Home
↓
Install WebLogic 15c
↓
Copy user_projects
↓
Start WebLogic
↓
AdminServer → RUNNING
↓
Validate environment
The existing domain was able to start successfully using the new WebLogic 15c installation.
However, this lab observation should not be interpreted as saying that reconfiguration is universally unnecessary.
Oracle's documented WebLogic 15.1.1 upgrade procedure includes domain upgrade/reconfiguration considerations, so production environments should be evaluated against the official upgrade documentation before choosing to omit that step.
This distinction is important:
A successful server startup in a lab does not by itself establish that every documented production upgrade step can be skipped.
- Domain Upgrade vs Application Upgrade
These are two separate areas.
WebLogic Domain
↓
Domain upgrade / configuration
↓
WebLogic 15c
and:
WAR / EAR Application
↓
Jakarta EE compatibility
↓
Modification / recompilation if required
↓
Deploy to WebLogic 15c
WebLogic 15.1.1 introduces the Jakarta EE 9.1 application environment, so application compatibility should be tested separately.
- WebLogic Remote Console
Another major administration change is the use of WebLogic Remote Console.
For modern WebLogic environments, administrators can use Remote Console to manage:
Servers
Deployments
Data Sources
JMS
Security
Domain configuration
WebLogic Remote Console can be downloaded from the official Oracle repository:
Oracle WebLogic Remote Console Releases
For example:
WebLogic 15c
↓
AdminServer
↓
WebLogic Remote Console
↓
Domain Administration
I also documented the Remote Console setup separately:
How to Access Oracle WebLogic Remote Console in WebLogic 14c
- Final Architecture
The lab migration can be represented as:
WEBLOGIC 14c
14.1.2.0.0
│
▼
BACKUP ORACLE HOME
│
▼
INSTALL WEBLOGIC 15c
15.1.1.0.0
│
▼
COPY USER_PROJECTS
│
▼
START DOMAIN
│
┌────────┴────────┐
▼ ▼
AdminServer Managed Servers
│ │
└────────┬────────┘
▼
APPLICATION TEST
│
▼
VALIDATION
Conclusion
My WebLogic 14c → 15c lab migration demonstrated that an existing WebLogic domain can be tested against a new WebLogic 15c Oracle Home by:
Backup → Install 15c → Copy user_projects → Start → Validate
The most important lesson is to keep the Oracle Home, domain, and applications as separate upgrade considerations.
For production migrations, always compare your environment with Oracle's official 15.1.1 upgrade documentation, particularly around domain reconfiguration and application compatibility.
References
Oracle WebLogic Server 15.1.1 Upgrade Guide
Oracle WebLogic Server 15.1.1 Installation Guide
Oracle WebLogic Remote Console Releases
Top comments (0)