Oracle® Fusion Middleware Understanding Oracle WebLogic Server 12c Release 1 (12.1.1) Part Number E24446-02 |
|
|
PDF · Mobi · ePub |
Oracle attempts to support binary and source-level compatibility between the current version of WebLogic Server and all versions as far back as 9.2 in the areas of persistent data, generated classes, and API compatibility. In some cases, it is impossible to avoid incompatibilities. Where incompatibilities arise, they are fully documented in the Upgrade Guide for Oracle WebLogic Server.
WebLogic Server 12c Release 1 (12.1.1) is Java EE 6 compatible. This compatibility allows a Java EE 6 compliant application to be developed on one operating system platform, and deployed for production on another, without requiring Java EE 6 application code changes. Oracle ensures this compatibility of Java EE 6 application portability within a WebLogic Server release level.
With one exception, upgrading to WebLogic Server 12c Release 1 (12.1.1) does not require you to recompile applications in order to create new generated classes.
The current version of the EJBGen utility recognizes only JDK 5.0 or later metadata annotation-style EJBGen tags and not the old Javadoc-style tags. This means that source files that use the Javadoc-style tags must be upgraded to use the equivalent annotation, and then recompiled using the updated version of EJBGen.
All WebLogic Server instances within the same Administrative domain must be at the same major and minor version. You cannot mix server versions within a domain. Starting with the 12.1.1 release of WebLogic Server, the first two digits represent the major version and the third digit represents the minor version. All servers in a domain must be version 12.1.1.
Server instances within an Administrative domain can be at different patch set levels as long as the Administration Server is at the same patch set level or higher than its Managed Servers. The domain itself must remain at the lowest version number (must not be upgraded) and the configuration cannot include any attributes added in the newer versions.
All server instances within a cluster must be at the same patch set level. For example, all servers in a cluster can be at version 12.1.1.1, and there cannot be a mix of servers at 12.1.1.1 and 12.1.1.2 within a cluster.
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 Supported System Configurations page at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
. However, note that running clustered server instances on different hardware and operating systems may impact load balancing and performance.
When moving from WebLogic Server 9.x to 12.1.1, there are changes required to configuration files. Upgrade tooling in WebLogic Server versions 9.0 and later automatically convert the configuration files for you.
WebLogic Server 9.x, 10.0, and 10.3.x applications deployed on WebLogic Server 12c Release 1 (12.1.1) will function without modification. Exceptions to this rule include cases where API behavior was changed in order to conform to a specification or to fix incorrect behavior. In certain circumstances, a correction may cause your application to behave differently.
Interoperability between WebLogic Server 12c Release 1 (12.1.1) and WebLogic Server 9.x, 10.0, and 10.3.x is supported in the following scenarios:
A WebLogic Server 9.x, 10.0, and 10.3.x client can invoke RMI-based applications hosted on a WebLogic Server 12.1.1 server using IIOP, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.
A WebLogic Server 12.1.1 client can invoke RMI-based applications hosted on a WebLogic Server 9.x, 10.0, and 10.3.x server using IIOP, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.
A WebLogic Server 12.1.1 Web server plug-in can proxy to the latest patch set release of a 9.x, 10.0, and 10.3.x server.