Oracle WebLogic Server 188.8.131.52.0 supports the Java API for JSON Binding 1.0 (JSR 367) specification by including the JSR-367 reference implementation for use with applications deployed on a WebLogic Server instance.
Oracle WebLogic Server 184.108.40.206.0 supports the JSON P 1.1 specification at =374. The JSON Processing 1.1 specification is based on the javax.json API, which supports new features such as JSON Pointer, JSON Patch, and JSON Merge Patch. These features are used to retrieve, transform, or manipulate values in an object model. For more information, see New Features for JSON Processing in Developing Applications for Oracle WebLogic Server.
Oracle WebLogic Server 220.127.116.11.0 supports the JSF 2.3 specification at =372. The themes for this release are better integration with other APIs and leverage of Java SE 8 features. WebLogic Server support includes better CDI integration, better WebSocket integration, Ajax method invocation, and class-level bean validation. For more information, see JavaServer Faces (JSF) in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.
Oracle WebLogic Server 18.104.22.168.0 supports the Servlet 4.0 specification (see =369), which introduces several new features, including support for HTTP/2, server push, HTTP trailer support, and mapping discovery. For more information, see What's New and Changed in Servlet 4.0 in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.
Oracle WebLogic Server 22.214.171.124.0 supports the Java EE Security API 1.0 specification (see =375 ), which defines portable authentication mechanisms (such as HttpAuthenticationMechanism and IdentityStore), and an access point for programmatic security using the SecurityContext interface. You can use the built-in implementations of these APIs, or define custom implementations. For more information, see Using the Java EE Security API in Developing Applications with the WebLogic Security Service.
Oracle WebLogic Server 14c (126.96.36.199.0) is certified for use with JDK 11, in addition to JDK 8. Supported Oracle WebLogic Server 14c (188.8.131.52.0) clients are certified for use with JDK 11.0.6. A certified JDK is required for running the WebLogic Server installation program.
In Oracle WebLogic Server 184.108.40.206.0, in addition to the generic installer and the Fusion Middleware Infrastructure installer, you can use the slim installer to install and configure Oracle WebLogic Server and Coherence.
Oracle WebLogic Server 14c (220.127.116.11.0) builds on support from prior WebLogic Server versions to improve the reliability, availability, scalability, and performance of WebLogic Server applications with regard to the use of clustered environments, Oracle database features, and multi data center architectures.
As of Oracle WebLogic Server 18.104.22.168.0, the default minimum version of the Transport Layer Security (TLS) protocol configured in WebLogic Server is Version 1.2. Oracle recommends the use of TLS v1.2 or later in a production environment. WebLogic Server logs a warning if the TLS version is set below 1.2.
As a result of an enhancement in WebLogic Server 22.214.171.124.0, the demonstration certificates generated by the CertGen utility by default contain the fully-qualified DNS name in the Subject Alternative Name (SAN) extension value, along with the host name as the common name (CN) value. However, you can create your certificate without the SAN extension and disable the fully-qualified DNS name using the -nosandnshost option at the command line. Optionally, you can specify additional host names, or IP addresses, or both, in the SAN extension value using the -a DNS:,IP: option.
Oracle WebLogic Server 14c (126.96.36.199.0) provides options to automatically create WebLogic cluster database leasing tables. See High Availability Database Leasing in Administering Clusters for Oracle WebLogic Server for the cluster configuration options related to database leasing.
Oracle WebLogic Server 14c (188.8.131.52.0) provides options to configure custom network channels for JTA communication. The network channels are used for JTA interserver communication. See Configuring Network Channels for JTA Communication in Developing JTA Applications for Oracle WebLogic Server.
The Oracle WebLogic Server 184.108.40.206.0 Proxy Plug-in includes new features, such as server push functionality, support for TLSv1.3 cipher suites, support for certificates signed with RSASSA-PSS signature algorithm, and security improvements.
The update history of the Oracle WebLogic Server documentation library summarizes the updates that have been made to various user and reference guides, as well as online help, for the initial release of version 14c (220.127.116.11.0).
Prior to WebLogic Server 18.104.22.168.0, the Managed Server JMX notifications were enabled by default. Starting with WebLogic Server 22.214.171.124.0, the Managed Server JMX notifications are changed to be disabled by default. See Best Practices: Listening for WebLogic Server Events in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.
Oracle WebLogic Server 14c (126.96.36.199.0) provides Java EE 8 full platform support, Java SE 11 certification, support for web services standards, support on multiple operating system and JVM platforms, and support for several security standards.
For development purposes, you can download and install the fmw_188.8.131.52.0_wls_lite_generic_AIX_zLinux_JDK11.jar file from the Oracle Fusion Middleware Software Downloads page at -server-downloads.html.
For development purposes, you can download and install the fmw_184.108.40.206.0_wls_lite_generic_ARM_OCI.jar or fmw_220.127.116.11.0_wls_lite_quick_slim_generic_ARM_OCI.jar file from the Oracle Fusion Middleware Software Downloads page at -server-downloads.html.
WebLogic Server Multitenant domain partitions, resource groups, resource group templates, virtual targets, resource override configuration MBeans, Resource Consumption Management, and proxy data sources have been removed from WebLogic Server as of version 18.104.22.168.0.
The JMS Interop Modules have been removed from WebLogic Server as of version 22.214.171.124.0. If you have a module named interop-jms.xml in your config.xml, convert it to a regular system module. See JMS System Module Configuration.
Active-Active XA Transaction Recovery (automated cross-site XA transaction recovery) has been removed from WebLogic Server as of version 126.96.36.199.0. For more information on XA transaction recovery solutions, see Understanding XA Transaction Recovery in Disaster Recovery. 2b1af7f3a8