what's new in oracle weblogic server · oracle® fusion middleware what's new in oracle...
TRANSCRIPT
Oracle® Fusion MiddlewareWhat's New in Oracle WebLogic Server
12c (12.2.1.4.0)E90786-09July 2020
Oracle Fusion Middleware What's New in Oracle WebLogic Server, 12c (12.2.1.4.0)
E90786-09
Copyright © 2007, 2020, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Governmentend users are "commercial computer software" or “commercial computer software documentation” pursuantto the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.
This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Documentation Accessibility viii
Conventions viii
1 Introduction and Roadmap
Document Scope and Audience 1-1
Guide to This Document 1-1
2 What's New in Oracle WebLogic Server
WebLogic Server Update Summary 2-1
Java EE 7 Support 2-6
Batch Application Processing (JSR 352) 2-7
Concurrent Managed Objects (JSR 236) 2-7
Default Data Source 2-7
JMS 2.0 Support for Simplified JMS Application Development (JSR 343) 2-7
Java EE Connector Architecture 1.7 (JSR 322) 2-8
Enterprise JavaBeans 3.2 (JSR-345) 2-8
Clustering and High Availability Support for WebSocket 1.1 Applications 2-8
GZIP Compression Support 2-8
Java EE 7 Security Standards 2-8
Sample Applications 2-8
Avitek Medical Records — MedRec 2-9
New Java EE 7 Examples 2-9
JDK 8 and Server JRE 8 Certification 2-9
Oracle GraalVM Enterprise Edition Certification 2-10
Docker Certification 2-10
WebLogic Server Kubernetes Operator 2-11
Runtime Improvements 2-11
Deployment 2-11
Overriding Resource Group Template Application Configuration 2-11
Parallel Deployment 2-12
iii
FastSwap Enhancements 2-12
Deployment Performance Enhancements 2-12
Behavior Change for Application Names 2-13
JDBC Data Sources 2-13
Simplified Driver Installation and Update 2-14
Proxy Data Source Support 2-14
JDBC Data Source Support for Multitenancy 2-14
Universal Connection Pool Data Sources 2-14
Connection Leak Profiling Enhancements 2-14
Enhanced Connection-Based System Properties 2-15
Application Continuity Runtime Statistics 2-15
ONS Node List Configuration Enhancements 2-15
DRCP Network Timeout Property 2-15
Enhanced Edition-Based Redefinition (EBR) Documentation 2-15
Guidelines for Planned Maintenance and Database Outages 2-15
Enabling ONS and JDBC Debugging Changes 2-15
Support for Encrypted Passwords in a Data Source Definition 2-16
Enhanced Data Source Shutdown 2-16
Retry Count 2-16
Connection Initialization Callback for Non-Oracle Drivers 2-16
JDBC Store Improved Retry Handling 2-16
JDBC Store Connection Caching Policy 2-16
Gradual Draining 2-17
Shared Pooling 2-17
WebLogic Server Integration with Oracle Database 12.2 Driver 2-17
Initial Capacity Enhancement in the Connection Pool 2-17
JTA 2-17
Transactions without TLog Write 2-18
Transaction Guard 2-18
Network Channels for JTA Communication 2-18
Messaging 2-18
JMS Per-JVM Load Balancing 2-18
JMS Failover Limit 2-19
JMS Object-Based Security 2-19
Messaging Support for Multitenancy 2-19
Simplified JMS Cluster Configuration and High Availability Enhancements 2-19
Service Restart In Place 2-20
Message Limit in a Subscription 2-20
Monitoring WebSocket Applications 2-20
Policy Classloader 2-21
ReadyApp Integration with WebLogic Server 2-21
iv
RESTful Web Services 2-21
Simple WLST APIs for Dynamic Clusters 2-22
ThreadLocal Clean Out Support for Work Managers 2-22
Manageability Improvements 2-22
Elasticity Support for Dynamic Clusters 2-23
Resource Groups 2-23
Resource Group Templates and Resource Overrides 2-23
Named Concurrent Edit Sessions 2-24
Configuration Overriding 2-25
REST Resources for WebLogic Server Management 2-25
Fusion Middleware Control 2-25
Security 2-26
Support for Secured Production Mode 2-26
Oracle Identity Cloud Service Security Provider 2-27
New Method for Two-Way SSL Authentication in Java Clients Using JNDI 2-28
Java EE 7 Standards Support 2-28
LDAP Authentication Provider Manageability Enhancements 2-28
Default Minimum TLS Protocol Version 2-28
Support for weblogic-jwt-token 2-28
SAML 2.0 Implementation Updates 2-29
JEP 290 Utilization 2-29
AES 256-Bit Encryption Used in New Domains 2-30
Signing and Encryption Support for SAML 2.0 Assertions 2-30
Logging Enhancements 2-31
WebLogic Diagnostic Framework 2-31
WebLogic Server Development and Supplemental Distribution 2-33
Zero Downtime Patching 2-33
Applied Patch List 2-34
WLST 2-34
New Domain Commands 2-34
New Diagnostic Commands 2-35
New Node Manager Commands 2-36
New Edit Session Commands 2-36
New System Component Commands 2-36
Other New Commands 2-36
Modifications to Existing Commands 2-37
idd Variable and Argument 2-37
Resource Consumption Management 2-37
SNMPv3 Default Protocol 2-38
Continuous Availability 2-38
Documentation Update History 2-39
v
Standards Support, Supported Configurations, and WebLogic Server Compatibility 2-44
Standards Support 2-44
Java Standards 2-44
Web Services Standards 2-46
Other Standards 2-46
Supported Configurations 2-47
Licensing Information 2-48
WebLogic Server Compatibility 2-48
Database Interoperability 2-48
Application Data Access 2-48
Database Dependent Features 2-49
Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x) 2-49
WebLogic jCOM 2-50
Oracle Traffic Director (OTD) 2-50
Deprecated WebLogic Server Multitenant Functionality and ResourceConsumption Management 2-50
Automated Cross-Site XA Transaction Recovery Deprecated 2-51
Simple Network Management Protocol (SNMP) v1 and v2 2-51
ValidateCertChain Java Utility File-based Certificate Chains 2-51
SecurityConfigurationMBean.AnonymousAdminLookupEnabled Attribute 2-51
ServerTemplateMBean.DefaultTGIOPUser Attribute 2-51
WebLogic Full and Standard Clients 2-52
Log4j 2-52
LogMBean.ServerLoggingBridgeUserParentLoggersEnabled Attribute 2-52
User Name and Password System Properties 2-52
Maven 11x Plug-In Deprecated 2-52
JSP Tags for XML Processing 2-53
Deprecated Functionality in WLST 2-53
Server Argument to WLST Diagnostics Commands 2-53
The addTemplate and readTemplate Control Commands 2-53
Implicit Importing of Modules Using WLST 2-53
The configToScript Command 2-54
Deprecated RESTful Management Features 2-54
RESTful Management Resources for Oracle WebLogic Server Multitenant 2-54
RESTful Life Cycle Management Resources 2-54
RESTful Resources for Monitoring and Management 2-55
URL Format for REST Management 2-55
WebLogic Server/Spring Integration Features 2-55
Deprecated Diagnostics Exceptions 2-55
RESTful Web Services 2-56
Jersey 1.18 (JAX-RS 1.1 RI) Client APIs 2-56
vi
Runtime Monitoring MBeans 2-56
CacheFilter API 2-56
JAX-RPC WebService-ReliableMessaging 2-56
SSLMBean.ExportKeyLifespan Attribute 2-56
setSSLClientCertificate and setSSLClientKeyPassword Methods 2-57
EJBGen 2-57
WebLogic Replicated Store 2-57
JMS Interop Modules 2-57
WebLogic JMS Resource Adapter 2-57
JMS Reconnect 2-58
JMS Deployable Configuration 2-58
JMS Weighted Distributed Destinations 2-58
DynamicServersMBean.MaximumDynamicServerCount Attribute 2-58
Compatibility Setting for JTA Security Interoperability Mode 2-58
Removed Functionality and Components 2-59
Certificate Chains 2-59
Compatibility Security 2-59
6.x Realms 2-63
Certificate Request Generator Servlet 2-63
weblogic.Admin 2-63
JAXR 2-64
Jersey 1.18 (JAX-RS 1.1. RI) Server APIs 2-64
WebLogic Keystore Provider 2-64
weblogic.security.provider.PrincipalValidatorImpl 2-64
weblogic.xml.stream.util.XMLPullReaderBase 2-64
Connect-Time Failover 2-64
Compatibility MBean Server and Type-Safe MBean Interfaces 2-65
Startup Option for Lighter-Weight Runtime 2-65
Oracle WebLogic Server Proxy Plug-In for Oracle iPlanet Web Server 2-65
vii
Preface
This preface describes the document accessibility features and conventions used inthis guide—What's New in Oracle WebLogic Server 12.2.1.4.0.
Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the OracleAccessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
ConventionsThe following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.
Preface
viii
1Introduction and Roadmap
This chapter describes the contents and audience for this guide—What’s New inOracle WebLogic Server 12.2.1.4.0.This chapter includes the following sections:
• Document Scope and Audience
• Guide to This Document
Document Scope and AudienceSystem administrators and operators responsible for monitoring and managinga WebLogic Server installation should use this document as a resource forunderstanding new features for all components of Oracle WebLogic Server 12c(12.2.1.4.0).
This document is relevant to all phases of a software project, from developmentthrough test and production phases.
Guide to This DocumentThis document is organized as follows:
• This chapter, Introduction and Roadmap, provides a roadmap and describes theaudience for this guide.
• What's New in Oracle WebLogic Server describes the new and changedfunctionality in this WebLogic Server release.
1-1
2What's New in Oracle WebLogic Server
This document describes the new features made in the initial release of 12c(12.2.1.0.0), and also describes the changes made in the subsequent patch setreleases: 12.2.1.1.0, 12.2.1.2.0, 12.2.1.3.0, and 12.2.1.4.0.
Note:
Unless noted otherwise, the new and changed features described in thisdocument were introduced in the initial release of Oracle WebLogic Server12c (12.2.1.0.0).
This chapter includes the following topics:
• WebLogic Server Update Summary
• Java EE 7 Support
• JDK 8 and Server JRE 8 Certification
• Oracle GraalVM Enterprise Edition Certification
• Docker Certification
• WebLogic Server Kubernetes Operator
• Runtime Improvements
• Manageability Improvements
• Continuous Availability
• Documentation Update History
• Standards Support, Supported Configurations, and WebLogic Server Compatibility
• Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
• Removed Functionality and Components
WebLogic Server Update SummaryOracle has released four patch set releases for Oracle WebLogic Server 12c(12.2.1.0.0).
These updates are summarized in the following sections, starting with the most recentrelease.
Oracle WebLogic Server version 12.2.1.4.0, also known as Patch Set 4, adds thefeatures described in the following table.
2-1
Feature Description
ConfigurationOverriding
Configuration overriding lets administrators place configuration information,contained in an XML file, in a known location where running serversidentify and load it, overriding aspects of the existing configuration. SeeConfiguration Overriding.
In previous releases, configuration overrides required an expiration time andtherefore were always temporary. See Temporary Configuration Overridingin Understanding Domain Configuration for Oracle WebLogic Server. Now,this limitation is removed.
Security New features include:
• Use of AES 256-bit encryption for sensitive configuration and run-timevalues. All new domains created in this release and later will use AES256–bit encryption. In previous releases, domains used AES 128–bitencryption. See AES 256-Bit Encryption Used in New Domains.
• Support for signing and encrypting SAML assertions for SAML 2.0. SeeSigning and Encryption Support for SAML 2.0 Assertions.
• A new attribute, AllowedTargetHosts on theFederationServicesMBean and SingleSignOnServicesMBeanthat can be used to specify the list of allowed destination hosts wherethe SAML SP target URL may be redirected.
• Enhancements to the JEP 290 implementation:
– WebLogic Server now provides a system property,weblogic.oif.serialFilterLogging, that you can use to logthe current blocklist classes and packages.
– The scope of the default filter is now set to global.See JEP 290 Utilization.
• Two new configuration attributes,ServerNotAvailableCounterInterval andServerBackoffEnabled, were added to theOracleIdentityCloudIntegratorMBean to handle authenticationfailures that can occur when the Oracle Identity Cloud Service isunavailable or not responding to authentication requests. See OracleIdentity Cloud Service Security Provider.
• Additional security recommendations were added to help reduceattack surface on the WebLogic Server development and productionenvironments. These recommendations include:– Using network channels and connection filters to isolate incoming
and outgoing application traffic– Limiting protocol for external channels– Running different protocols on different ports– Disabling tunneling on channels that are available external to the
firewall– Preventing unauthorized access to your WebLogic Server
resources such as JDBC, JMS or EJB resources.See Ensuring the Security of Your Production Environment in Securinga Production Environment for Oracle WebLogic Server.
JMS Per-JVMLoad Balancing
You can now enable Per-JVM instead of Per-Member message loadbalancing behavior for new or forwarded messages. With Per-JVM, only onemember of a distributed destination on each WebLogic Server JVM getsnew messages regardless of the number of members hosted by a JVM.See JMS Per-JVM Load Balancing.
JMS FailoverLimit
You can now set a Fail Over Limit to limit the number of cluster-targeted JMS Server or SAF Agent instances that can fail over to aparticular JVM. See JMS Failover Limit.
Chapter 2WebLogic Server Update Summary
2-2
Feature Description
Certification onOracle GraalVMEnterprise Edition
Oracle WebLogic Server and Coherence are now certified on OracleGraalVM Enterprise Edition. See Oracle GraalVM Enterprise EditionCertification.
Deprecatedcomponents
The following components are deprecated in this patch set and will beremoved in a future release of WebLogic Server:• Simple Network Management Protocol (SNMP) v1 and v2. The default
is now SNMPv3. See SNMPv3 Default Protocol.• ValidateCertChain Java utility file-based certificate chains.• WebLogic Server Multitenant domain partitions, resource groups,
resource group templates, virtual targets, Resource ConsumptionManagement, and proxy data sources are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.
• Active-Active XA Transaction Recovery (automated cross-site XAtransaction recovery) is deprecated in WebLogic Server 12.2.1.4.0 andwill be removed in the next release. See Automated Cross-Site XATransaction Recovery Deprecated.
See Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x).
Patch Set 3
Oracle WebLogic Server version 12.2.1.3.0, also known as Patch Set 3, adds thefeatures described in the following table.
Feature Description
Service RestartIn Place
Service Restart In Place adds support for the ability to use any customstore with any migration policy. See Service Restart In Place.
Message limit ina JMS messagesubscription
WebLogic JMS adds a message limit option to help prevent individualoverloaded subscriptions from using up all available resources. SeeMessage Limit in a Subscription.
Security New features include:
• The WebLogic Security Service adds the secured production modefeature, which helps ensure a highly secure environment forapplications and resources. See Support for Secured Production Mode.
• A new security provider, Oracle Identity Cloud Integrator, that is anauthentication and identity assertion provider that can access users,groups, and Oracle Identity Cloud Service scopes and application rolesstored in the Oracle Identity Cloud Service. See Oracle Identity CloudService Security Provider.
Updates to the SAML 2.0 implementation include:
• Use of the SHA2 signature algorithm as the default for signing requestsand responses. For backward compatibility, set thecom.bea.common.security.saml2.useSHA1SigAlgorithm to true.
• By default, certificates that are expired or not yet valid are no longerused in SAML signing. To allow use of these certificates, set thecom.bea.common.security.saml2.allowExpiredCerts to true.
See SAML 2.0 Implementation Updates.
Zero DowntimePatching
ZDT Patching adds support for modifying workflows using custom hooks.See Zero Downtime Patching.
Applied PatchesList
Oracle WebLogic Server adds the ability to obtain a list of patches that havebeen applied to a server instance. See Applied Patch List.
Chapter 2WebLogic Server Update Summary
2-3
Feature Description
JDBC datasources
New features include:
• Shared pooling for WebLogic data sources. Shared pooling providesthe ability for multiple data source definitions to share an underlyingconnection pool. See Shared Pooling.
• Additional integration support for several new Oracle Database 12.2features. See WebLogic Server Integration with Oracle Database 12.2Driver.
• Initial Capacity Enhancement in the Connection Pool. WebLogic Server12.2.1.3 enhances creation of initial capacity connections in a datasource by providing control over connection retry, early failure, andcritical resources. See Initial Capacity Enhancement in the ConnectionPool.
JTA WebLogic JTA adds transaction guard, which provides at-most-onceexecution during planned and unplanned outages and prevents duplicatesubmissions. See Transaction Guard.
TemporaryConfigurationOverriding
Temporary configuration overriding lets administrators place configurationinformation, contained in an XML file, in a known location where runningservers identify and load it, overriding aspects of the existing configuration.See Configuration Overriding.
Apache Ant This patch set release of WebLogic Server now includes Apache Ant 1.9.8,which may have an impact on the use of the clientgen Ant task. SeeUpgraded Version of Apache Ant in Upgrading Oracle WebLogic Server.
Deprecatedcomponents
The following components are deprecated in this patch set and will beremoved in a future release of WebLogic Server:
• The following WebLogic JMS features and components:
– WebLogic Replicated Store, which is intended solely for use inOracle Exalogic Elastic Cloud environments
– JMS resource adapter– WebLogic JMS Automatic Reconnect– WebLogic JMS Application Modules for Deployment
• WebLogic SAF Agent support for JAX-RPC Reliable Messaging• EJBGen utility• The AnonymousAdminLookupEnabled attribute on the
SecurityConfigurationMBean• The RESTful management resources listed in Deprecated RESTful
Management Features.See Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x).
Patch Set 2
Oracle WebLogic Server version 12.2.1.2.0, also known as Patch Set 2, adds thefeatures described in the following table.
Feature Description
Oracle ServerJRE 8
Oracle WebLogic Server 12.2.1.2.0 is certified for use with Oracle ServerJRE 8.0. See JDK 8 and Server JRE 8 Certification.
JDBC datasources
WebLogic JDBC now supports gradual draining of connections in the JDBCconnection pool, to improve performance during maintenance shutdowns.See Gradual Draining.
Chapter 2WebLogic Server Update Summary
2-4
Feature Description
Security The weblogic.jndi.Environment class has been enhanced forconfiguring two-way SSL authentication for Java clients using JNDI. SeeNew Method for Two-Way SSL Authentication in Java Clients Using JNDI.
Patch Set 1
Oracle WebLogic Server version 12.2.1.1.0, also known as Patch Set 1, introduced theupdates summarized in the following table.
Feature Description
Resourceconsumptionmanagement
A configurable, partition auto-restart trigger action has been added thatrestarts the partition on the server instance on which the partition'sresource consumption quotas have been breached. See Triggers in UsingOracle WebLogic Server Multitenant.
Partitionadministration
The partition administrator role has been added. When logged in orconnected to a partition as a member of the management identity domain,the partition administrator can manage the security realm data associatedwith the partition, such as managing users and groups, credentialmaps, roles, and policies. See Managing Security Data as a PartitionAdministrator: Main Steps and Examples in Using Oracle WebLogic ServerMultitenant.
Domain toPartitionConversion Tool
The Domain to Partition Conversion Tool (D-PCT) has been added, whichprovides the ability to migrate existing applications and resources from anon-multitenant domain to a multitenant domain partition.
Cross-sitetransactionrecovery
This patch set introduces a site leasing mechanism to provide automaticrecovery when a site failure or mid-tier failure occurs. With site leasing,WebLogic Server provides a more robust mechanism to failover andfailback transaction recovery without imposing dependencies on the TLog,which affect the health of the servers hosting the transaction manager. SeeActive-Active XA Transaction Recovery in Developing JTA Applications forOracle WebLogic Server.
Continuousavailability bestpracticesdocumentation
New best practices for multi-data center deployments are described inDesign Considerations for Continuous Availability in Continuous Availabilityfor Oracle WebLogic Server.
Administrationenhancements forCoherence
This patch set release includes enhancements to the WebLogic ServerAdministration Console for configuring the following Coherence features:
• Coherence federated caching – You can now set up federationwith basic active/active and active/passive configurations using theAdministration Console, eliminating the need to use configuration files.
• Coherence persistence – A persistence tab has been added thatprovides the ability to configure persistence-related settings that applyto all services.
See Configuring Cache Federation and Configuring Cache Persistence inAdministering Clusters for Oracle WebLogic Server.
Chapter 2WebLogic Server Update Summary
2-5
Feature Description
Zero DowntimePatching
Zero Downtime Patching includes the following new capabilities:
• Support has been added for updating applications running in amultitenant partition without affecting other partitions that run in thesame cluster.
• Coherence applications can now be updated while maintaining highavailability of the Coherence data during the rollout process.
• The requirement to use Node Manager start the Administration Serverto upgrade it has been removed.
See Zero Downtime Patching.
JDBC datasources
Enhancements include the following:
• A configured connection initialization callback can now be called withany driver and any data source type.
• New asynchronous, task-based operations have been added for datasource suspend and shutdown.
• Using JDBC Store's retry mechanism, you can now configure multipleretry attempts over a specified time period.
See JDBC Data Sources for more information about JDBC feature updates.
Diagnostics The Policies and Actions component of the WebLogic DiagnosticsFramework has been updated to support the heap dump and thread dumpactions, which capture heap dumps or thread dumps, respectively, whencertain runtime conditions are met. See Configuring Actions in Configuringand Using the Diagnostics Framework for Oracle WebLogic Server.
Java EE 7 SupportOracle WebLogic Server 12c (12.2.1) is a fully compatible implementation of the JavaPlatform, Enterprise Edition (Java EE) Version 7.0. Java EE 7 enables developersto make use of the latest innovations in the Java Enterprise APIs, which includenew programming models, as well as consolidating, enhancing, and in some casessimplifying existing specifications.
The Java EE 7 APIs and related capabilities simplify development of serverapplications accessed by "rich" clients using lightweight web-based protocols suchas REST, WebSocket, and Server-Sent Events. Improvements to developmenttooling and open source support expand developer choices and simplify creation ofdevelopment environments.
New Java EE 7 support updates provided in WebLogic Server 12c (12.2.1) aredescribed in the following sections:
• Batch Application Processing (JSR 352)
• Concurrent Managed Objects (JSR 236)
• Default Data Source
• JMS 2.0 Support for Simplified JMS Application Development (JSR 343)
• Java EE Connector Architecture 1.7 (JSR 322)
• Enterprise JavaBeans 3.2 (JSR-345)
• Clustering and High Availability Support for WebSocket 1.1 Applications
• GZIP Compression Support
Chapter 2Java EE 7 Support
2-6
• Java EE 7 Security Standards
• Sample Applications
Batch Application Processing (JSR 352)
Oracle WebLogic Server 12c (12.2.1) adds support for Batch Processing Runtime forthe Java EE 7 Platform (JSR 352), which provides support for defining, implementing,and running batch jobs.
The batch runtime in WebLogic Server uses a data source, also known as the jobrepository, and a managed executor service to execute asynchronous batch jobs.The executor service processes the jobs and the job repository data source storesthe status of current and past jobs. The default batch runtime in each WebLogicdomain can be used without any configuration using the Derby demo database. Forenvironments that use an enterprise-level database schema, you can configure adedicated job repository data source and executor service for each WebLogic domain.
For more information about configuring and managing the batch runtime, see Usingthe Batch Runtime in Administering Server Environments for Oracle WebLogic Server.
Concurrent Managed Objects (JSR 236)
Oracle WebLogic Server 12c (12.2.1) adds support for Concurrency Utilities for JavaEE 1.0 (JSR 236), which is a standard API for providing asynchronous capabilities toJava EE application components, such as servlets and EJBs.
WebLogic Server provides concurrency capabilities to Java EE applications byassociating the Concurrency Utilities API with the Work Manager to make threadscontainer-managed. You configure concurrent managed objects (CMOs) and thenmake them available for use by application components. Similar to Work Managers,CMOs can be defined at the domain level, application level, and module level, byusing the Administration Console, MBeans, or deployment descriptors:
For more information about configuring and managing concurrent resources, seeConfiguring Concurrent Managed Objects in Administering Server Environments forOracle WebLogic Server.
Default Data Source
Oracle provides a default data source that is required by a Java EE 7-compliantruntime. This preconfigured data source can be used by an application to access theDerby Database that can be installed with WebLogic Server. See Using the DefaultData Source in Administering JDBC Data Sources for Oracle WebLogic Server.
JMS 2.0 Support for Simplified JMS Application Development (JSR343)
This release of WebLogic Server supports the JMS simplified API defined by theJava Message Service (JMS) 2.0 specification. See Understanding the Simplified APIProgramming Model in Developing JMS Applications for Oracle WebLogic Server.
Chapter 2Java EE 7 Support
2-7
Java EE Connector Architecture 1.7 (JSR 322)
Oracle WebLogic Server 12c (12.2.1) supports the Java EE Connector Architecture1.7 specification. See Understanding Resource Adapters in Developing ResourceAdapters for Oracle WebLogic Server.
Enterprise JavaBeans 3.2 (JSR-345)
Oracle WebLogic Server 12c (12.2.1) supports the Enterprise Java Beans (EJBs)3.2 specification (JSR 352). See Understanding Enterprise JavaBeans in DevelopingEnterprise JavaBeans for Oracle WebLogic Server.
Clustering and High Availability Support for WebSocket 1.1Applications
This release of Oracle WebLogic Server adds support for clustering and highavailability with WebSocket applications. WebSocket clustering uses Coherence aspart of its implementation to establish communication among all cluster members.WebSocket clustering enables horizontal scaling, allows you to send messages to allmembers of the cluster, increases the maximum number of connected clients, anddecreases broadcast execution time.
GZIP Compression Support
Oracle WebLogic Server adds support for GZIP compression in the WebLogic Wwebcontainer, which you can enable at the domain or web application level. With GZIPcompression enabled, you can configure attributes, such as minimum content lengthand compression content types, and monitor related statistics. See Enabling GZIPCompression for Web Applications in Developing Web Applications, Servlets, andJSPs for Oracle WebLogic Server.
Java EE 7 Security Standards
Oracle WebLogic Server 12c (12.2.1) includes support for the following securitystandards:
• Java Authorization Contract for Containers 1.5
• Java Authentication Service Provider Interface for Containers 1.1 (JASPIC)
• Packaged Permissions
• Uncovered HTTP Methods (JSR 340 for Servlet 3.1)
See Security.
Sample Applications
Chapter 2Java EE 7 Support
2-8
The sample applications that can optionally be installed with WebLogic Server havebeen updated for Java EE 7, as described in the following sections:
• Avitek Medical Records — MedRec
• New Java EE 7 Examples
Avitek Medical Records — MedRec
Avitek Medical Records (or "MedRec") is a comprehensive educational sampleapplication that demonstrates WebLogic Server and Java EE features, as well as bestpractices. In Oracle WebLogic Server 12c (12.2.1), MedRec has been upgraded todemonstrate the following Java EE 7 features:
• Java Persistence 2.1
• Simplified API of JMS 2.0
• Contexts and Dependency Injection 1.1
• Batch 1.0
• JAX-RS 2.0
• JavaServer Faces 2.2
• JSON Processing 1.0
• HTML5
New Java EE 7 Examples
New sample applications have been added to show the following Java EE 7 features:
• JSON Processing 1.0
• Servlet 3.1
• JavaServer Faces 2.2
• Expression Language 3.0
• Batch Processing
• Concurrency Utilities
• Contexts and Dependency Injection 1.1
• Java EE Connector Architecture 1.7
• Java Persistence 2.1
• Java Message Service API 2.0
• Enterprise JavaBeans 3.2
• Java API for RESTful Web Services (JAX-RS) 2.0 asynchronous processing,filters and interceptors, and server-sent events (SSE) Jersey support.
JDK 8 and Server JRE 8 CertificationOracle WebLogic Server 12c (12.2.1) is certified for use with JDK 8. Supported OracleWebLogic Server 12c (12.2.1) clients are certified for use with JDK 7 and JDK 8
Chapter 2JDK 8 and Server JRE 8 Certification
2-9
Update 40. A certified JDK is required for running the WebLogic Server installationprogram.
As of release 12.2.1.2.0, Oracle WebLogic Server is also certified for use with OracleServer JRE 8, which is designed for server-side applications. The Server JRE makesstorage and deployment faster and easier by including only the commonly requiredfeatures and components from the JRE and JDK.
See the following topics:
• The Oracle Fusion Middleware Supported System Configurations page on OracleTechnology Network.
• The Java SE Downloads page on Oracle Technology Network from which OracleServer JRE 8 is available, including release notes and installation instructions:http://www.oracle.com/technetwork/java/javase/downloads/index.html
See also the Java Platform Group Product Management blog, Understanding theServer JRE.
• Roadmap for Verifying Your System Environment in Installing and ConfiguringOracle WebLogic Server and Coherence
Oracle GraalVM Enterprise Edition CertificationOracle WebLogic Server and Coherence 12.2.1.4.0 are certified to run on OracleGraalVM Enterprise Edition.
Oracle GraalVM Enterprise Edition is a high performance runtime platform built onOracle's enterprise-class Java SE. Its optimizing compiler accelerates WebLogicapplications by rearranging compiled code, aggressive method inlining, escapeanalysis, advanced vectorization and more. Based on internal testing, you shouldexperience up to a 5-10% performance improvement.
For details, see Running Oracle WebLogic Server and Coherence on GraalVMEnterprise Edition.
Docker CertificationOracle WebLogic Server 12.2.1 is certified to run inside a Docker container. Dockeris a Linux-based container technology that enables you to quickly create lightweightclustered and non-clustered WebLogic Server domain configurations on a single ormulti host OS, or virtual machines, for either development or production environments.
As part of this certification, Oracle provides Docker files and supporting scripts forbuilding images of Oracle WebLogic Server. These images are built as an extension ofexisting Oracle Linux images. These scripts and build images are available on GitHubat the following location:
https://github.com/oracle/docker/tree/master/OracleWebLogic
For information about using Docker with WebLogic Server, and the combinations ofOracle WebLogic Server, JDK, Linux and Docker versions that are certified for buildingyour Docker images, see the Supported Virtualization Technologies with Oracle FusionMiddleware.
Chapter 2Oracle GraalVM Enterprise Edition Certification
2-10
WebLogic Server Kubernetes OperatorOracle provides an open-source WebLogic Server Kubernetes Operator which hasseveral key features to assist you with deploying and managing WebLogic domainsin a Kubernetes environment. The operator uses a common set of KubernetesAPIs to provide an improved user experience when automating operations such as:provisioning, life cycle management, application versioning, product patching, scaling,and security.
The operator is packaged in a Docker image which you can access from DockerHub. For project documentation, scripts, samples, and files, see the Oracle WebLogicServer Kubernetes Operator GitHub repository.
Runtime ImprovementsOracle WebLogic Server 12c (12.2.1) builds on support from prior WebLogic Serverversions to improve the reliability, availability, scalability and performance of WebLogicServer applications with regards to use of clustered environments, new OracleDatabase features, and multi data center architectures.
These support improvements are described in the following topics:
• Deployment
• JDBC Data Sources
• JTA
• Messaging
• Monitoring WebSocket Applications
• Policy Classloader
• ReadyApp Integration with WebLogic Server
• RESTful Web Services
• Simple WLST APIs for Dynamic Clusters
• ThreadLocal Clean Out Support for Work Managers
Deployment
Oracle WebLogic Server 12c (12.2.1) includes the following new and changeddeployment features:
• Overriding Resource Group Template Application Configuration
• Parallel Deployment
• FastSwap Enhancements
• Deployment Performance Enhancements
• Behavior Change for Application Names
Overriding Resource Group Template Application Configuration
Chapter 2WebLogic Server Kubernetes Operator
2-11
Note:
Resource groups, resource group templates, and resource overrideconfiguration MBeans are deprecated in WebLogic Server 12.2.1.4.0 andwill be removed in the next release.
When a resource group references a resource group template, it inherits theapplication configuration defined in the resource group template. You can customizea specific application in a resource group by overriding the default applicationconfiguration in the resource group template.
To override the application configuration defined in a resource group template, specifya different deployment plan that the application should use for its configuration. Youcan apply application overrides or remove existing overrides using the AdministrationConsole, Fusion Middleware Control, or by using the update or redeploy commandwith one of the supported deployment clients.
See Overriding Application Configuration in Deploying Applications to OracleWebLogic Server and Overriding Application Configuration in Using Oracle WebLogicServer Multitenant.
Parallel Deployment
This release of Oracle WebLogic Server adds support for parallel deployment. For usecases involving the deployment of multiple applications, the deployment of a singleapplication with multiple modules, or the deployment of one or more applicationsacross multiple partitions, parallel deployment improves startup and post-runningdeployment time. In multitenant environments, parallel deployment helps avoid cross-tenant performance impact.
For more information about parallel deployment, see Enabling Parallel Deployment forApplications and Modules in Deploying Applications to Oracle WebLogic Server andEnabling Parallel Deployment in Multitenant Environments in Using Oracle WebLogicServer Multitenant.
FastSwap Enhancements
This release of Oracle WebLogic Server enhances FastSwap to work with the Java EEContexts and Dependency Injection (CDI) specification.
Used in development mode, FastSwap helps developers avoid redeployment of anapplication and reduce turnaround time during development iterations. To improve thedeveloper experience, you can now use FastSwap with CDI. For more informationabout FastSwap, see Using FastSwap Deployment to Minimize Redeployment inDeploying Applications to Oracle WebLogic Server.
Deployment Performance Enhancements
This release of Oracle WebLogic Server adds several deployment performanceenhancements. Improvements include:
• Application class loading in parallel.
Chapter 2Runtime Improvements
2-12
• Indexing of class finder data to locate classes and resources faster.
• Deployment factory caching during identification of a deployment, helping largedeployments process faster.
• Annotation scanning caching for libraries and applications, benefiting server restartand resulting in faster deployment time.
• Annotation scanning in parallel so that each JAR file in the class path of a moduleis handled in parallel.
Behavior Change for Application Names
As of Oracle WebLogic Server 12.2.1, application names must be unique withineach deployment scope. When deploying an application globally to a domain, if thatapplication name is already in use in the current domain, the application deploymentfails. This is a behavior change from previous WebLogic Server versions, whenspecifying the same application name caused WebLogic Server to automatically derivea unique name based on the specified name.
JDBC Data SourcesOracle WebLogic Server 12c (12.2.1) includes the following new and changedfeatures:
• Simplified Driver Installation and Update
• Proxy Data Source Support
• JDBC Data Source Support for Multitenancy
• Universal Connection Pool Data Sources
• Connection Leak Profiling Enhancements
• Enhanced Connection-Based System Properties
• Application Continuity Runtime Statistics
• ONS Node List Configuration Enhancements
• DRCP Network Timeout Property
• Enhanced Edition-Based Redefinition (EBR) Documentation
• Guidelines for Planned Maintenance and Database Outages
• Enabling ONS and JDBC Debugging Changes
• Support for Encrypted Passwords in a Data Source Definition
• Enhanced Data Source Shutdown
• Retry Count
• Connection Initialization Callback for Non-Oracle Drivers
• JDBC Store Improved Retry Handling
• JDBC Store Connection Caching Policy
• Gradual Draining
• Shared Pooling
Chapter 2Runtime Improvements
2-13
• WebLogic Server Integration with Oracle Database 12.2 Driver
• Initial Capacity Enhancement in the Connection Pool
Simplified Driver Installation and Update
In previous releases, adding a new JDBC driver or updating a JDBC driverwhere the replacement JAR has a different name than the original JAR requiredupdating the WebLogic Server's classpath to include the location of the JDBC driverclasses. As of Oracle WebLogic Server 12.2.1, you can simply put the drivers inthe $DOMAIN_HOME/lib directory without the need to change the classpath. See AddingThird-Party JDBC Drivers Not Installed with WebLogic Server in Administering JDBCData Sources for Oracle WebLogic Server.
Proxy Data Source Support
Oracle provides a new data source type called the proxy data source, which providesthe ability to switch between databases in a WebLogic Server Multitenant environment.See Using Proxy Data Sources in Administering JDBC Data Sources for OracleWebLogic Server.
JDBC Data Source Support for Multitenancy
Data source configuration and monitoring support has been added for WebLogicServer Multitenant. See Configuring JDBC in Using Oracle WebLogic ServerMultitenant.
Universal Connection Pool Data Sources
Universal Connection Pool (UCP) data sources are now available as an option ifyou wish to use UCP to connect to Oracle Databases. UCP provides an alternativeconnection pooling technology to WebLogic Server connection pooling. See UsingUniversal Connection Pool Data Sources in Administering JDBC Data Sources forOracle WebLogic Server.
Connection Leak Profiling EnhancementsConnection leak profiling enhancements include:
• A new attribute, Set Connection Leak Timeout Seconds, that can be usedinstead of Inactive Connection Timeout Seconds to specify the length of timebefore a reserved connection is considered leaked.
• Two new profile records:
– JDBC Object Closed Usage—Collect profile information about applicationcomponents that close a connection, statement, or result set.
– Local Transaction Connection Leak—Collect profile information aboutapplication components that leak a local transaction (start it but don't commitor rollback the transaction).
See Collecting Profile Information in Administering JDBC Data Sources for OracleWebLogic Server.
Chapter 2Runtime Improvements
2-14
Enhanced Connection-Based System Properties
You can set connection-based system properties using variables based on yourenvironment. See Enabling Connection-Based System Properties in AdministeringJDBC Data Sources for Oracle WebLogic Server.
Application Continuity Runtime StatisticsApplication Continuity (or replay) statistics are available using theJDBCReplayStatisticsRuntimeMBean for generic and Active GridLink data sources.See Viewing Runtime Statistics for Application Continuity in Administering JDBC DataSources for Oracle WebLogic Server.
ONS Node List Configuration EnhancementsYou can now use a property node list to configure the ONS node list. The propertynode list, which can be used instead of a single node list, is a string composed ofmultiple records, with each record consisting of a key=value pair. See ONS ClientConfiguration in Administering JDBC Data Sources for Oracle WebLogic Server.
DRCP Network Timeout PropertyA system property weblogic.jdbc.attachNetworkTimeout is provided that, after anattach to the server, specifies a network timeout that forces a round trip to thedatabase (using an Oracle ping database operation). The timeout is then unset.See Database Resident Connection Pooling in Administering JDBC Data Sources forOracle WebLogic Server.
Enhanced Edition-Based Redefinition (EBR) DocumentationThe documentation that describes this feature has been enhanced to include detailsabout using EBR with JDBC connections, and describes how to configure WebLogicdata sources to use Editions. See Using Edition-Based Redefinition in AdministeringJDBC Data Sources for Oracle WebLogic Server.
Guidelines for Planned Maintenance and Database OutagesProcedures and guidelines have been included for planning and managing databasemaintenance and downtimes for multi data source and Active GridLink (AGL) datasources. See the following topics in Administering JDBC Data Sources for OracleWebLogic Server:
• Planned Database Maintenance with a Multi Data Source
• Managing Database Downtime with AGL Data Sources
Enabling ONS and JDBC Debugging ChangesTo enable ONS and JDBC replay debugging, you must configure java.util.logging.See the following topics in Administering JDBC Data Sources for Oracle WebLogicServer:
• Enabling JDBC Driver Debugging
Chapter 2Runtime Improvements
2-15
• Debugging ONS
Support for Encrypted Passwords in a Data Source Definition
In previous releases, the PasswordEncrypted attribute was not supported in datasource definitions. This restriction has been removed. See Using an EncryptedPassword in a DataSourceDefinition in Developing JDBC Applications for OracleWebLogic Server.
Enhanced Data Source Shutdown
In Oracle WebLogic Server 12.2.1.1.0, new asynchronous, task-based operationshave been added for data source suspend and shutdown. When a data sourceis shutting down, suspend closes all idle connections immediately and closesconnections when returned to the pool. See Shutting Down the Data Source inAdministering JDBC Data Sources for Oracle WebLogic Server.
Retry Count
During a ConnectionInitializationCallback operation, the application may wantto know when the connection work is being replayed. The getReplayAttemptCountmethod on the WLConnection interface is added in WebLogic Server 12.2.1.1.0 toobtain the number of times that replay is attempted on the connection. See ApplicationContinuity Auditing in Administering JDBC Data Sources for Oracle WebLogic Server.
Connection Initialization Callback for Non-Oracle Drivers
As of Oracle WebLogic Server 12.2.1.1.0, you can now configure the connectioninitialization callback that can be called with non-Oracle drivers. See Create anInitialization Callback in Administering JDBC Data Sources for Oracle WebLogicServer.
JDBC Store Improved Retry Handling
In previous releases, a JDBC Store's retry mechanism would make one reconnectattempt, then throw a JDBCStoreException if it was not able to reconnect to thedatabase. In Oracle WebLogic Server 12.2.1.1.0, Oracle allows you to configuremultiple retry attempts over a specified time period. See Configuring JDBC StoreReconnect Retry in Administering the WebLogic Persistent Store.
JDBC Store Connection Caching Policy
Oracle WebLogic Server 12.2.1.1.0 adds an option to reduce the number of JDBCconnections cached by a JDBC store.
See Configuring a JDBC Store Connection Caching Policy in Administering theWebLogic Persistent Store.
Chapter 2Runtime Improvements
2-16
Gradual Draining
When planned maintenance occurs, a planned down service event is processed byWebLogic Server data source. By default, all unreserved connections in the pool areclosed and borrowed connections are closed when returned to the pool. This cancause an uneven performance because:
• New connections need to be created on the alternative instances.
• A logon storm on the other instances can occur.
It is desirable to gradually drain connections instead of closing them all immediately.The application can define the length of the draining period during which connectionsare closed.
In Oracle WebLogic Server 12.2.1.2.0, this feature is supported for an AGL datasource running with Oracle RAC. See Gradual Draining in Administering JDBC DataSources for Oracle WebLogic Server.
Shared Pooling
Oracle WebLogic Server now includes a shared pooling feature for WebLogic datasources. Shared pooling provides the ability for multiple data source definitions toshare an underlying connection pool. See Using Shared Pooling Data Sources inAdministering JDBC Data Sources for Oracle WebLogic Server.
WebLogic Server Integration with Oracle Database 12.2 Driver
In Oracle WebLogic Server 12.2.1.3.0, WebLogic JDBC adds the Oracle Database12.2.0.1 client jar files and additional integration capabilities with several new OracleDatabase 12.2 features. See WebLogic JDBC Features for Oracle Database 12.2 inAdministering JDBC Data Sources for Oracle WebLogic Server.
Initial Capacity Enhancement in the Connection Pool
WebLogic Server 12.2.1.3 enhances creation of initial capacity connections in a datasource by providing control over connection retry, early failure, and critical resources.See Initial Capacity Enhancement in the Connection Pool in Administering JDBC DataSources for Oracle WebLogic Server.
JTAThis release of WebLogic Server includes the following new and changed JTAfeatures:
• Transactions without TLog Write
• Transaction Guard
• Network Channels for JTA Communication
Chapter 2Runtime Improvements
2-17
Transactions without TLog WriteOracle improves XA transaction performance by providing the option to eliminate thewriting of XA transactions to the TLog. XA transaction resources (determiners) areused during transaction recovery when a TLog is not present. See XA Transactionswithout Transaction TLogs Write in Developing JTA Applications for Oracle WebLogicServer.
Transaction Guard
In release 12.2.1.3.0, Oracle WebLogic Server adds transaction guard integration withWebLogic JDBC data sources. Transaction guard provides at-most-once executionduring planned and unplanned outages and prevents duplicate submissions. SeeUsing Transaction Guard.
Network Channels for JTA CommunicationOracle WebLogic Server 12c (12.2.1.4.0) provides options to configure customnetwork channels for JTA communication. The network channels are usedfor JTA interserver communication. See Configuring Network Channels for JTACommunication in Developing JTA Applications for Oracle WebLogic Server.
MessagingThis release of WebLogic Server includes the following new and changed messagingfeatures:
• JMS Per-JVM Load Balancing
• JMS Failover Limit
• JMS Object-Based Security
• Messaging Support for Multitenancy
• Simplified JMS Cluster Configuration and High Availability Enhancements
• Service Restart In Place
• Message Limit in a Subscription
JMS Per-JVM Load BalancingYou can now enable 'Per-JVM' instead of 'Per-Member' message load balancingbehavior for new or forwarded messages. With Per-JVM, only one member of adistributed destination on each WebLogic Server JVM gets new messages regardlessof the number of members hosted by a JVM.
This is useful for evenly distributing messages among servers in a cluster that hasbeen shrunk due to decreased loads, but that also retains failed over members inorder to process any of the failed-over members' recovered messages. See Load-Balancing Heuristics in Administering JMS Resources.
Chapter 2Runtime Improvements
2-18
JMS Failover LimitYou can now set a Fail Over Limit to limit the number of cluster targeted JMSServer or SAF Agent instances that can fail over to a particular JVM.
This is useful for preventing too many JMS instances from failing over to a single JVM.See Additional Configuration Options for JMS Services.
JMS Object-Based SecurityWebLogic JMS clients can use a new simplified object-based security feature.This feature is useful for multithreaded clients that access secured WebLogic JMSdestinations in order to minimize or even eliminate the need for additional codeto transfer security subjects between threads. See Understanding JMS Security inDeveloping JMS Applications for Oracle WebLogic Server.
Messaging Support for Multitenancy
Note:
WebLogic Server Multitenant domain partitions, resource groups, resourcegroup templates, and virtual targets are deprecated in WebLogic Server12.2.1.4.0 and will be removed in the next release.
WebLogic JMS provides support for the WebLogic Messaging Service in WebLogic12.2.1 and later environments, including:
• Core WebLogic Messaging components including modules, JMS resources, pathservice, stores, and admin helpers such as one that can locate an available JMSdestination
• Integration solutions, including the Messaging Bridge, JMS pools, and foreign JMSservers
• Store-and-Forward (SAF) agents
• AQ JMS using foreign JMS servers
See Configuring Messaging in Using Oracle WebLogic Server Multitenant.
Simplified JMS Cluster Configuration and High Availability Enhancements
Oracle WebLogic Server 12.2.1 and later provides enhanced support for simplifiedmessaging configurations that set up JMS using cluster targeting instead ofindividually configuring and targeting JMS resource artifacts on each server in acluster. This enhanced support for cluster targeted JMS improves high availability andremoves the limitations from previous releases.
Cluster targeting now supports:
• High availability features:
Chapter 2Runtime Improvements
2-19
– Automatic service migration—automatically restarts a failed JMS instance on adifferent WebLogic Server instance.
– Fail-back—returns an instance to its original host server when the host serverrestarts.
– Restart-in-place—automatically restarts a failed JMS instance on its runningWebLogic Server instance.
• Unit-of-Order and Unit-of-Work messaging
• Singleton destinations (in addition to already supported distributed destinations)
• SAF agents, bridges, and path services (in addition to already supported JMSservers and stores)
See Simplified JMS Cluster and High Availability Configuration in Administering JMSResources for Oracle WebLogic Server.
Service Restart In PlaceService Restart In Place automatically recovers a failed custom store and itsdependent JMS services on their original running WebLogic Server. It can beconfigured independently of whole server migration or service migration.
WebLogic Server 12.2.1.3.0 extends Service Restart In Place beyond previousversions to support any custom store with any migration policy, where the store can betargeted to a standalone server, a cluster, or a migratable target.
See Service Restart In Place in Administering the WebLogic Persistent Store.
Message Limit in a SubscriptionIn Oracle WebLogic Server 12.2.1.3.0, WebLogic JMS provides a message limit optionat the topic subscription level as a way to help prevent individual overloadedsubscriptions from using up all available resources. If a subscription reaches itsconfigured limit on a FIFO sorted destination, then, by default, the oldest messageson the subscription are ejected to make room for newer messages. You can set amessage limit on both stand-alone and distributed topics.
See Subscription Message Limits in Tuning Performance of Oracle WebLogic Server.
Monitoring WebSocket Applications
In Oracle WebLogic Server 12c (12.2.1), you can monitor message statisticsand runtime properties for WebSocket applications and endpoints. Endpoint-levelmonitoring collects information per individual endpoint, while application-levelmonitoring aggregates information from all endpoints deploying in the givenapplication.
The following MBeans have been added or modified to support WebSocket monitoring:
• WebAppComponentRuntimeMBean
• WebsocketApplicationRuntimeMBean
• WebsocketEndpointRuntimeMBean
• WebsocketMessageStatisticsRuntimeMBean
Chapter 2Runtime Improvements
2-20
• WebsocketBaseRuntimeMBean
You can also use the WebLogic Server Administration Console or Fusion MiddlewareControl to monitor WebSocket applications.
See Monitoring WebSocket Applications in Developing Applications for OracleWebLogic Server.
Policy Classloader
This release of WebLogic Server integrates the policy classloader implementationas the default system class loader when using WebLogic start scripts. The policyclassloader improves class loader performance and server startup time and issupported in all WebLogic modes (development and production).
See Class Caching With the Policy Classloader in Developing Applications for OracleWebLogic Server.
ReadyApp Integration with WebLogic Server
This release of WebLogic Server integrates the ReadyApp framework. At times,applications are not fully initialized when WebLogic Server completed its startupprocess. By using the ReadyApp framework, applications can register with theWebLogic Server ReadyApp during the deployment process and influence thetrue readiness state of the server instance. Applications notify ReadyApp of theirapplication state so server instances can determine if an application is fully initializedand ready to accept requests. ReadyApp also allows load balancers to detect serverreadiness by providing a reliable health-check URL.
See Using the ReadyApp Framework in Deploying Applications to Oracle WebLogicServer.
RESTful Web Services
This release of Oracle WebLogic Server provides the following new and changedfeatures for RESTful web services:
• Provides support for Jersey 2.x (JAX-RS 2.0 RI) by default in this release.Registration as a shared library with WebLogic Server is no longer required.
• Provides enhanced monitoring of RESTful web services in the WebLogicAdministration Console, including enhanced runtime statistics for your RESTfulapplications and resources, detailed deployment and configuration data, globalexecution statistics, and resource and resource method execution statistics. Thefollowing runtime MBeans have been modified or added to support enhancedmonitoring:
– JaxRsApplicationRuntimeBean
– JaxRSExceptionMapperStatisticsRuntimeMbean
– JaxRsExecutionStatisticsRuntimeMBean
– JaxRsResourceMethodBaseRuntimeMBean
– JaxRsResourceMethodRuntimeMBean
Chapter 2Runtime Improvements
2-21
– JaxRsResourceRuntimeMBean
– JaxRsResponseStatisticsRuntimeMBean
– JaxRsSubResourceLocatorRuntimeMBean
– JaxRsUriRuntimeMBean
• Includes the ability to disable RESTful web services monitoring at the individualapplication level, or globally at the domain level.
• Reflects support for the Jersey 2.21.1 (JAX-RS 2.0 RI).
• Supports securing Jersey 2.x (JAX-RS 2.0 RI) web services using Oracle WebServices Manager (OWSM) security policies.
• Adds support for Java EE 7.
See Introduction to RESTful Web Services in Developing and Securing RESTful WebServices for Oracle WebLogic Server.
Simple WLST APIs for Dynamic Clusters
This release of WebLogic Server adds WLST commands to improve usability fordynamic cluster lifecycle operations. By using the WLST scaleUp and scaleDowncommands, you can easily start and stop dynamic servers in a dynamic cluster andexpand or shrink the size of a dynamic cluster.
See Starting and Stopping Servers in Dynamic Clusters and Expanding or ReducingDynamic Clusters in Administering Clusters for Oracle WebLogic Server.
ThreadLocal Clean Out Support for Work Managers
This release of Oracle WebLogic Server enhances ThreadLocal clean out support inWork Managers. To clean up stray ThreadLocal use by applications and third-partylibraries, configure the eagerThreadLocalCleanup attribute in the KernelMBean. Bydefault, the self-tuning thread pool only cleans up ThreadLocal storage when a threadreturns to a standby pool and after an application is undeployed. See ThreadLocalClean Out in Administering Server Environments for Oracle WebLogic Server.
Manageability ImprovementsOracle WebLogic Server 12c (12.2.1) continues to provide new management featuresthat simplify the configuration, monitoring, and ongoing management of WebLogicdomains and applications with regards to elasticity support in dynamic clusters,multitenancy administration, REST, security, patching, and more.
These new features are described in the following sections:
• Elasticity Support for Dynamic Clusters
• Resource Groups
• Resource Group Templates and Resource Overrides
• Named Concurrent Edit Sessions
• Configuration Overriding
Chapter 2Manageability Improvements
2-22
• REST Resources for WebLogic Server Management
• Fusion Middleware Control
• Security
• Logging Enhancements
• WebLogic Diagnostic Framework
• WebLogic Server Development and Supplemental Distribution
• Zero Downtime Patching
• Applied Patch List
• WLST
• Resource Consumption Management
• SNMPv3 Default Protocol
Elasticity Support for Dynamic Clusters
This release of WebLogic Server introduces elasticity. Elasticity enables the automaticscaling of dynamic clusters and re-provisioning of associated resources based ondemand. The Elasticity Framework leverages the WebLogic Diagnostic Framework(WLDF) policies and actions system. See Overview in Configuring Elasticity inDynamic Clusters for Oracle WebLogic Server.
Resource Groups
Note:
Resource groups are deprecated in WebLogic Server 12.2.1.4.0 and will beremoved in the next release.
WebLogic Server Multitenant introduces resource groups as a convenient way togroup together Java EE applications and the resources they use into a distinctadministrative unit within the domain. The resources and applications in a resourcegroup are "fully qualified" in that the administrator provides all the information neededto start or connect to those resources, including credentials for connecting to a datasource and targeting information for Java EE applications. A resource group will eithercontain these deployable resources directly or refer to a resource group templatewhich contains the resources. Resource groups can be defined at the domain level, orbe specific to a domain partition.
See Configuring Resource Groups in Using Oracle WebLogic Server Multitenant.
Resource Group Templates and Resource Overrides
Chapter 2Manageability Improvements
2-23
Note:
Resource group templates and resource override configuration MBeans aredeprecated in WebLogic Server 12.2.1.4.0 and will be removed in the nextrelease.
Resource group templates are a named, domain-level collection of deployableresources intended to be used as a pattern by (usually) multiple resource groups.Each resource group that refers to a given template will have its own runtime copies ofthe resources defined in the template. A resource group template is a convenient wayto define and replicate resources for multiple tenants. Resource group templates makeit very easy to deploy the same collection of applications and resources to multipledomain partitions.
Resource group templates are particularly useful in SaaS environments whereWebLogic Server Multitenant activates the same applications and resources multipletimes, once per domain partition. Some of the information about such resourcesis the same across all domain partitions, while some of it, such as JMS queuesand database connections, varies from one partition to the next. WebLogic ServerMultitenant provides several methods for overriding resource definitions:
• Resource Override Configuration MBeans
• Resource deployment plans
• Partition-specific application deployment plans
Administrators can employ and combine any of these techniques.
See Configuring Resource Group Templates and Configuring Resource Overrides inUsing Oracle WebLogic Server Multitenant.
Named Concurrent Edit Sessions
In previous releases, WebLogic Server supported only one active configuration editsession at a time. The system administrator got a global edit lock, made changes, andthen activated them. Other administrators could not make changes at the same time.However, this release of Oracle WebLogic Server enables multiple, named concurrentedit sessions, which allows more than one administrator to make configurationchanges at the same time. This is typically useful when multiple administrators workin different parts of the system. Also, when configuring a system takes a long timebecause of the serial execution of configuration commands, a single administrator canopen multiple named edit sessions. This saves time by running the configuration editsessions in parallel.
In a multitenant environment, more than one administrator will need to makeconfiguration changes concurrently. A multitenant WebLogic domain contains multiplepartitions each with its own administrator. Partition administrators must be able tomake configuration changes to their partitions and the resources deployed in themwithout affecting other partition administrators or the WebLogic system administrator.Multiple, named concurrent edit sessions support one or more configuration editsessions per partition plus global configuration edit sessions.
See Managing Named Concurrent Edit Sessions in Using Oracle WebLogic ServerMultitenant.
Chapter 2Manageability Improvements
2-24
Configuration OverridingConfiguration overriding lets administrators place configuration information, containedin an XML file, in a known location where running servers identify and load it,overriding aspects of the existing configuration.
You can use configuration overriding (also called situational configuration) to changesettings such as server debugging flags, timeout values, or diagnostics settings,without running the Administration Server. The configuration overrides are targetedto Managed Servers but can also be applied to the Administration Server.
Configuration overrides can update configuration information coming from theconfig.xml file or system resource files that exist in the jdbc, jms, and diagnosticssubdirectories of the domain config directory. The overrides may have an expirationtime or they can be permanent; no expiration time need be specified.
See Configuration Overriding in Understanding Domain Configuration for OracleWebLogic Server.
REST Resources for WebLogic Server ManagementRESTful Management Services are a publicly documented programming interface toOracle WebLogic Server. In each release of WebLogic Server, the availability of RESTresources for WebLogic Server administration has been enhanced and extended. Inthis release of Oracle WebLogic Server, WebLogic RESTful management resourcesprovide a comprehensive public interface for configuring, monitoring, deploying andadministering WebLogic Server in all supported environments.
For information about the RESTful management resources provided in this releaseof WebLogic Server, see About the WLS RESTful Management Interface inAdministering Oracle WebLogic Server with RESTful Management Services.
Fusion Middleware ControlFusion Middleware Control provides management support for all Fusion Middlewarecomponents, including WebLogic Server. Use Fusion Middleware Control to manageWebLogic Server when using other Fusion Middleware products in addition toWebLogic Server.
In this release of WebLogic Server, the following subsets of functionality are nowavailable in Fusion Middleware Control:
• Create WebLogic Server clusters, server instances, domains, machines, andserver templates
• Configure and deploy applications and libraries
• Create and configure UCP and proxy data sources
• Create and configure JMS servers, Store-and-Forward agents, JMS modules, JMSresources, path services, messaging bridges, and messaging bridge destinations
• Create and configure security realms
• Manage WebLogic Server diagnostics
• Configure elasticity for dynamic clusters
Chapter 2Manageability Improvements
2-25
• Configure Coherence clusters
• Manage WebLogic Server in a multitenant environment
See Administration in Administering Oracle WebLogic Server with Fusion MiddlewareControl.
As of release 12.2.1.1.0, you can use Fusion Middleware Control to connect directly toa domain partition instead of logging in at the domain level. When you do this the username that you specify is validated against the security realm and the managementidentity domain for that partition. See Configuring Security in Using Oracle WebLogicServer Multitenant.
SecurityThe new security features provided in Oracle WebLogic Server 12c (12.2.1.x) aredescribed in the following sections:
• Support for Secured Production Mode
• Oracle Identity Cloud Service Security Provider
• New Method for Two-Way SSL Authentication in Java Clients Using JNDI
• Java EE 7 Standards Support
• LDAP Authentication Provider Manageability Enhancements
• Default Minimum TLS Protocol Version
• Support for weblogic-jwt-token
• SAML 2.0 Implementation Updates
• JEP 290 Utilization
• AES 256-Bit Encryption Used in New Domains
• Signing and Encryption Support for SAML 2.0 Assertions
Support for Secured Production ModeOracle WebLogic Server 12.2.1.3.0 and later provides support for securing yourproduction environment using the secured production mode feature. To ensure ahighly secure environment for your WebLogic Server applications and resources,enable secured production mode and related security settings for your domain in oneof the following ways:
• Use the WebLogic Server Administration Console to enable secured productionmode and related security settings for your domain. See Secure your productiondomain in Oracle WebLogic Server Administration Console Online Help.
• Use the Fusion Middleware Control to enable secured production mode andrelated security settings. See Configure domain security in Administering OracleWebLogic Server with Fusion Middleware Control.
• Use WLST offline while creating the domain. The setOption WLST offlinecommand includes a new secure value for the ServerStartMode argument tostart your server in secured production mode. See setOption in WLST CommandReference for Oracle WebLogic Server.
Chapter 2Manageability Improvements
2-26
• Use WLST online to enable secured production mode for your existing productiondomain. See Using WLST Online to Update an Existing WebLogic Domain inUnderstanding the WebLogic Scripting Tool.
Note:
You cannot upgrade domains prior to 12.2.1.3.0 to run in secured productionmode. Only domains new in 12.2.1.3.0 can be configured to run in securedproduction mode.
For more information about using secure mode, see the following topics:
• Install and Configure WebLogic Server in a Secure Manner in Securing aProduction Environment for Oracle WebLogic Server
• Configuring Security for a WebLogic Domain in Administering Security for OracleWebLogic Server
Oracle Identity Cloud Service Security ProviderWebLogic Server 12.2.1.3.0 includes a new security provider, Oracle Identity CloudIntegrator, that combines authentication and identity assertion into a single provider.The provider establishes identity on WebLogic Server when the identity store is theOracle Identity Cloud Service.
The Oracle Cloud Integrator provider supports:
• Basic authentication with the Oracle Identity Cloud Service using user names andpasswords.
• Perimeter authentication (identity assertion) using Oracle Identity Cloud Serviceidentity tokens. The provider also supports perimeter authentication for usersauthenticated by the Identity Cloud Service, and for protected resources usingOracle Identity Cloud Service access tokens.
• A multiple identity store environment. You can use the provider to access theOracle Identity Cloud Service as a single source of users, or in a hybridenvironment in combination with other identity stores.
• A Single Sign-on (SSO) Synchronization Filter to synchronize the remote cloudSSO session with the local container session.
• Identity domains, which are used to represent the tenancy of users and groups.
• One-way SSL to establish trust between the provider and the Oracle Identity CloudService.
In WebLogic Server 12.2.1.4.0, two new configuration attributes,ServerNotAvailableCounterInterval and ServerBackoffEnabled, were added tothe OracleIdentityCloudIntegratorMBean to handle authentication failures that canoccur when the Oracle Identity Cloud Service is unavailable or not responding toauthentication requests.
See Configuring the Oracle Identity Cloud Integrator Provider in Administering Securityfor Oracle WebLogic Server.
Chapter 2Manageability Improvements
2-27
New Method for Two-Way SSL Authentication in Java Clients Using JNDI
As of release 12.2.1.2.0 a new method, setSSLContext(), has been added tothe weblogic.jndi.Environment class for configuring two-way SSL authenticationfor Java clients using JNDI. Alternatively, you can use loadLocalIdentity().The methods previously recommended, setSSLClientCertificate() andsetSSLClientKeyPassword(), have been deprecated in this release. See Two-WaySSL Authentication with JNDI in Developing Applications with the WebLogic SecurityService.
Java EE 7 Standards Support
This release of WebLogic Server supports the following Java EE 7 standards andfeatures for security:
• Java Authorization Contract for Containers 1.5 (JSR 115)
• Java Authentication Service Provider Interface for Containers (JASPIC) 1.1 (JSR196)
• Packaged Permissions (Java EE 7 Platform Specification)
• Uncovered HTTP methods for Servlet 3.1 (JSR 340)
LDAP Authentication Provider Manageability Enhancements
The following enhancements have been added to the LDAP Authentication provider toimprove the configuration process:
• LDAP Authentication provider performance enhancements for improved caching,searching, and LDAP server connection handling, such as:
– The ability to collect hit/miss metrics on user and group caching, allowingyou to determine the best settings for user and group caching to maximizeresponse time and throughput.
– Support for specifying a timeout on the LDAP server connection.
• Support for testing the LDAP server connection prior to activating the LDAPAuthentication provider, similar to the way JDBC connections can be tested duringdata source configuration. Testing occurs automatically at the time you activate thethis provider: if the test succeeds, the provider is activated.
See Improving the Performance of WebLogic and LDAP Authentication Providers inAdministering Security for Oracle WebLogic Server.
Default Minimum TLS Protocol Version
As of Oracle WebLogic Server 12.2.1, the default minimum version of the TransportLayer Security (TLS) protocol configured in WebLogic Server is Version 1.1.
Support for weblogic-jwt-token
Chapter 2Manageability Improvements
2-28
The WebLogic Identity Assertion and WebLogic Credential mapping providers havebeen enhanced to include support for the JSON web token, weblogic-jwt-token. Thistoken type, which is configured by default in these security providers, is used internallyfor propagating identity among web applications in the domain.
SAML 2.0 Implementation UpdatesThe SAML 2.0 implementation includes the following updates in this release:
• Use of the SHA2 signature algorithm as the default for signing SAML requestsand responses. In previous releases, the SAML 2.0 implementation used theSHA1 signature algorithm to sign SAML requests and responses. If required forbackward compatibility, you can use the SHA1 signature algorithm by setting theJava system property com.bea.common.security.saml2.useSHA1SigAlgorithm totrue. To do so, specify the following option in the Java command that startsWebLogic Server:
-Dcom.bea.common.security.saml2.useSHA1SigAlgorithm=true
• By default, certificates that are expired or not yet valid are no longer used inSAML signing. To allow use of these certificates, set the Java system propertycom.bea.common.security.saml2.allowExpiredCerts to true. For example,specify the following option in the Java command that starts WebLogic Server:
-Dcom.bea.common.security.saml2.allowExpiredCerts=true
JEP 290 UtilizationTo improve security, WebLogic Server uses the JDK JEP 290 mechanism to filterincoming serialized Java objects and limit the classes that can be deserialized.Although it is a useful feature, serialization in Java can also be used to inject maliciouscode using serialized Java objects that can cause Denial of Service (DoS) or RemoteCode Execution (RCE) attacks during deserialization. WebLogic Server uses the JDK JEP 290 mechanism to protect against thesemalicious attacks as follows:
• Implements a WebLogic Server-specific object input filter to enforce a blocklist ofprohibited classes and packages for input streams used by WebLogic Server. Thefilter also enforces a default value for the maximum depth of a deserialized objecttree. In WebLogic Server 12.2.1.4.0 and later, the scope of the default filter is setto global and a system property, weblogic.oif.serialFilterLogging, has beenadded that you can use to log the contents of the current default filter.
• Provides system properties that you can use to add or remove classes andpackages from the default filter to blocklist or allowlist particular classes. Youcan also use the system properties to filter deserialized classes based on thenesting depth of the deserialized object, the number of internal references in thedeserialized object, the size of object arrays, and/or the maximum size in bytes ofa deserialized object.
See Configuring a Custom JEP 290 Deserialization Filter in Administering Security forOracle WebLogic Server
Chapter 2Manageability Improvements
2-29
AES 256-Bit Encryption Used in New DomainsAs of Oracle WebLogic Server 12.2.1.4.0, WebLogic Server uses AES 256–bitencryption to protect sensitive configuration and runtime values. Only new domainscreated in this release and later use AES 256–bit encryption.
Domains created with earlier releases of WebLogic Server use AES 128–bitencryption. The encryption level of a domain cannot be upgraded. If you upgrade adomain to 12.2.1.4.0 or later, then the encryption level remains at AES 128-bit.
Note:
All server and Node Manager instances in a domain must be at the sameencryption level. If you require AES 256-bit encryption, you cannot use anupgraded domain and must create a new 12.2.1.4.0 domain.
Signing and Encryption Support for SAML 2.0 Assertions
This release of WebLogic Server supports the following new features for SAMLencryption and signing:
• In previous releases, WebLogic Server did not require SAML assertions to besigned by default. If the signature section was omitted from a SAML response,then no signature verification was performed. This behavior could be used tobypass authentication and gain access as an arbitrary user. In WebLogic Server12.2.1.4.0, the default setting is changed to accept only signed assertions. In theWebLogic Server Administration Console, the Only accept signed assertionssetting on the SAML 2.0 Service Provider configuration page is now selected bydefault.
• In this release, WebLogic Server supports encrypted SAML assertions for SAML2.0. To implement confidentiality of individuals or organizations, the following newencryption attributes have been added to the SingleSignOnServicesMBean. Youcan configure these attributes using the WebLogic Server Administration Consoleor WLST:
– AssertionEncryptionEnabled
– KeyEncryptionAlgorithm
– DataEncryptionAlgorithm
– MetadataEncryptionAlgorithms
– AssertionEncryptionDecryptionKeyAlias
– AssertionEncryptionDecryptionKeyPassPhrase
– AssertionEncryptionDecryptionKeyPassPhraseEncrypted
See Configuring SAML 2.0 Services in Administering Security for Oracle WebLogicServer.
Chapter 2Manageability Improvements
2-30
Logging EnhancementsIn this release of WebLogic Server, the WebLogic logging services include thefollowing changes:
• Partition scope logging — The logs for several WebLogic Server components,such as partition scope JMS, SAF, and servlet resources, are kept in partition-specific log files. The logs for server and domain scope resources, such as theserver scope HTTP access log, the Harvester component, the Instrumentationcomponent, and also the server and domain logs, can be tagged with partition-specific information to enable logging that is performed on behalf of a partition tobe identified and made available to partition users.
See Monitoring and Debugging Partitions in Using Oracle WebLogic ServerMultitenant.
Note:
To revert the format of generated log messages to thatthey are compatible with the format used in versions ofWebLogic Server prior to 12.2.1, you can enable theDomainMBean.LogFormatCompatibilityEnabled attribute. See Log FileFormat Compatibility with Previous WebLogic Server Versions inConfiguring Log Files and Filtering Log Messages for Oracle WebLogicServer.
• Monitoring for excessive logging — When enabled, the logging service monitorsthe domain for excessive rates of logging and, when present, suppressesmessages that are being generated repeatedly.
See Preventing Excessive Logging in Configuring Log Files and Filtering LogMessages for Oracle WebLogic Server.
• Server log rotation behavior — In WebLogic Server 12.2.1.3.0, the loggingbehavior has changed for WebLogic Server instances that are started using NodeManager. In previous releases, Node Manager always rotated the server log filewhen the server was restarted. As of 12.2.1.3.0, the log file rotation on the startupof a Managed Server instance can be configured using the RotateLogOnStartupattribute on that server’s LogMBean. The default value of the RotateLogOnStartupattribute is true development mode, and false in production mode. Note that thebehavior of other log file rotation parameters that are specified in the LogMBean forthe Managed Server instance, such as size and time, are unaffected. However, thevalue of the RotateLogOnStartup setting is now honored by Node Manager.
WebLogic Diagnostic FrameworkIn this release of WebLogic Server, the WebLogic Diagnostic Framework (WLDF)includes the following changes:
• The terms watch and notification are replaced by policy and action, respectively.However, the definition of these terms has not changed.
• Four new action types are introduced as part of the Policy and Action componentof WLDF. Actions are triggered when a policy expression evaluates to true. In
Chapter 2Manageability Improvements
2-31
addition to JMX notification actions, JMS message actions, SMTP (e-mail) actions,SNMP trap actions, and diagnostic image actions, WebLogic Server now supportsthe following new action types:
– Elastic actions — scale a dynamic cluster up or down
– REST notification — sends a notification to a REST endpoint
– Script — executes an external command line script
– Log — sends a custom message to the server log
– Heap dump — captures heap dumps when certain runtime conditions are met(added in 12.2.1.1.0)
– Thread dump — capture thread dumps when certain runtime conditions aremet (added in 12.2.1.1.0)
In addition, WLDF enhances the SMTP action to allow you to send custom subjectand body elements in an email message.
See Configuring Actions in Configuring and Using the Diagnostics Framework forOracle WebLogic Server.
• This release of WebLogic Server introduces dynamic debug patches. Dynamicdebug patches allow you to capture diagnostic information using a patch thatis activated and deactivated without requiring a server restart. Dynamic debugpatching requires target WebLogic Server instances to be started with the WLDFinstrumentation agent. See Using Debug Patches in Configuring and Using theDiagnostics Framework for Oracle WebLogic Server.
• This release of WebLogic Server introduces smart rules. Smart rules areprepackaged policy expressions with a set of configurable parameters that allowthe end user to create a complex policy expression just by specifying the valuesfor these configurable parameters. See Configuring Smart Rule Based Policies inConfiguring and Using the Diagnostics Framework for Oracle WebLogic Server.
• When you initiate a diagnostic image capture, the images produced by thedifferent server subsystems are captured and combined into a single .zip file.In previous releases of WebLogic Server, the components of a diagnostics imagecapture file all used the .img extension even though these files are all in textformat and can be viewed in a text editor. As of WebLogic Server 12.2.1, the fileextensions have been updated to either .txt or .xml to clarify that these are textfiles.
See Data Included in the Diagnostics Image Capture File in Configuring and Usingthe Diagnostics Framework for Oracle WebLogic Server.
• The Java Expression Language (EL) is now supported as the recommendedlanguage to use in policy expressions. The WLDF query language is deprecated.
• The WLDFScheduleBean is now available for policies that are configured withthe Harvester rule type and the Java EL expression language. These policies,called scheduled policies, use the WLDFScheduleBean for scheduling all metriccollection. Even though these policies are configured as Harvester rule types, theydo not use the Harvester for metric collection or for scheduling.
• The following enhancements have been made to WLDF integration with JavaFlight Recorder:
– Improvements to execution context ID (ECID) tracing and correlation in servletJFR events and SOAP JFR events
Chapter 2Manageability Improvements
2-32
– Support for relationship ID (RID) tracing, including within standalone WebLogicServer environments
– Support for log level propagation in the diagnostic context within standaloneWebLogic Server
See Using WLDF with Java Flight Recorder.
• WLST command changes, described in WLST.
WebLogic Server Development and Supplemental Distribution
As of WebLogic Server 12.2.1, the WebLogic Server Development and Supplementaldistributions are available as JAR files and are installed using the java command. Theinstallation uses the Oracle Universal Installer (OUI) and is automatically done in silentmode; you only need to specify the ORACLE_HOME location for the installation.
Zero Downtime Patching
WebLogic Zero Downtime Patching (ZDT Patching) automates the rollout of out-of-place patching or updates across a domain while allowing your applications tocontinue servicing requests. To use ZDT Patching, you create a workflow thatorchestrates how updates are rolled out, and then you execute the workflow usinguse either WLST or the WebLogic Server Administration Console.
ZDT Patching supports the following workflow types:
Feature Description
Move servers to apatched OracleHome
Transitions the Administration Server or clusters, or both, to another OracleHome that has already been patched using OPatch.
Update to a newJava version
Updates the Administration Server or clusters, or both, to use a newlyinstalled Java Home.
Deploy updatedapplications
Deploys updated applications to the selected clusters.
Perform a rollingrestart of servers
Sequentially and safely restarts the Administration Server or servers in theselected clusters, or both, including graceful shutdown and restart.
For a comprehensive overview of ZDT patching, see Introduction to Zero DowntimePatching in Administering Zero Downtime Patching Workflows.
In Oracle WebLogic Server 12.2.1.1.0, ZDT Patching is enhanced to provide supportfor the following additional features:
• Starting the Administration Server without a dependency on Node Manager— Inthe previous release, for the rollout to be successful, the Administration Server hadto be started using Node Manager. This restriction is now removed. See Startingthe Administration Server in Administering Zero Downtime Patching Workflows.
• To support multitenancy and partitions, the following new features have beenintroduced:
– Rolling restart of partitions—ZDT Patching allows WebLogic Serveradministrators and partition administrators to perform the rolling restart
Chapter 2Manageability Improvements
2-33
of partitions. See Initiating a Rolling Restart of Servers or Partitions inAdministering Zero Downtime Patching Workflows
– Rolling out application updates to partitions and resource groups—ZDTPatching now provides application rollout capabilities to both partitionsand resource groups. See Rolling Out Updated Applications: Overview inAdministering Zero Downtime Patching Workflows.
In Oracle WebLogic Server 12.2.1.3.0, ZDT Patching is enhanced to provide supportfor custom hooks. ZDT custom hooks provide a flexible mechanism for modifyingthe patching workflow by executing additional scripts at specific extension points inthe patching rollout. This functionality can be used by administrators and applicationdevelopers for a variety of purposes, including the following:
• To modify Java properties files while the servers are down. For example, changingsecurity settings in the Java home directory.
• To perform additional backup operations on each node
• To run any script on cloud servers while upgrading services
• To include any operation that is specific to a particular type of rollout but that is notappropriate to include in the base patching workflow
For complete details about using custom hooks in ZDT Patching workflows, seeModifying Workflows Using Custom Hooks in Administering Zero Downtime PatchingWorkflows.
Applied Patch List
Oracle WebLogic Server 12.2.1.3.0 introduces the ability to obtain the list of patchesthat have been applied to a WebLogic Server instance. The applied patch list isavailable by accessing either the weblogic.log.DisplayPatchInfo system property orthe ServerRuntimeMBean.PatchList attribute, as follows:
• You can access the weblogic.log.DisplayPatchInfo system property at systemstartup by specifying the -Dweblogic.log.DisplayPatchInfo=true option, or byrunning the weblogic.version utility.
• You can access the ServerRuntimeMBean.PatchList attribute using WLST, REST,the WebLogic Server Administration Console, or JMX.
See Obtaining a List of Applied Patches in Upgrading Oracle WebLogic Server.
WLSTThis section describes new WLST commands for WebLogic Server and changes toexisting WLST commands in this release of WebLogic Server.
New Domain Commands
The following WLST commands related to domain creation and domain extension areadded in this release of WebLogic Server :
• setTopologyProfile—Sets the topology profile at domain creation to eitherCompact or Expanded.
Chapter 2Manageability Improvements
2-34
• selectTemplate—Selects an existing domain or extension template for creating orextending a domain.
• selectCustomTemplate—Selects an existing custom domain or extension templatefor creating or extending a domain.
• loadTemplates—Loads all templates that were selected using the selectTemplateor selectCustomTemplate commands.
• readTemplateForUpdate—Opens an existing domain template for templateupdate.
• unselectTemplate—Deselects a currently selected template.
• unselectCustomTemplate—Deselects a currently selected custom template.
• showTemplates—Displays all currently selected and loaded templates.
• showAvailableTemplates—Displays all currently selected templates for loading.
New Diagnostic Commands
The following diagnostics commands were added in this release of WebLogic Server:
• purgeCapturedImages—Purges the diagnostic image files on the server as per thespecified age criteria.
• listDebugPatches—Lists active and available debug patches on the specifiedtargets.
• showDebugPatchInfo—Displays details about a debug patch on the specifiedtargets.
• activateDebugPatch—Activates a debug patch on the specified targets.
• deactivateDebugPatches—Deactivates debug patches on the specified targets.
• deactivateAllDebugPatches—Deactivates all debug patches on the specifiedtargets.
• listDebugPatchTasks—Lists debug patch tasks from the specified targets.
• purgeDebugPatchTasks—Purges debug patch tasks from the specified targets.
• getAvailableDiagnosticDataAccessorNames—Gets the diagnostic data accessornames that are currently available on a server or partition.
• exportHarvestedTimeSeriesData—Exports the harvested metric data within thespecified internal, in CSV format.
• exportHarvestedTimeSeriesDataOffline—Exports the harvested metric data inoffline mode within the specified internal, in CSV format.
In addition, a new optional parameter, last, is available to the following commands:
• exportDiagnosticData
• exportDiagnosticDataFromServer
• exportHarvestedTimeSeriesData
• exportHarvestedTimeSeriesDataOffline
The last option allows you to specify the timestamp range specification for the last nrecords. When specified, the beginTimestamp and endTimestamp options are ignored.
Chapter 2Manageability Improvements
2-35
The format is XXd YYh ZZm. For example, 1d 5h 30m specifies data that is one day, fivehours and 30 minutes old. You can specify any combination of day, hour, and minutecomponents in any order.
New Node Manager Commands
The following Node Manager WLST commands were added in this release ofWebLogic Server:
• nmrestart—Restarts the Node Manager instance.
• nmExecScript—Executes the named script using the connected Node Manager.
New Edit Session Commands
The following WLST edit session management commands were added in this releaseof WebLogic Server:
• createEditSession—Creates a new WLST edit session.
• showEditSession—Displays information about the specified edit sessions.
• destroyEditSession —Removes an open edit session.
• edit(editSessionName)—Creates a new edit session with the specified name ornavigates to an existing edit session with the specified name.
• resolve—Detects any external modifications and conflicts, and resolves them.
New System Component Commands
The following system component WLST commands were added in this release ofWebLogic Server:
• resync—Resynchronizes configuration files for a system component.
• resyncAll—Resynchronizes configuration files for all system components.
• showComponentChanges—Displays changes to a system component's configurationfiles on a remote node.
• pullComponentChanges—Removes changes to a system component'sconfiguration files on a remote node.
• enableOverWriteComponentChanges—Forces changes to all system componentsduring activation.
Other New Commands
Other WLST commands that were added in this release of WebLogic Server are:
• setShowLSResult—Specifies whether the ls() command should log its output tostandard output.
• scaleUp—Increases the number of running dynamic servers in the specifieddynamic cluster.
Chapter 2Manageability Improvements
2-36
• scaleDown—Decreases the number of running dynamic servers in the specifieddynamic cluster.
Modifications to Existing Commands
The following modifications were made to existing WLST commands in this release ofWebLogic Server.
• The format argument has been added to the exportDiagnosticData andexportDiagnosticDataFromServer commands. Use this argument to specify theformat in which data is exported.
• The last argument has been added to the exportDiagnosticData,exportDiagnosticDataFromServer, exportHarvestedTimeSeriesData, andexportHarvestedTimeSeriesDataOffline commands. This argument is atimestamp range specification for the last n seconds.
• The Server argument has been added to the getAvailableCapturedImagescommand. Use this argument to specify the server from which to obtain a listof available images.
• The waitForAllSessions argument has been added to the shutdown command.Use this argument to specify whether WLST should wait for all HTTP sessions tocomplete while shutting down.
• The following arguments were added to the startNodeManager command:
– block—Specifies whether WLST should block until it successfully connects toNode Manager or fails to connect within the specified timeout.
– nmConnectOptions—When block is true, use this argument to specify a list ofNode Manager connection options.
– timeout—The number of milliseconds to wait for Node Manager to connect.
idd Variable and Argument
The idd variable has been added to WLST. This WLST variable is the Identity Domainof the user who is currently connected to WLST.
In addition, the idd argument has been added to the connect command to specify theIdentity Domain of the user who is connecting.
Resource Consumption Management
Note:
Resource Consumption Management is deprecated in WebLogic Server12.2.1.4.0 and will be removed in the next release.
Resource Consumption Management allows WebLogic system administrators tospecify resource consumption management policies (such as constraints, recourseactions, and notifications) on JDK-managed resources such as CPU, Heap, File,
Chapter 2Manageability Improvements
2-37
and Network. See Configuring Resource Consumption Management in Using OracleWebLogic Server Multitenant.
A configurable, partition auto-restart trigger action has been added that restarts thepartition on the server instance on which the partition's resource consumption quotashave been breached. See Triggers in Using Oracle WebLogic Server Multitenant.
SNMPv3 Default ProtocolBy default, Simple Network Management Protocol (SNMP) is disabled in WebLogicServer. In WebLogic Server 12.2.1.4.0 and later, when you enable SNMP, the SNMPv3protocol is enabled by default. The use of SNMPv1 and v2 protocols is deprecated inthis release of WebLogic Server.
Because SNMPv1 and SNMPv2 use clear text passwords, they are not secure andcan cause certain potential security problems to occur on the SNMP service, includingunauthorized access and Denial of Service attacks. Oracle strongly recommendsusing the SNMPv3 protocol instead. If configuration attributes enable the use of theSNMPv1 and v2 protocols, WebLogic Server logs a deprecated warning at startup.
See Security for SNMP in Monitoring Oracle WebLogic Server with SNMP.
Continuous AvailabilityOracle WebLogic Server Continuous Availability provides an integrated solution forbuilding maximum availability architectures (MAA) that span data centers acrossdistributed geographical locations. Integrated components include Oracle WebLogicServer, Oracle Coherence, Oracle Traffic Director, Oracle SiteGuard, and OracleDatabase. The major benefits of this integrated solution are faster failover orswitchover, increased overall application availability, data integrity, reduced humanerror and risk, recovery of work, and local access of real-time data.
Note:
Automated cross-site XA transaction recovery and WebLogic ServerMultitenant domain partitions and resource groups are deprecated inWebLogic Server 12.2.1.4.0 and will be removed in the next release.
The key features in Continuous Availability include:
• Automated cross-site XA transaction recovery— Provides automatic recoveryof XA transactions across an entire domain, or across an entire site with serversrunning in a different domain or at a different site.
• Zero Downtime Patching—Provides an automated mechanism to orchestrate therollout of patches while avoiding downtime or loss of sessions.
• WebLogic Server Multitenant live resource group migration— Provides theability to migrate partition resource groups that are running from one cluster/serverto another within a domain without impacting the application users.
• Coherence federated caching—Replicates cache data asynchronously acrossmultiple geographically distributed clusters.
Chapter 2Continuous Availability
2-38
• Coherence GoldenGate HotCache—Detects and reflects database changes incache in real time.
• Oracle Traffic Director—Routes HTTP, HTTPS, and TCP traffic to applicationservers and web servers on the network.
• Oracle Site Guard—Enables administrators to automate complete site switchoveror failover.
For more information about the features in Continuous Availability and the supportedMAA architectures, see What is Continuous Availability? in Continuous Availability forOracle WebLogic Server.
Documentation Update HistoryThe update history of the Oracle WebLogic Server documentation library summarizesthe updates that have been made to various user and reference guides, as well asonline help, since the initial release of version 12c (12.2.1).
The following table summarizes updates made to the Oracle WebLogic Serverdocumentation library since its initial 12.2.1.0.0 release:
Date Description of Updates
June 21, 2016 Patch Set 1 (12.2.1.1.0) is generally available.
October 19, 2016 Patch Set 2 (12.2.1.2.0) is generally available.
January 30, 2017 • Due to the removal of the wlx startup option, as explained in StartupOption for Lighter-Weight Runtime, the following topics have beenremoved from the WebLogic Server 12.2.1 documentation:
– Using the weblogic.Server Command Line to Limit the WebLogicServer Run-Time Footprint, in Command Reference for OracleWebLogic Server
– Limiting Run-Time Footprint When Starting WebLogic Server, inAdministering Server Startup and Shutdown for Oracle WebLogicServer
• In Deploying Applications to Oracle WebLogic Server, the sectionEnabling Parallel Deployment for Applications and Modules wasupdated to clarify the circumstances in which parallel deployment iseither enabled or disabled.
The section Parallel Deployment has been added to Upgrading OracleWebLogic Server to explain this behavior.
• In Developing Web Applications, Servlets, and JSPs for OracleWebLogic Server, the information about the <session-descriptor>element of the weblogic.xml deployment descriptor hasbeen updated to describe the new <auth-cookie-id-length>subelement, which defines the length of the secure cookie,_WL_AUTHCOOKIE_JSESSIONID.
Chapter 2Documentation Update History
2-39
Date Description of Updates
August 23, 2017 Patch Set 3 (12.2.1.3.0) is generally available. Library changes include:
• To support secured production domain mode, the following topics havebeen added or updated:
– Install and Configure WebLogic Server in a Secure Manner andEnsuring the Security of Your Production Environment in Securinga Production Environment for Oracle WebLogic Server have beenupdated.
– Configuring Security for a WebLogic Domain in AdministeringSecurity for Oracle WebLogic Server has been updated.
– Development and Production Modes in Understanding DomainConfiguration for Oracle WebLogic Server has been updated.
– Secure your production domain has been added to theAdministration Console Online Help.
– How Domain Mode Affects the Default Security Configuration inSecuring a Production Environment for Oracle WebLogic Serverhas been added.
– Java Naming and Directory Interface (JNDI) Resources and JMXResources in Securing Resources Using Roles and Policies forOracle WebLogic Server have been updated.
• In Administering Security for Oracle WebLogic Server, the sectionConfiguring the Oracle Identity Cloud Integrator Provider was addedto describe how to configure the new authentication and identityassertion provider that accesses users, groups, and Oracle IdentityCloud Service scopes and application roles stored in the OracleIdentity Cloud Service.
• Oracle WebLogic JMS provides a topic subscription message limitoption as a way to help prevent individual overloaded subscriptionsfrom using up all available resources. In Tuning Performance of OracleWebLogic Server, a new section Subscription Message Limits hasbeen added.
• In Administering the WebLogic Persistent Store, a new section ServiceRestart In Place has been added to provide information aboutautomatic recovery of a failed store and its dependent services on theiroriginal running WebLogic Server.
• In Oracle WebLogic Server 12.2.1.3.0, ZDT Patching is enhanced toprovide support for custom hooks. See Modifying Workflows UsingCustom Hooks in Administering Zero Downtime Patching Workflows.
• The following topics have been added to Administering JDBC DataSources for Oracle WebLogic Server:
– Using Shared Pooling Data Sources describes the ability formultiple data source definitions to share an underlying connectionpool.
– WebLogic JDBC Features for Oracle Database 12.2 describesdata source integration with several new Database 12.2 features.
– Initial Capacity Enhancement in the Connection Pool describesconnection retry, early failure, and critical data sources, which arenew features in WebLogic Server 12.2.1.3 for enhancing the initialcapacity connections in the connection pool.
– Oracle Sharding Support describes Oracle sharding, which isavailable in 12.2 UCP and surfaced from WebLogic Server throughthe native UCP data source.
• The topic Using Transaction Guard has been added to Developing JTAApplications for Oracle WebLogic Server.
• The topic Temporary Configuration Overriding has been added toUnderstanding Domain Configuration for Oracle WebLogic Server.
Chapter 2Documentation Update History
2-40
Date Description of Updates
• Considerations and recommendations regarding the use of multiplebatch runtime instances in a domain, in both clustered andnonclustered environments, have been added to the following topics:
– Use of Multiple Batch Runtime Instances in Administering ServerEnvironments for Oracle WebLogic Server
– Batch Applications in Administering Clusters for Oracle WebLogicServer
• In Developing JMS Applications, the topic Replacing a ReplicatedDistributed Topic was added.
• In Configuring and Using the WebLogic Diagnostic Framework, thetopic Configuring Collected Metrics Based Policies was expanded toexplain how to write collected metrics-based policy expressions usingthe Java Expression Language (EL).
• The following additional changes were made to Administering Securityfor Oracle WebLogic Server:– The topic Using Automatic Realm Restart was added.– Appendix Using Certificate Chains was removed.
• Developing and Administering Spring Applications for Oracle WebLogicServer has been removed from the documentation library.
October 6, 2017 The topic Obtaining a List of Applied Patches was added to UpgradingOracle WebLogic Server.
April 17, 2018 • Added the following notices to Deprecated Functionality (OracleWebLogic Server 12c 12.2.1.x):
– DynamicServersMBean.MaximumDynamicServerCount Attribute– Compatibility Setting for JTA Security Interoperability Mode
• Updated the following topics to clarify the use of and distinctionbetween the DynamicClusterSize and MaxDynamicClusterSizeattributes of the DynamicServersMBean:
– Configuring Dynamic Clusters in Configuring Elasticity in DynamicClusters for Oracle WebLogic Server
– Expanding or Reducing Dynamic Clusters in AdministeringClusters for Oracle WebLogic Server
– Dynamic Server Properties in Administering Oracle WebLogicServer with Fusion Middleware Control
– Best Practices for Using Clustered JMS Services in AdministeringJMS Resources for Oracle WebLogic Server.
• Updated the following topics with a new note for scaleDown command:
– Limitations and Considerations When Using Dynamic Clusters
in Administering Clusters for Oracle WebLogic Server.– scaleDown in WLST Command Reference for WebLogic Server.
• Updated new REST endpoints in the following topics of AdministeringOracle WebLogic Server with RESTful Management Services:
– Viewing WLS Beans– Search Resources– Object Queries
• Updated the description of -dweblogic.management.startupMode=MODE in Other ServerConfiguration Options of Command Reference for Oracle WebLogicServer.
• Added a new note related to setUserOverrides parameter inCustomizing Domain Wide Server Parameters of Administering ServerStartup and Shutdown for Oracle WebLogic Server.
Chapter 2Documentation Update History
2-41
Date Description of Updates
August 31, 2018 Added the topic Configuring a Custom JEP 290 Deserialization Filter toAdministering Security for Oracle WebLogic Server
Chapter 2Documentation Update History
2-42
Date Description of Updates
September 27,2019
Patch Set 4 (12.2.1.4.0) is generally available. Library changes include:• The topic Configuration Overriding has replaced Temporary
Configuration Overriding in Understanding Domain Configuration forOracle WebLogic Server.
• The topic Using JMS 2.0 Asynchronous Message Sends has beenadded to Tuning Performance of Oracle WebLogic Server.
• Updated the following topics in Administering Security for OracleWebLogic Server:
– Configuring a Custom JEP 290 Deserialization Filter to describethe weblogic.oif.serialFilterLogging system property andthe scope of the default filter change to global.
– Configure SAML 2.0 Service Provider Services and ConfigureSAML 2.0 Identity Provider Services to describe the support forsigning and encrypting SAML assertions for SAML 2.0.
• Added the following new topics in Administering Security for OracleWebLogic Server:
– Configuring SAML Encryption Using WLST that describes how toconfigure encryption for SAML 2.0 assertions.
– Specify Allowed Target Hosts to describe the new attribute,AllowedTargetHosts on the FederationServicesMBean andSingleSignOnServicesMBean.
– Handling Authentication Failures to describe the twonew attributes, ServerNotAvailableCounterInterval andServerBackoffEnabled, that you can use to controlauthentication failures from the Oracle Identity Cloud Service.
• Updated the following topics to describe the deprecation of SNMPv1and v2 protocols, and the change to SNMPv3 as the default behavior:
– Security for SNMP in Monitoring Oracle WebLogic Server withSNMP
– Securing Network Connections in Securing a ProductionEnvironment for Oracle WebLogic Server
• Updated the topic ValidateCertChain in Command Reference forOracle WebLogic Server to indicate that the file-based certificate chainoptions are deprecated.
• Updated the following topics in Tuning Performance of OracleWebLogic Server:
– Renamed the topic Compressing Messages to ThresholdCompression for Remote Messages.
– Added a new topic Store Compression that describes theWebLogic Server ability to configure message compression forJMS Store I/O operations.
• Updated the chapter Ensuring the Security of Your ProductionEnvironment in Securing a Production Environment for OracleWebLogic Server to include the following security recommendationsfor reducing the attack surface on WebLogic Server development andproduction environments:– Using network channels and connection filters to isolate incoming
and outgoing application traffic– Limiting protocol for external channels– Running different protocols on different ports– Disabling tunneling on channels that are available external to the
firewall– Preventing unauthorized access to your WebLogic Server
resources such as JDBC, JMS or EJB resources.
Chapter 2Documentation Update History
2-43
Date Description of Updates
April, 2020 Added new guide Running Oracle WebLogic Server and Coherence onGraalVM Enterprise Edition.
May, 2020 Added a new topic, Default Users, to Securing Resources Using Roles andPolicies for Oracle WebLogic Server.
Standards Support, Supported Configurations, andWebLogic Server Compatibility
Oracle WebLogic Server 12c (12.2.1) provides Java EE 7 full platform support, JavaSE 8 certification, support for web services standards, support on multiple operatingsystem and JVM platforms, and support for several security standards such as X.509v3 and SSL v3.
The following sections describe WebLogic Server standards support, supportedsystem configuration, and WebLogic Server compatibility:
• Standards Support
• Supported Configurations
• Licensing Information
• WebLogic Server Compatibility
• Database Interoperability
Standards SupportWebLogic Server 12c (12.2.1) supports the following standards and versions:
• Java Standards
• Web Services Standards
• Other Standards
Java StandardsTable 2-1 lists currently supported Java standards.
Note:
See WebLogic Server Security Standards in Administering Security forOracle WebLogic Server for the currently supported security standards, suchas JAAS, JASPIC, JACC, JCE, and so forth.
Chapter 2Standards Support, Supported Configurations, and WebLogic Server Compatibility
2-44
Table 2-1 Java Standards Support
Standard Version
Batch Application Processing (JSR 352) 1.0
Contexts and Dependency Injection for Java EE 1.1
Dependency Injection for Java EE 1.0
Concurrent Managed Objects (JSR 236) 1.0
Expression Language (EL) 3.0, 2.2, 2.1, 2.0
Only JSP 2.0 and greater supports ExpressionLanguage 2.x.
Java API for JSON Processing (JSR-353) 1.0
Java API for XML-Based Web Services (JAX-WS) 2.2, 2.1, 2.0
Java API for RESTful Web Services (JAX-RS) 2.0
Java API for WebSocket 1.1
JavaBeans Activation Framework 1.1
Java EE 7.0
Java EE Application Deployment 1.2
Java EE Bean Validation 1.1
Java EE Common Annotations 1.2
Java EE Connector Architecture 1.7
Java EE EJB 3.2, 3.1, 3.0, 2.1, 2.0, and 1.1
Java EE Enterprise Web Services 1.3, 1.2, 1.1
Java EE Interceptors 1.2
Java EE JDBC 4.0, 3.0
Java EE JMS 2.0, 1.1, 1.0.2b
Java EE JNDI 1.2
Java EE JSF 2.2, 2.1.*, 2.0, 1.2, 1.1
Java EE JSP 2.3, 2.2, 2.1, 2.0, 1.2, and 1.1
JSP 1.2. and 1.1 include Expression Language (EL), butdo not support EL 2.x or greater.
Java EE Managed Beans 1.0
Java EE Servlet 3.1, 3.0, 2.5, 2.4, 2.3, and 2.2
Java RMI 1.0
JavaMail 1.5
Java Transaction API 1.2
JAX-B 2.2, 2.1, 2.0
JAX-P 1.3, 1.2, 1.1
JAX-R 1.0
JAX-RPC 1.1
JDKs 8.0 (8.0 and 7.0 for clients)
See JDK 8 and Server JRE 8 Certification for details.
Chapter 2Standards Support, Supported Configurations, and WebLogic Server Compatibility
2-45
Table 2-1 (Cont.) Java Standards Support
Standard Version
JMX 1.4
JPA 2.1, 2.0., 1.0
JSR 77: Java EE Management 1.1
JSTL 1.2
Managed Beans 1.0
OTS/JTA OTS 1.2 and JTA 1.2
RMI/IIOP 1.0
SOAP Attachments for Java (SAAJ) 1.3, 1.2
Streaming API for XML (StAX) 1.0
Web Services Metadata for the Java Platform 2.0, 1.1
Web Services StandardsFor the current list of standards supported for WebLogic web services, see Featuresand Standards Supported by WebLogic Web Services in Understanding WebLogicWeb Services for Oracle WebLogic Server.
Other StandardsTable 2-2 lists other standards that are supported in WebLogic Server 12c (12.2.1).
Note:
See WebLogic Server Security Standards in Administering Security forOracle WebLogic Server for additional information on standards relating tosecurity, such as SSL, TLS, and XACML, and so forth.
Table 2-2 Other Standards
Standard Version
X.509 v3
LDAP v3
TLS v1.1, v1.2
HTTP 1.1
SNMP SNMPv1, SNMPv2, SNMPv3
xTensible Access Control Markup Language(XACML)
2.0
Partial implementation of Core and HierarchicalRole Based Access Control (RABC) Profile ofXACML
2.0
Chapter 2Standards Support, Supported Configurations, and WebLogic Server Compatibility
2-46
Table 2-2 (Cont.) Other Standards
Standard Version
Internet Protocol (IP) Versions:
• v6• v4
For more information about IPv6 support for all Fusion Middleware products, seethe Oracle Fusion Middleware Supported System Configurations page on OracleTechnology Network.
Supported ConfigurationsFor the most current information on supported configurations, see the Oracle FusionMiddleware Supported System Configurations page on Oracle Technology Network.
Please note the following restrictions and advice when running Oracle WebLogicServer 12c (12.2.1), and Oracle WebLogic Server 12c (12.2.1) applications, on JavaSE 8:
• Oracle WebLogic Server 12c (12.2.1) does not support applications using thenew Java SE 8 fork/join and parallel streams features. Avoid these features whenbuilding Oracle WebLogic Server 12c (12.2.1) applications using Java SE 8. Thereason for this restriction is that the threads used by the fork/join thread poolwill not be WebLogic Server managed threads. Any of the work performed inthese threads may not be able to make use of WebLogic Server or Java EEfacilities because the state of these threads, including security and transactionstate, may not be created properly. Further, these threads will not be controlled byWebLogic Server Work Manager thread management facilities, possibly resultingin excessive thread usage.
• Check all third party vendor software you are using for Java SE 8 compatibility.It may be necessary to upgrade to a later version of the software that correctlyhandles Java SE 8 classes, and some software may not yet be compatible.For example, the current version of the open source tool "jarjar" does not workcorrectly with Java SE 8 yet.
• Java SE 8 has new APIs for JDBC 4.2 that are supported for versions ofWebLogic Server 12.1.3 and later that are running on Java SE 8 with a JDBCdriver that supports JDBC 4.2. However, although the Oracle JDBC thin driverbundled with WebLogic Server is certified on Java SE 8, the Oracle JDBC thindriver does not support JDBC 4.2. The Derby 10.10 driver that is shipped withOracle WebLogic Server as of release 12c (12.2.1) has been tested with JDBC4.2 and may be used. The corresponding Derby documentation is available athttp://db.apache.org/derby/docs/10.10/ref/rrefjdbc4_2summary.html.
• When running using SSL connections with JCE on JDK 8, it may be necessaryto install the Java Cryptography Extension (JCE) Unlimited Strength JurisdictionPolicy Files 8. You can download the JCE Unlimited Strength JurisdictionPolicy Files for JDK 8 at http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html.
Chapter 2Standards Support, Supported Configurations, and WebLogic Server Compatibility
2-47
Licensing InformationFor the most current information on Oracle Fusion Middleware Licensing, seeLicensing Information User Manual.
WebLogic Server CompatibilityFor the most current information on compatibility between the current version ofWebLogic Server and previous releases, see WebLogic Server Compatibility inUnderstanding Oracle WebLogic Server.
Database InteroperabilityThe certification matrices and My Oracle Support Certifications define the followingterms to differentiate between types of database support:
• Application Data Access
• Database Dependent Features
Application Data AccessApplication Data Access refers to those applications that use the database fordata access only and do not take advantage of WebLogic Server features that areDatabase dependant. WebLogic Server support of databases used for application dataaccess only are less restrictive than for database dependent features.
WebLogic Server provides support for application data access to databases usingJDBC drivers that meet the following requirements:
• The driver must be thread safe.
• The driver must implement standard JDBC transactional calls, such assetAutoCommit() and setTransactionIsolation(), when used in transactionalaware environments.
Note the following restrictions:
• JDBC drivers that do not implement serializable or remote interfaces cannot passobjects to an RMI client application.
• Simultaneous use of automatic database connection failover and load balancingand global transactions (XA) with a highly-available (HA) DBMS architecture issupported with Oracle DB RAC only, and only for the Oracle DB RAC versionsindicated on the System worksheet. These HA capabilities are only supported byActive GridLink for RAC and Multi Data Sources with RAC. These HA capabilitiesare not supported on other Oracle DB RAC versions or with other HA DBMStechnologies on other non-Oracle DB products. Multi Data Sources are supportedon other Oracle DB versions, and with non-Oracle DB technologies, but not withsimultaneous use of automatic failover and load balancing and global transactions.
• Application data access to databases meeting the restrictions articulated above issupported on other Oracle DB versions, in addition to those documented in thecertification matrix.
Chapter 2Standards Support, Supported Configurations, and WebLogic Server Compatibility
2-48
• WebLogic Type 4 JDBC drivers also support the following databases. For thesedatabases, WebLogic Server supports application data access only, and does notsupport WebLogic Server database dependent features:
– DB2 for z/OS 10.1
– Informix 11.7+
Database Dependent FeaturesWhen WebLogic Server features use a database for internal data storage, databasesupport is more restrictive than for application data access. The following WebLogicServer features require internal data storage:
• Container Managed Persistence (CMP)
• Rowsets
• JMS/JDBC Persistence and use of a WebLogic JDBC Store
• JDBC Session Persistence
• RDBMS Security Providers
• Database Leasing (for singleton services and server migration)
• JTA Logging Last Resource optimization
• JDBC TLog
Deprecated Functionality (Oracle WebLogic Server 12c12.2.1.x)
Complete details about deprecated functionality for WebLogic Server, includingfor previous releases, can be found on My Oracle Support at https://support.oracle.com/. Search for "Deprecated Features" in the Search KnowledgeBase field.
The following functionality and components are deprecated in WebLogic Server 12c(12.2.1.x):
• WebLogic jCOM
• Oracle Traffic Director (OTD)
• Deprecated WebLogic Server Multitenant Functionality and ResourceConsumption Management
• Automated Cross-Site XA Transaction Recovery Deprecated
• Simple Network Management Protocol (SNMP) v1 and v2
• ValidateCertChain Java Utility File-based Certificate Chains
• SecurityConfigurationMBean.AnonymousAdminLookupEnabled Attribute
• ServerTemplateMBean.DefaultTGIOPUser Attribute
• WebLogic Full and Standard Clients
• Log4j
• LogMBean.ServerLoggingBridgeUserParentLoggersEnabled Attribute
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-49
• User Name and Password System Properties
• Maven 11x Plug-In Deprecated
• JSP Tags for XML Processing
• Deprecated Functionality in WLST
• Deprecated RESTful Management Features
• WebLogic Server/Spring Integration Features
• Deprecated Diagnostics Exceptions
• RESTful Web Services
• CacheFilter API
• JAX-RPC WebService-ReliableMessaging
• SSLMBean.ExportKeyLifespan Attribute
• setSSLClientCertificate and setSSLClientKeyPassword Methods
• EJBGen
• WebLogic Replicated Store
• JMS Interop Modules
• WebLogic JMS Resource Adapter
• JMS Reconnect
• JMS Deployable Configuration
• JMS Weighted Distributed Destinations
• DynamicServersMBean.MaximumDynamicServerCount Attribute
• Compatibility Setting for JTA Security Interoperability Mode
WebLogic jCOMWebLogic jCOM is deprecated as of WebLogic Server 12.2.1.4.0.
jCOM has been provided as a migration path for interim solutions that require Java-to-COM integration. Oracle believes that web services and REST are the preferredway to communicate with Microsoft applications. Oracle recommends that you migratelegacy COM applications to .NET in order to use this type of communication.
Oracle Traffic Director (OTD)As of 12.2.1.4.0, Oracle Traffic Director is deprecated.
In the future, for equivalent functionality, use Oracle HTTP Server, Microsoft IIS WebServer, or Apache HTTP Server plug-ins, or a native Kubernetes load balancer, suchas Traefik.
Deprecated WebLogic Server Multitenant Functionality and ResourceConsumption Management
WebLogic Server Multitenant domain partitions, resource groups, resource grouptemplates, virtual targets, resource override configuration MBeans, Resource
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-50
Consumption Management, and proxy data sources are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.
WebLogic Server Multitenant domain partitions enable the configuration of a portionof a WebLogic domain that is dedicated to running application instances and relatedresources. Oracle recommends that customers using domain partitions as a containerdedicated to specific applications and resources consider the use of alternativecontainer-based architectures, including the deployment of WebLogic applications andservices in Docker containers running in Kubernetes clusters. For more information,see Running Oracle WebLogic Server on Docker and WebLogic Server KubernetesOperator.
Automated Cross-Site XA Transaction Recovery Deprecated
Active-Active XA Transaction Recovery (automated cross-site XA transactionrecovery) is deprecated in WebLogic Server 12.2.1.4.0 and will be removed inthe next release. For more information on XA transaction recovery solutions, seeUnderstanding XA Transaction Recovery in Disaster Recovery.
Simple Network Management Protocol (SNMP) v1 and v2The following configuration attributes are deprecated as of Oracle WebLogic Server12.2.1.4.0:
• CommunityPrefix in SNMPAgentMBean
• CommunityBasedAccessEnabled in SNMPAgentMBean
• Community in SNMPTrapDestinationMBean
ValidateCertChain Java Utility File-based Certificate Chains
The following file-based options of the ValidateCertChain utility are deprecated as ofOracle WebLogic Server 12.2.1.4.0:
• java utils.ValidateCertChain -file pemcertificatefilename
• java utils.ValidateCertChain -pem pemcertificatefilename
• java utils.ValidateCertChain -pkcs12file pkcs12filename password
Oracle recommends that you use the -pkcs12store or the -jks keystore optionsinstead.
SecurityConfigurationMBean.AnonymousAdminLookupEnabledAttribute
The AnonymousAdminLookupEnabled attribute on the SecurityConfigurationMBean isdeprecated as of Oracle WebLogic Server 12.2.1.
ServerTemplateMBean.DefaultTGIOPUser AttributeThe DefaultTGIOPUser attribute on the ServerTemplateMBean is deprecated as ofOracle WebLogic Server 12.2.1.3.0.
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-51
WebLogic Full and Standard ClientsThe following WebLogic clients are deprecated:
• The WebLogic full client, wlfullclient.jar, is deprecated as of Oracle WebLogicServer 12.1.3. Oracle recommends using T3 client or Install client instead ofWebLogic full client.
• The WebLogic Server-IIOP client is deprecated as of WebLogic Server 12.1.3because of its dependency on the wlfullclient.jar and it will be removed in afuture release. Oracle recommends using T3 clients instead of IIOP clients.
• The standard client, wlclient.jar, and the following clients that depend on it, aredeprecated as of Oracle WebLogic Server 12.2.1.2.0:
– The JMS client, wljmsclient.jar
– The JMS SAF client, wlsafclient.jar
See Clients and Features in Developing Standalone Clients for Oracle WebLogicServer.
Log4jThe use of Log4j with the WebLogic logging service, as an alternative to Java logging,is deprecated as of WebLogic Server 12.1.3. Note that Log4j 2 and later is notsupported in WebLogic Server.
LogMBean.ServerLoggingBridgeUserParentLoggersEnabled AttributeThe ServerLoggingBridgeUserParentLoggersEnabled attribute on the LogMBean isdeprecated as of WebLogic Server 12.1.3.
User Name and Password System PropertiesAs of WebLogic Server 12.1.1, the boot user name and password system propertiesweblogic.management.username and weblogic.management.password have beendeprecated and will be removed in a future release, and you will no longer be ableto specify the user name and password in the command for starting WebLogic Serverin production mode.
As an alternative, Oracle recommends that you use the boot.properties file tospecify the boot user name and password for WebLogic Server. For more informationabout the boot.properties file, see Boot Identity Files in Administering Server Startupand Shutdown for Oracle WebLogic Server.
For information about other methods you can use to provide user credentials, seeProvide User Credentials to Start and Stop Servers in Administering Server Startupand Shutdown for Oracle WebLogic Server.
Maven 11x Plug-In DeprecatedThe weblogic-maven-plugin plug-in delivered in WebLogic Server 11g Release 1is deprecated as of release 12.1.2. Oracle recommends that you instead use theWebLogic Server Maven plug-in introduced in version 12.1.2. See Using the WebLogic
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-52
Development Maven Plug-in in Developing Applications for Oracle WebLogic Serverfor complete documentation.
JSP Tags for XML ProcessingAs of WebLogic Server 12.1.2, XSLT JSP tags and the WebLogic XSLT JSP TagLibrary have been deprecated and will be removed in a future release. You canuse JAXP to transform XML data. For more information, see Transforming XMLDocuments in Developing XML Applications for Oracle WebLogic Server.
Deprecated Functionality in WLST
The following functionality in WLST has been deprecated as of WebLogic Server12.2.1.
Server Argument to WLST Diagnostics CommandsThe Server argument to the following WLST diagnostics commands has beendeprecated:
• captureAndSaveDiagnosticImage
• createSystemResourceControl
• destroySystemResourceControl
• disableSystemResource
• enableSystemResource
• listSystemResourceControls
The Server argument is being replaced by the Target argument. For moreinformation, see Diagnostics Commands in WLST Command Reference for WebLogicServer.
The addTemplate and readTemplate Control Commands
The addTemplate and readTemplate commands have been deprecated as ofWebLogic Server 12.2.1 and will be removed in a future release. Use theselectTemplate and loadTemplates commands instead. For more information andexamples, see Creating and Updating a WebLogic Domain in Understanding theWebLogic Scripting Tool.
Implicit Importing of Modules Using WLST
Support for using WLST to implicitly import modules into an application has beendeprecated. When using WLST to import modules, Oracle recommends doing theoperation explicitly.
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-53
The following WLST snippet shows an explicit import of the module EJBResource fromweblogic.security.service:
@ from weblogic.security.service import EJBResourceejbRes = EJBResource('DDPoliciesEar', 'DDPolinEarMiniAppBean.jar', 'DDRolesAndPolicies', 'getSubject', 'Remote', None)
The configToScript Command
The configToScript command is deprecated in Oracle WebLogic Server 12.2.1.To replicate a server configuration, Oracle recommends that you use the pack andunpack commands. See Creating Templates and Domains Using the Pack and UnpackCommands.
Deprecated RESTful Management FeaturesThe following RESTful management features are deprecated in this release of OracleWebLogic Server.
RESTful Management Resources for Oracle WebLogic Server MultitenantThe following RESTful management resources for Oracle WebLogic ServerMultitenant are deprecated in version 12.2.1.4.0 and will be removed in the nextrelease:
• /management/weblogic/latest/edit/partitions/
• /management/weblogic/latest/domainConfig/partitions/
• /management/weblogic/latest/domainRuntime/domainPartitionRuntimes/
• /management/weblogic/latest/serverConfig/partitions/
• /management/weblogic/latest/serverRuntime/partitionRuntimes/
Oracle recommends that customers using domain partitions as a container dedicatedto specific applications and resources consider the use of alternative container-basedarchitectures, including the deployment of WebLogic applications and services inDocker containers running in Kubernetes clusters.
RESTful Life Cycle Management Resources
The following RESTful Life Cycle Management (LCM) resources are deprecated inOracle WebLogic Server as of version 12.2.1.3.0 and will be removed in a futurerelease:
• /lifecycle/{version}/runtimes/{runtime-name}/scaleUp
• /lifecycle/{version}/runtimes/{runtime-name}/scaleDown
• /lifecycle/{version}/runtimes/{runtime-name}/quiesce
• /lifecycle/{version}/runtimes/{runtime-name}/start
• /lifecycle/{version}/runtimes/{runtime-name}/sync
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-54
Oracle recommends that you migrate immediately to the corresponding /management/weblogic RESTful resources, which continue to be supported and enhanced. SeeAdministering Oracle WebLogic Server with RESTful Management Services.
RESTful Resources for Monitoring and Management
The following RESTful management resources are deprecated in Oracle WebLogicServer as of version 12.2.1.3.0 and will be removed in a future release:
• /management/tenant-monitoring, introduced in Oracle WebLogic Server 10.3.6
• /management/wls, introduced in Oracle WebLogic Server 12.1.3
In Oracle WebLogic Server 12.2.1.4.0, /management/weblogic resource versions12.2.1.0.0, 12.2.1.1.0, 12.2.1.2.0 and 12.2.1.3.0 are now deprecated. The latestversion is 12.2.1.4.0. For future releases, latest always refers to the most recentrelease.
Oracle recommends that you migrate immediately to the newer /management/weblogic RESTful resources. See Administering Oracle WebLogic Server withRESTful Management Services.
URL Format for REST ManagementThe URL format for REST management APIs has changed in 12.1.3. The URL formatintroduced in 12.1.2 will continue to work, but is deprecated as of Oracle WebLogicServer 12.1.3.
WebLogic Server/Spring Integration Features
Integration features for WebLogic Server/Spring are deprecated in Oracle WebLogicServer as of version 12.2.1. Also, as of version 12.2.1, the Oracle WebLogic ServerSpring console extension is not supported when using JRF or restricted-JRF.
Deprecated Diagnostics Exceptions
The following exceptions in the Harvester component of the WebLogic DiagnosticsFramework are deprecated:
weblogic.diagnostics.harvester.HarvesterExceptionweblogic.diagnostics.harvester.HarvesterException.AmbiguousInstanceNameweblogic.diagnostics.harvester.HarvesterException.AmbiguousTypeNameweblogic.diagnostics.harvester.HarvesterException.HarvestableInstancesNotFoundExceptionweblogic.diagnostics.harvester.HarvesterException.HarvestableTypesNotFoundExceptionweblogic.diagnostics.harvester.HarvesterException.HarvestingNotEnabledweblogic.diagnostics.harvester.HarvesterException.MissingConfigurationTypeweblogic.diagnostics.harvester.HarvesterException.TypeNotHarvestable
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-55
RESTful Web Services
The following JAX-RS functionality has been deprecated as of Oracle WebLogicServer 12.2.1.
Jersey 1.18 (JAX-RS 1.1 RI) Client APIs
Support for the Jersey 1.18 (JAX-RS 1.1RI) client APIs, including the com.sun.jerseyand its nested packages, and the weblogic.jaxrs.api.client packages, aredeprecated in this release of WebLogic Server but are maintained for backwardcompatibility. It is recommended that you update your RESTful client applications touse the JAX-RS 2.0 RI client APIs at your earliest convenience. For more information,see Introduction to RESTful Web Services in Developing and Securing RESTful WebServices for Oracle WebLogic Server.
Runtime Monitoring MBeans
The following runtime MBeans have been deprecated:
• JaxRsMonitoringInfoRuntimeMBean
• JaxRsResourceConfigTypeRuntimeMBean
Note:
The functionality provided by these MBeans has been replaced by newor updated MBeans. For more information, see Monitoring RESTful WebServices and Clients in Developing and Securing RESTful Web Services forOracle WebLogic Server.
CacheFilter API
The WebLogic Server API weblogic.cache.filter.CacheFilter has beendeprecated as of Oracle WebLogic Server 12.2.1.
JAX-RPC WebService-ReliableMessagingWebLogic SAF Agent support for JAX-RPC Reliable Messaging is deprecated, alongwith the complete JAX-RPC API. Consequently, the SAF Agent Service Type attributewill be ignored and all SAF Agents will be treated as Service Type Sending-onlyin a future release. Oracle recommends use of JAX-WS Reliable Messaging as areplacement for this technology.
SSLMBean.ExportKeyLifespan Attribute
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-56
The SSLMBean.ExportKeyLifespan attribute is deprecated as of WebLogic Server12.2.1. This attribute was used by the Certicom-based SSL implementation, which wasremoved from WebLogic Server in version 12.1.1 and replaced by JSSE. The JSSEimplementation in WebLogic Server does not use the SSLMBean.ExportKeyLifespanattribute. For more information about JSSE, see Using the JSSE-Based SSLImplementation in Administering Security for Oracle WebLogic Server.
setSSLClientCertificate and setSSLClientKeyPassword Methods
The setSSLClientCertificate() and setSSLClientKeyPassword() methods in theweblogic.jndi.Environment class have been deprecated in this release. UseloadLocalIdentity() or setSSLContext() instead. For more information, see Two-Way SSL Authentication with JNDI in Developing Applications with the WebLogicSecurity Service.
EJBGen
EJBGen, an Enterprise JavaBeans 2.x code generator utility, is deprecated as ofOracle WebLogic Server 12.2.1.3.0, and will be removed in a future release.
WebLogic Replicated Store
The WebLogic Replicated Store, a WebLogic JMS messages storage option that isintended only for use in Oracle Exalogic Elastic Cloud environments, is deprecated asof Oracle WebLogic Server version 12.2.1.3.0 and will be removed in a future release.
• DomainMBean.ReplicatedStores attribute
• weblogic.management.configuration.ReplicatedStoreMBean API
• The document Administering WebLogic Server for Oracle Exalogic Elastic Cloud
Oracle recommends that you use either a JDBC store or a custom file store for JMSmessage storage.
JMS Interop ModulesJMS Interop Modules are deprecated in WebLogic Server 12.1.1. If you have a modulenamed interop-jms.xml in your config.xml, convert it to a regular system module.See JMS System Module Configuration.
WebLogic JMS Resource Adapter
The WebLogic JMS resource adapter is deprecated as of Oracle WebLogicServer 12.2.1.3.0, and will be removed in a future release. Oracle recommends thatyou use either the thin T3 client or a message bridge to integrate applications runningon non-WebLogic application servers through JMS. See the following topics:
• Developing a WebLogic Thin T3 Client in Developing Standalone Clients forOracle WebLogic Server
• Understanding the Messaging Bridge in Administering the WebLogic MessagingBridge for Oracle WebLogic Server.
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-57
Note:
The WebLogic JMS resource adapter is supported only on Oracle GlassFishServer, so only users of GlassFish Server are affected.
JMS Reconnect
The WebLogic JMS automatic reconnect feature is deprecated. The JMSconnection factory configuration, javax.jms.extension.WLConnection API, andjavax.jms.extension.JMSContext API for this feature will be removed or ignoredin a future release. They do not handle all possible failures and so are not aneffective substitute for standard resiliency best practices. Oracle recommends thatclient applications handle connection exceptions as described in Client Resiliency BestPractices in Administering JMS Resources for Oracle WebLogic Server.
JMS Deployable ConfigurationWebLogic JMS Application Modules for Deployment are deprecated, includingpackaged and standalone modules. Support for JMS Application Modules will beremoved in a future release. Oracle recommends creating required JMS configurationusing system modules.
JMS Weighted Distributed DestinationsJMS Weighted Distributed Destinations were deprecated in WebLogic Server 10.3.4.0.Oracle recommends using Uniform Distributed Destinations.
DynamicServersMBean.MaximumDynamicServerCount Attribute
The DynamicServersMBean.MaximumDynamicServerCount attribute is deprecatedas of WebLogic Server 12.2.1. This attribute is replaced by theDynamicServersMBean.DynamicClusterSize attribute, which the Elasticity Frameworkuses in conjunction with the MinDynamicClusterSize and MaxDynamicClusterSizeattributes on the DynamicServersMBean to define the boundaries within which adynamic cluster may be scaled up or down.
The MaximumDynamicServerCount attribute is presently retained for backwardscompatibility, but will be removed in a future release. For more information about usingthe DynamicClusterSize attribute, see Configuring Dynamic Clusters in ConfiguringElasticity in Dynamic Clusters for Oracle WebLogic Server.
Compatibility Setting for JTA Security Interoperability Mode
The compatibility setting for JTA Security Interoperability Mode is deprecatedin this release of WebLogic Server and will be removed in a future release. Formore information about how to configure compatible communication channels betweenservers in global transactions with participants in the same or different domains, see
Chapter 2Deprecated Functionality (Oracle WebLogic Server 12c 12.2.1.x)
2-58
Security Interoperability Mode in Developing JTA Applications for Oracle WebLogicServer.
Removed Functionality and ComponentsSeveral components deprecated in previous versions of WebLogic Server areremoved from Oracle WebLogic Server 12c (12.2.1).
• Certificate Chains
• Compatibility Security
• 6.x Realms
• Certificate Request Generator Servlet
• weblogic.Admin
• JAXR
• Jersey 1.18 (JAX-RS 1.1. RI) Server APIs
• WebLogic Keystore Provider
• weblogic.security.provider.PrincipalValidatorImpl
• weblogic.xml.stream.util.XMLPullReaderBase
• Connect-Time Failover
• Compatibility MBean Server and Type-Safe MBean Interfaces
• Startup Option for Lighter-Weight Runtime
• Oracle WebLogic Server Proxy Plug-In for Oracle iPlanet Web Server
Certificate ChainsThe support for file-based certificate chains has been removed from Oracle WebLogicServer as of version 12.2.1.
Compatibility Security
As of release 12.2.1, WebLogic Server has removed support for Compatibility securityin both the server and client. In prior releases, Compatibility security is used forrunning security configurations developed with WebLogic Server 6.x. For informationabout interoperability with a version of WebLogic Server that uses Compatibilitysecurity, see Protocol Compatibility in Understanding Oracle WebLogic Server. Thefollowing components that provided Compatibility security in previous releases areremoved as of Oracle WebLogic Server 12.2.1:
• CompatibilityRealm
• CachingRealm
• LDAPRealm
• NTRealm
• FileRealm
• Custom security realm
Chapter 2Removed Functionality and Components
2-59
• RDBMS security realm
• Realm Adapter provider
• Realm Adapter Auditing provider
• Realm Adapter Authentication provider
• Realm Adapter Authorization provider
• Realm Adapter Adjudication provider
The following classes that provided support for Compatibility security were removed:
• weblogic.management.configuration.Acl
• weblogic.management.configuration.BasicRealmMBean
• weblogic.management.configuration.CachingRealmMBean
• weblogic.management.configuration.CustomRealmMBean
• weblogic.management.configuration.FileRealmMBean
• weblogic.management.configuration.Group
• weblogic.management.configuration.LDAPRealmMBean
• weblogic.management.configuration.ListResults
• weblogic.management.configuration.NTRealmMBean
• weblogic.management.configuration.PasswordPolicyMBean
• weblogic.management.configuration.Principal
• weblogic.management.configuration.RDBMSRealmMBean
• weblogic.management.configuration.RealmException
• weblogic.management.configuration.RealmIterator
• weblogic.management.configuration.RealmMBean
• weblogic.management.configuration.RealmManager
• weblogic.management.configuration.RemoteEnumeration
• weblogic.management.configuration.SecurityMBean
• weblogic.management.configuration.UnixRealmMBean
• weblogic.management.configuration.User
• weblogic.management.mbeans.custom.LDAPRealm
• weblogic.management.mbeans.custom.NTRealm
• weblogic.management.mbeans.custom.Realm
• weblogic.management.mbeans.custom.Security
• weblogic.management.mbeans.custom.UnixRealm
• weblogic.management.internal.BatchedEnumeration
• weblogic.management.internal.RemoteEnumerationImpl
• weblogic.management.internal.RemoteRealmException
• weblogic.management.internal.RemoteRealmManager
Chapter 2Removed Functionality and Components
2-60
• weblogic.management.internal.RemoteRealmManagerImpl
• weblogic.security.acl.AbstractListableRealm
• weblogic.security.acl.AbstractManageableRealm
• weblogic.security.acl.AclEntryImpl
• weblogic.security.acl.AclImpl
• weblogic.security.acl.AdminPermissions
• weblogic.security.acl.CachingRealm
• weblogic.security.acl.CertAuthentication
• weblogic.security.acl.CertAuthenticator
• weblogic.security.acl.ClosableEnumeration
• weblogic.security.acl.CredentialChanger
• weblogic.security.acl.DebuggableRealm
• weblogic.security.acl.DefaultGroupImpl
• weblogic.security.acl.DefaultUserImpl
• weblogic.security.acl.DynamicUserAcl
• weblogic.security.acl.Everyone
• weblogic.security.acl.ExplicitlyControlled
• weblogic.security.acl.FlatGroup
• weblogic.security.acl.GroupImpl
• weblogic.security.acl.InvalidLogin
• weblogic.security.acl.ListableRealm
• weblogic.security.acl.LoginFailureRecord
• weblogic.security.acl.ManageableRealm
• weblogic.security.acl.OwnerImpl
• weblogic.security.acl.PasswordGuessing
• weblogic.security.acl.PasswordGuessingWrapper
• weblogic.security.acl.PermissionImpl
• weblogic.security.acl.PrivilegedAction
• weblogic.security.acl.PrivilegedExceptionAction
• weblogic.security.acl.Realm
• weblogic.security.acl.RealmProxy
• weblogic.security.acl.RefreshableRealm
• weblogic.security.acl.SSLUserInfo
• weblogic.security.acl.Security
• weblogic.security.acl.SecurityMessage
• weblogic.security.acl.SecurityMulticastRecord
Chapter 2Removed Functionality and Components
2-61
• weblogic.security.acl.TTLCache
• weblogic.security.acl.UnlockUserRecord
• weblogic.security.acl.internal.AuthenticationDelegate
• weblogic.security.acl.internal.ClusterRealm
• weblogic.security.acl.internal.DefaultRealmImpl
• weblogic.security.audit.Audit
• weblogic.security.audit.AuditProvider
• weblogic.security.internal.RealmTest
• weblogic.security.ldaprealm.LDAPRealm
• weblogic.security.ldaprealmv1.LDAPDelegate
• weblogic.security.ldaprealmv1.LDAPException
• weblogic.security.ldaprealmv1.LDAPGroup
• weblogic.security.ldaprealmv1.LDAPRealm
• weblogic.security.ldaprealmv1.LDAPUser
• weblogic.security.ldaprealmv2.LDAPDelegate
• weblogic.security.ldaprealmv2.LDAPEntity
• weblogic.security.ldaprealmv2.LDAPGroup
• weblogic.security.ldaprealmv2.LDAPRealm
• weblogic.security.ldaprealmv2.LDAPRealmException
• weblogic.security.ldaprealmv2.LDAPUser
• weblogic.security.ntrealm.NTDelegate
• weblogic.security.ntrealm.NTRealm
• weblogic.security.unixrealm.SubprocessException
• weblogic.security.unixrealm.UnixDelegate
• weblogic.security.unixrealm.UnixGroup
• weblogic.security.unixrealm.UnixRealm
• weblogic.security.unixrealm.UnixUser
• weblogic.security.providers.realmadapter.AdjudicationProviderImpl
• weblogic.security.providers.realmadapter.AuditProviderImpl
• weblogic.security.providers.realmadapter.AuthenticationProviderImpl
• weblogic.security.providers.realmadapter.AuthorizationProviderImpl
• weblogic.security.providers.realmadapter.IdentityAsserterImpl
• weblogic.security.providers.realmadapter.LoginModuleImpl
• weblogic.security.providers.realmadapter.RealmAdapterAdjudicatorImpl
• weblogic.security.providers.realmadapter.RealmAdapterAuditorImpl
• weblogic.security.providers.realmadapter.RealmAdapterAuthenticatorImpl
Chapter 2Removed Functionality and Components
2-62
• weblogic.security.providers.realmadapter.RealmAdapterAuthorizerImpl
• RealmAdapterAdjudicatorMBean
• RealmAdapterAuditorMBean
• RealmAdapterAuthenticatorMBean
• RealmAdapterAuthorizerMBean
6.x Realms
The 6.x realm configuration and associated APIs have been removed from WebLogicServer as of version 12.2.1. The following deprecated configuration MBeans andassociated elements have been removed from the DomainMBean configuration element:
Configuration MBean Associated DomainMBean Configuration Element
SecurityMBean <security>
FileRealmMBean <file-realm>
CachingRealmMBean <caching-realm>
PasswordPolicyMBean <password-policies>
BasicRealmMBean <basic-realm>
CustomRealmMBean <custom-realm>
LDAPRealmMBean <ldap-realm>
NTRealmMBean <nt-realm>
RDBMSRealmMBean <rdbms-realm>
RealmMBean <realm>
UnixRealmMBean <unix-realm>
Certificate Request Generator Servlet
The Certificate Request Generator servlet has been removed fromOracle WebLogic Server as of version 12.2.1, including theweblogic.servlet.security.CertificateServlet class.
weblogic.AdminThe weblogic.Admin utility, a command-line interface for administering, configuring,and monitoring WebLogic Server, has been removed from Oracle WebLogic Serveras of version 12.2.1. Oracle recommends the WebLogic Scripting Tool (WLST) forall command-line operations previously available from the weblogic.Admin utility. SeeUnderstanding the WebLogic Scripting Tool.
Chapter 2Removed Functionality and Components
2-63
Note:
The weblogic.Admin utility used the compatibility MBean server to accessMBeans. As noted in Compatibility MBean Server and Type-Safe MBeanInterfaces, the compatibility MBean server is also removed. However, youcan use WLST to browse and access the full set of MBeans for configuring,monitoring, and managing WebLogic Server resources, including securityrealms.
JAXR
The JAVA API for XML Registries (JAXR) has been removed from Oracle WebLogicServer as of version 12.2.1.
Jersey 1.18 (JAX-RS 1.1. RI) Server APIs
The Jersey 1.18 (JAX-RS 1.1 RI) server APIs have been removed from OracleWebLogic Server as of version 12.2.1. You should use the corresponding standardJAX-RS 2.0 or Jersey 2.x APIs instead. See Introduction to RESTful Web Services inDeveloping and Securing RESTful Web Services for Oracle WebLogic Server.
WebLogic Keystore Provider
The WebLogic Keystore provider, which was deprecated in previous releases, hasbeen removed from WebLogic Server as of version 12.2.1.
weblogic.security.provider.PrincipalValidatorImpl
The weblogic.security.provider.PrincipalValidatorImpl class, which wasdeprecated in the previous release, is removed from WebLogic Server as of version12.2.1.
weblogic.xml.stream.util.XMLPullReaderBase
The weblogic.xml.stream.util.XMLPullReaderBase class, which was deprecated ina previous release, has been removed from Oracle WebLogic Server as of version12.2.1.
Connect-Time Failover
Oracle Connect-Time Failover was deprecated in an earlier release. This functionalityand the supporting documentation has been removed from Oracle WebLogic Serveras of version 12.2.1.
Chapter 2Removed Functionality and Components
2-64
Compatibility MBean Server and Type-Safe MBean Interfaces
As of Oracle WebLogic Server 12.2.1, the compatibility MBean server and all type-safeinterfaces to WebLogic Server MBeans are removed.
Startup Option for Lighter-Weight Runtime
The startup option for running a lighter-weight runtime instance of WebLogic Serverin a domain has been removed from Oracle WebLogic Server as of version 12.2.1.This startup option, shown below, resulted in a WebLogic Server instance that omittedthe startup of the Enterprise JavaBean, Java EE Connector Architecture, and JavaMessage Service services:
-DserverType="wlx"
The following sections of the WebLogic Server documentation that explain how to usethis startup option have been removed:
• Limiting Run-Time Footprint When Starting WebLogic Server in AdministeringServer Startup and Shutdown for Oracle WebLogic Server
• Using the weblogic.Server Command Line to Limit the WebLogic Server Run-TimeFootprint in Command Reference for Oracle WebLogic Server
Oracle WebLogic Server Proxy Plug-In for Oracle iPlanet Web Server
From 12.2.1.4.0 onward, the Oracle WebLogic Server proxy plug-in is not supportedfor Oracle iPlanet Web Server.
Chapter 2Removed Functionality and Components
2-65