WebLogic Server Compatibility

Jakarta EE 9.1 Compatibility

WebLogic Server 15c (15.1.1.0.0) is Jakarta EE 9.1 compatible. This compatibility allows a Jakarta EE 9.1 compliant application to be developed on one operating system platform and deployed for production on another, without requiring Jakarta EE 9.1 application code changes.

Oracle ensures this compatibility of Jakarta EE 9.1 application portability within a WebLogic Server release level.

Compatibility Within a Domain

Within the scope of a WebLogic domain, Oracle WebLogic Server supports a wide range of compatibility with respect to the specific versions of WebLogic Server instances that can run in that domain, as well as the mix of hardware, operating system, and JVM platforms on which those server instances can run.

However, depending upon the specific configurations present in the domain, such as WebLogic clusters, Oracle has specific recommendations for how you can achieve optimal performance. The following topics provide key information regarding compatibility within WebLogic domains:

About WebLogic Server Version Numbers

Within a WebLogic domain, the Administration Server, Managed Server instances, and the domain itself each have a WebLogic Server version number. The version number contains five decimal places; for example, WebLogic Server 15.1.1.0.0. The meaning of each decimal place is described below:

The first two decimal places together describe the Major Version number, for example "15.1" in 15.1.1.0.0. The WebLogic Server 14.1 Major Version release is also branded as the WebLogic Server 14c Major Version release.
The first three decimal places together describe the Minor Version number, for example "15.1.1" in 15.1.1.0.0. WebLogic Server 15.1.1 (or 15.1.1.0.0) is the first Minor Version release of the WebLogic Server 15.1 Major Version release. WebLogic Server 15.1.2 (or 15.1.2.0.0) would be the second Minor Version release of the WebLogic Server 15.1 Major Version release.
Patch Set releases for WebLogic Server 15.1.1.0.0 will increment the fourth decimal place. For example, 15.1.1.1.0 would be the first patch set release.
Patch Set Update releases are named uniquely by incrementing the fifth decimal place with the date of the Patch Set Update release in YYMMDD format; for example, 15.1.1.0.251130. This convention is used for Patch Set Update naming purposes; for example, naming downloads available on My Oracle Support. However, the application of a Patch Set Update does not change the version number of an existing WebLogic Server installation as referenced in the Oracle inventory directory (oraInventory) used by WebLogic Server 15.1.1 installers.

You can obtain the version number and Patch Set level of a WebLogic Server instance or domain several different ways. For example:

For an Administration Server or Managed Server instance, you can view the version message sent to stdout when the server is started. For example:
```
<Version: WebLogic Server 15.1.1.0.0  Sat Nov 11 12:34:37 PDT 2025 1960751 >
```
For a domain, you can view the value of the <domain-version> element in the domain configuration file, config.xml. For example:
```
<domain-version>15.1.1.0.0</domain-version>
```

WebLogic Version Compatibility

Within a WebLogic domain, the Administration Server, all Managed Server instances, and the WebLogic domain must be at the same WebLogic Server Major and Minor Version. This means that in WebLogic Server 15.1.1.0.0, the Administration Server, Managed Servers, and the WebLogic domain must all be at version 15.1.1.0.0. Note the following guidelines for maintaining consistency in Patch Set Update and Interim or One-off Patch levels within a domain.

In general, the best practice is for all server instances within a domain to be at the same Patch Set Update (PSU) and Interim or One-off Patch level during steady-state operation. However, there may be cases where server instances are required to run at different PSUs and Interim or One-off Patch levels within a domain. The primary examples include:
- When applying PSUs, Interim or One-off Patches in rolling fashion across server instances in the domain. In such cases, the maintenance should be applied to the Administration Server first, so that the Administration Server is at the same PSU and Interim or One-off Patch level (or higher) than its Managed Servers. See About Rolling Upgrade in Upgrading Oracle WebLogic Server.
- When there are specific requirements to run Managed Servers within a domain at different PSU and Interim or One-off Patch levels in steady-state operation. In such cases, the Administration Server should be at the highest PSU level, so that the Administration Server is at the same PSU level or higher than all of the Managed Servers. If Managed Servers within a domain are running with different Interim or One-off Patches, it will not be possible to apply a consistent set of Interim or One-off Patches to the Administration Server. Because this maintenance complexity may be difficult to manage, the general best practice is to use the same PSU and Interim or One-off Patch level across all servers in the domain.
Server instances within a cluster or domain can run on any hardware and operating systems as long as the hardware and operating systems are listed on the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network. However, note that running clustered Managed Server instances on different hardware and operating systems may impact load balancing and performance. In general, the best practice is to run all Managed Servers within a cluster on the same hardware and operating system.
If the WebLogic domain is part of an Oracle Enterprise Manager Cloud Control installation, additional requirements exist regarding the combinations of hardware, operating system, and JVMs, that may be configured in the domain. See Oracle Enterprise Manager Cloud Control Administrator's Guide.

For more information about WebLogic domains and additional details about domain compatibility, see Domain Restrictions in Understanding Domain Configuration for Oracle WebLogic Server.

