5 WebLogic Server 14.1.2.0.0 Compatibility with Previous Releases

Learn about important compatibility information that you should consider before upgrading to Oracle WebLogic Server 14.1.2.0.0 from 14.1.1.0.0 (standalone WebLogic Server) or 12.2.1.4 release. Also learn about the feature changes in various Oracle WebLogic Server versions that may impact the applications you plan to run in the upgraded environment.

See also:

  • WebLogic Server Compatibility in Understanding Oracle WebLogic Server. This section provides general information about WebLogic Server compatibility goals and how they apply to this WebLogic Server release.

  • What's New in Oracle WebLogic Server 14.1.2.0.0 for this and prior releases. These documents provide information about new features that are available to you as well as behavior changes that may impact your applications.

About WebLogic Server Cluster Messaging

In 12.2.1.4.0, WebLogic Server cluster messaging was enhanced. If all of the servers in a cluster are running the same installation version of WebLogic Server, no changes are required.

When you perform an upgrade from 12.2.1.4.0 or 14.1.1.0.0, the upgraded servers must be explicitly set, to temporarily allow the older protocol. You can do this by setting the system property weblogic.upgradeExpirationDate with an expiration date, which enables the upgraded server to allow communication on the cluster until that expiration date and time is reached. For example:

-Dweblogic.upgradeExpirationDate=2024-01-05T08:47

If you want the clusters that are at different versions, to continue to communicate for an extended period of time, you must set the value to a preferred future upgrade date.

Note:

The system property -Dweblogic.upgradeExpirationDate must be used in the Server Start arguments for each of the Managed Servers, and not in the JAVA_OPTIONS environment variable in the startWebLogic.sh or startWebLogic.cmd scripts.