Hardware, Operating System, and JVM Platform Compatibility

WebLogic Server instances within a domain can run on any hardware, operating system, and JVM platform as long as the hardware, operating systems, and JVMs are supported for the current version of WebLogic Server. For details, see the Oracle Fusion Middleware Supported System Configurations page on the Oracle Technology Network.

Note:

Although this platform compatibility support extends to Managed Server instances within a cluster, Oracle strongly recommends that clusters be homogeneous with respect to the underlying hardware, operating system, and JVM. Managed Server instances running in the same cluster are assumed to be equivalent, so running clustered server instances on mixed platforms may have a negative impact on load balancing and performance. If you must operate a cluster on a mixed platform, Oracle strongly recommends that you understand the load balancing and performance implications.

Node Manager Compatibility

As a best practice, Oracle recommends that the version of Node Manager used in a WebLogic domain should match the version of the Administration Server.

Persistent Data Compatibility

If you are upgrading Oracle WebLogic Server from release 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0 to release 15c (15.1.1.0.0), a number of updates are required to several configuration files. However, Oracle WebLogic Server upgrade tooling makes those configuration file updates for you automatically.

API Compatibility

WebLogic Server 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0 applications deployed on WebLogic Server must be modified and recompiled to run in the WebLogic Server 15.1.1.0.0 application environment.

Oracle recommends using Rewrite WebLogic recipes to apply the changes required for migrating applications to WebLogic Server 15.1.1.0.0 and Jakarta EE 9.1. You can use Rewrite WebLogic recipes for migrating WebLogic Server applications to newer versions of WebLogic Server, Java, Jakarta EE, and related versions of Jakarta Server Faces and Spring Framework. For more information, see Upgrade Your Applications in Upgrading Oracle WebLogic Server.

For a list of previously deprecated APIs that are removed in Oracle WebLogic Server 15.1.1.0.0, see Removed Functionality and Components in What’s New in Oracle WebLogic Server 15.1.1.0.0.

Protocol Compatibility

Interoperability between WebLogic Server 15c (15.1.1.0.0) and WebLogic Server 12.2.1.4.0, 4.1.1.0.0, and 14.1.2.0.0 is supported in several scenarios with regard to WebLogic clients, transport protocols, and WebLogic proxy plug-ins.

The supported client-server interoperability scenario is as follows: a WebLogic Server 15.1.1.0.0 server acting as a client can invoke RMI-based applications hosted on a WebLogic Server 14.1.2.0.0 server using IIOP*, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.

The supported server-server interoperability scenarios are as follows:

WLS 15.1.1.0.0 <-> WLS 14.1.2.0.0
WLS 15.1.1.0.0 <-> WLS 14.1.1.0.0
WLS 15.1.1.0.0 <-> WLS 12.2.1.4.0

The following clients can interoperate with WebLogic 15.1.1.0.0 servers. The parentheses indicate which version of WLS provides the client in its installation and whether the client itself uses javax or jakarta packages.

WL Thin T3 Client (15.1.1.0.0 jakarta)
WL Thin T3 Client (14.1.2.0.0 javax)
WL Thin T3 Client (14.1.1.0.0 javax)
WL Thin T3 Client (12.2.1.4.0 javax)
Install Client (T3) (15.1.1.0.0 jakarta)
Install Client (T3) (14.1.2.0.0 javax)
Install Client (T3) (14.1.1.0.0 javax)
Install Client (T3) (12.2.1.4.0 javax)
Web Services (15.1.1.0.0 jakarta)
Web Services (14.1.2.0.0 javax)
Web Services (14.1.1.0.0 javax)
Web Services (12.2.1.4.0 javax)
RESTful Webservices Client (15.1.1.0.0 jakarta)
RESTful Webservices Client (14.1.2.0.0 javax)
RESTful Webservices Client (14.1.1.0.0 javax)
RESTful Webservices Client (12.2.1.4.0 javax)

WebLogic Server 15c (15.1.1.0.0) supports client to server IIOP communications and interoperability with the following restrictions:

The only supported WebLogic Java IIOP clients are:
- A weblogic.jar install client from 15.1.1.0.0 or earlier WebLogic Server versions that are supported and under error correction.
- A wlfullclient.jar, available in earlier versions of WebLogic Server that are supported and under error correction. The wlfullclient.jar is included but deprecated in 12.2.1.4.0. WebLogic Server versions 14.1.1.0.0 and 14.1.2.0.0 do not include wlfullclient.jar.
- A wlclient.jar from earlier WebLogic Server versions that are supported and under error correction. WebLogic Server 15c (15.1.1.0.0) does not include wlclient.jar.
A Jakarta SE client (no JAR file from WebLogic Server in the class path) is not supported.
For WebLogic Server 15c (15.1.1.0.0) instances running on JDK17 or 21, IIOP interoperability with Jakarta clients is only available with a WebLogic Server 15c (15.1.1.0.0) install client running on JDK 17 or 21.
Interoperability support is not available between WebLogic Server 15c (15.1.1.0.0) instances running on JDK 17 or 21, and WebLogic Java IIOP clients running on JDK 17 or 21.