Fusion Middleware Documentation
Advanced Search


What's New in Oracle WebLogic Server

This document, What's New in Oracle WebLogic Server, describes the following new and changed functionality in this WebLogic Server release:

Oracle Fusion Middleware 12.1.3 Support

This release of WebLogic Server is integrated with other Oracle Fusion Middleware 12.1.3 products. Oracle Fusion Middleware is a comprehensive family of products ranging from application development tools and integration solutions to identity management, collaboration, and business intelligence reporting. For more information, see the Oracle Fusion Middleware 12.1.3 documentation library page at http://docs.oracle.com/middleware/1213/index.html.

New APIs and Tools for Application Development

WebLogic Server 12.1.3 provides support for selected new or updated APIs from Java EE 7, such as JAX-RS 2.0, Java API for JSON Processing (JSR 353), Java API for WebSocket (JSR 356), and JPA 2.1. These APIs and related capabilities simplify development of server applications accessed by "rich" clients using lightweight web-based protocols such as REST, WebSocket, and Server-Sent Events. Improvements to development tooling and open source support expand developer choices and simplify creation of development environments.

These updates are described in the following sections:

Java API for JSON Processing 1.0 (JSR 353)

This release of WebLogic Server adds support for the Java API for JSON Processing 1.0 (JSR 353). JSON is a data exchange format widely used in web services and other connected applications. JSR 353 provides an API to parse, transform, and query JSON data using the object model or the streaming model.

For more information about the Java API for JSON Processing, see "Java API for JSON Processing" in Developing Applications for Oracle WebLogic Server.

Java API for RESTful Web Services (JAX-RS) 2.0

This release of WebLogic Server adds support of the Jersey 2.5.1 Java API for RESTful Web Services (JAX-RS) 2.0 Reference Implementation (RI) as a pre-built shared library.

For information about how to develop Java EE web services in WebLogic Server that conform to the Representational State Transfer (REST) architectural style using Java API for RESTful Web Services (JAX-RS), see Developing and Securing RESTful Web Services for Oracle WebLogic Server.

Server-Sent Events

This release of WebLogic Server adds support for server-sent events through the integration of the Jersey 2.5.1 library. The Jersey 2.5.1 library provides the Reference Implementation (RI) of JSR-399 (JAX-RS 2.0: Java API for RESTful Web Services) and is delivered as a shared library.

Server-sent events enable servers to push data to Web pages over standard HTTP. To use the Jersey 2.5.1 (JAX-RS 2.0 RI) server-sent events implementation, register the library and declare it in the appropriate deployment descriptors.

For more information, see "Using Server-Sent Events in WebLogic Server" in Developing and Securing RESTful Web Services for Oracle WebLogic Server.

Java API for WebSocket (JSR 356)

This release of WebLogic Server adds support for the Java API for WebSocket (JSR 356). Support for the Java API for WebSocket enables application developers to use the standard Java EE 7 WebSocket API for connections over the WebSocket protocol.

The proprietary WebLogic Server WebSocket API that was introduced in release 12.1.2 is deprecated but remains supported for backward compatibility.

Although the JSR 356 Java API for WebSocket coexists with the proprietary WebLogic Server WebSocket API, an application cannot contain calls to both APIs. Only one of the APIs can be used in an application.

For more information, including code examples, see "Using the WebSocket Protocol in WebLogic Server" in Developing Applications for Oracle WebLogic Server.

Protocol Fallback for WebSocket Messaging

This release of WebLogic Server adds support for protocol fallback for WebSocket messaging.

Protocol fallback provides a mechanism for using an alternative transport for WebSocket messaging when the WebSocket protocol is not supported. Typically the WebSocket protocol is not supported either because the WebSocket object is not available or because WebSocket frames are blocked by a firewall. In this release, the only supported alternative transport is HTTP Long Polling.

Protocol fallback enables application developers to rely on standard programming APIs to perform WebSocket messaging regardless of whether or not the runtime environment supports the WebSocket protocol. For more information, see "Enabling Protocol Fallback for WebSocket Messaging" in Developing Applications for Oracle WebLogic Server.

Java Persistence API (JPA) 2.1

This release of WebLogic Server supports JPA 2.1, which includes support or enhancements for features including Criteria Bulk Update/Delete, stored procedures, JPQL generic function, injectable entity listeners, TREAT, converters, DDL generation, and entity graphs. For the complete JPA 2.1 specification, see "JSR-000338 Java Persistence 2.1 (Final Release)" at http://jcp.org/aboutJava/communityprocess/final/jsr338/index.html.

For information about enabling JPA 2.1 as the persistence provider in the EJB container, see "Using JPA 2.1 with Oracle TopLink in WebLogic Server" in Developing Enterprise JavaBeans for Oracle WebLogic Server.

Updated Spring Support

The WebLogic Server/Spring integration features in this release of WebLogic Server support Spring Framework versions 3.0.x, 3.1.x, and 4.0.x. (Note that Spring Framework version 3.2.x is not supported.)

For more information about Spring Framework features that WebLogic Server supports for use inside Java EE applications, see Developing and Administering Spring Applications for Oracle WebLogic Server.

Updated Maven Support

Apache Maven is a software tool for building and managing Java-based projects. WebLogic Server provides support for Maven through the provisioning of plug-ins that enable you to perform various operations on WebLogic Server from within a Maven environment.

In this release of WebLogic Server, the following Maven support updates are included:

  • Maven plug-in installation and configuration enhancements.

  • Improvements in web services integration of ws-clientgen, ws-jwsc, and ws-wsdlc with the Maven life cycle.

  • Update to Apache Maven 3.0.5.

  • Support for a new wlst-client goal, which is a WLST wrapper for executing WLST online commands without requiring a local installation of WebLogic Server.

For more detail about the updated Maven support, see the following documentation:

Classloader Analysis Tool Enhancements

Applications may have multiple manifest references to classes that are not directly present in the applications's classpath, but which are being chained into the classpath by manifest references. In some cases, application developers may not be aware that additional classes have been unknowingly pulled into the application's classpath from other JARs, which in turn have manifest references to other JARs.

In this release of WebLogic Server, the Classloader Analysis Tool (CAT) adds the ability to search through an application's or module's classpath to detect and display the underlying chained manifest references.

For information, see "Using the Classloader Analysis Tool (CAT)" in Developing Applications for Oracle WebLogic Server.

Runtime Improvements

WebLogic Server 12.1.3 builds on support from prior WebLogic Server versions to improve the reliability, availability, scalability and performance of WebLogic Server applications in clustered environments, when using new Oracle database features, in multi data center architectures, and on Exalogic Systems.

These support improvements are described in the following topics:

Whole Server Migration with Dynamic and Mixed Clusters

This release of WebLogic Server adds support for whole server migration with dynamic and mixed clusters. Whole server migration behavior is the same for all clusters, but configuration differs depending on the cluster type.

For a dynamic cluster, you enable or disable automatic whole server migration in the server template. For a mixed cluster, you first enable automatic whole server migration in the server template used by the dynamic server instances in the mixed clusters. Then, you manually enable automatic whole server migration for any of the configured server instances in the cluster, and choose the machines to which you want to migrate if a server instance fails.

For more information, see "Whole Server Migration with Dynamic and Mixed Clusters" in Administering Clusters for Oracle WebLogic Server.

Bundling of Oracle Database 12c Driver

This release of WebLogic Server includes Oracle 12c JDBC drivers and is certified to operate with the Oracle 12c database. For more information, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network.

For information about limitations when using Application Continuity, see "Limitations with Application Continuity with Oracle 12c Database" in Administering JDBC Data Sources for Oracle WebLogic Server.

JDBC Data Sources

This release includes the following new and changed features:

Encrypted Connection Properties

As part of a secure configuration, it may be necessary to provide one or more connection property values that should not appear as clear text in the Data Source descriptor file. Update existing Data Source configurations using the Encrypted Properties attribute. See "Using Encrypted Connection Properties" in Administering JDBC Data Sources for Oracle WebLogic Server.

Connection Labeling Enhancements

WebLogic Server provides two new connection pool properties, ConnectionLabelingHighCost and HighCostConnectionReuseThreshold, to allow a connection pool to use brand-new physical connections to serve connection requests from different tenants without incurring re-initialization overhead on other tenant connections already in the pool. See "Using Initialization and Reinitialization Costs to Select Connections" in Administering JDBC Data Sources for Oracle WebLogic Server.

WebLogic Server supports callbacks, such as labeling and connection initialization, in EAR or WAR files used by packaged applications. See "Using Connection Labeling with Packaged Applications" in Administering JDBC Data Sources for Oracle WebLogic Server.

CountOfTestFailuresTillFlush and CountOfRefreshFailuresTillDisable

As of this release, the CountOfTestFailuresTillFlush and CountOfRefreshFailuresTillDisable attributes are disabled when their value is set to 0. In prior releases, the value was 2147483647.

Oracle Data Base Testing Using SQL ISVALID

A new Test Table name value of SQL ISVALID is now supported for Oracle databases. To improve connection testing performance of your Oracle data source, the default setting of the Test Table Name attribute of the connection pool is now SQL ISVALID. See "Database Connection Testing Options" in Administering JDBC Data Sources for Oracle WebLogic Server.

Oracle Enable JavaNet FastPath

The Oracle Enable JavaNet FastPath attribute on the Domain Structure > Services > Data Sources > Configuration:Oracle tab of the WebLogic Server Administration Console is no longer supported.

Change to securityCacheTimeoutSeconds Parameter

A maximum security cache limit of 10 minutes has been implemented for the -Dweblogic.jdbc.securityCacheTimoutSeconds parameter. In prior releases, there was no limit.

Derby Database Driver Version

The Derby Database driver has been updated to version 10.10.1.1.

Messaging

In this release of WebLogic Server, JMS includes the following:

  • Active GridLink Support for Oracle AQ JMS. For information, see "Configuring an AGL Data Source for AQ JMS" in Administering JMS Resources for Oracle WebLogic Server.

  • Support for whole server migration (WSM) with dynamic and mixed clusters. For information, see "Simplified JMS Cluster Configuration" in Administering JMS Resources for Oracle WebLogic Server.

  • To enable JMS .NET clients developed prior to WebLogic Server 12.1.3 to interoperate with WebLogic Server 12.1.3, set -Dweblogic.protocol.t3.login.replyWithRel10Content=true. See "Configuring WebLogic Server" in Developing JMS .NET Client Applications for Oracle WebLogic Server.

  • Certification with Oracle Streams Advanced Queuing (AQ) JMS in Oracle Database 12c. See "Interoperating with Oracle AQ JMS" in Administering JMS Resources for Oracle WebLogic Server.

JTA

This release of WebLogic Server includes the following new an changed JTA features:

Transactions without TLogs

Oracle improves XA transaction performance by providing the option to eliminate the writing of XA transactions to the TLog. XA transaction resources (Determiners) are used during transaction recovery when a TLog is not present. See "XA Transactions without TLogs" in Developing JTA Applications for Oracle WebLogic Server.

XA Transaction Cluster Affinity

XA transaction affinity improves performance by allowing server instances that are participating in a global transactions to service related requests rather than load-balancing these requests to other member servers. See "XA Transaction Cluster Affinity" in Developing JTA Applications for Oracle WebLogic Server.

Transaction Recovery Across Data Centers

This release of WebLogic Server includes new documentation that describes XA transaction recovery of WebLogic domains spanning physical sites. For documented procedures and approaches, see "Transaction Recovery Spanning Multiple Domains" in Developing JTA Applications for Oracle WebLogic Server.

Optimizations for Exalogic Elastic Cloud Software

This release of WebLogic Server includes additional optimizations for Exalogic Elastic Cloud software, including the following:

  • A WebLogic Replicated Store is a high performance storage option for Weblogic Messaging Services that require persistence in Oracle Exalogic Elastic Cloud environments. WebLogic Replicated stores depend on Exalogic replicated memory that is managed by a separately administered Daemon Cluster.

  • Cooperative Memory Management (CMM) promotes effective memory utilization by allowing WebLogic Server resources to adjust memory utilization in Exalogic Elastic Cloud environments.

  • An optimization for JDBC stores to commit a batch of INSERT or DELETE operations with the last operation of the transaction instead of issuing a separate commit call to database server. This feature saves a server round trip per transaction and benefits applications that have many transactions of a small number of operations or small messages.

  • TopLink Exalogic optimizations that include: batch writing, increasing the default cache size, and enable other optimizations such as weaving eager relationships. A runtime tuning agent optimizes the use of query batch fetching and dynamic query processing.

For more information, see Administering WebLogic Server for Oracle Exalogic Elastic Cloud.

WebLogic Tuxedo Connector

When TightlyCoupledTransactionsEnabled=true, if a transaction between WebLogic Server and Tuxedo resources use a Active GridLink (AGL) Data Source with GridLink Affinity enabled, then the XA Affinity Policy is automatically used for the transaction.

Manageability Improvements

WebLogic Server 12.1.3 continues to provide new management features which simplify the configuration, monitoring and ongoing management of WebLogic Server domains and applications. These new features are described in the following sections:

REST Resources for Server Management

This release of WebLogic Server includes a set of Representational State Transfer (REST) resources that support the following WebLogic domain management features:

  • Life cycle management for servers, deployments, resources

  • Deployment operations for applications and libraries

  • Data Source configuration

  • Access to server and application logs

  • Explicit participation in change management

For information about the RESTful management resources provided in this release, see RESTful Management Interface Reference for Oracle WebLogic Server.

Fusion Middleware Control

WebLogic Server can now be managed through Fusion Middleware Control. Fusion Middleware Control provides management support for all Fusion Middleware components, including WebLogic Server. Use Fusion Middleware Control to manage WebLogic Server when using other Fusion Middleware products in addition to WebLogic Server.

WebLogic Server support includes the following subsets of functionality:

  • Manage WebLogic Server clusters, server instances, and domains

  • Deploy and redeploy applications and manage application deployments

  • Create and configure JDBC data sources

  • Manage WebLogic Server messaging (JMS)

  • Create and configure users and groups

  • Create and configure server templates

For more information, see Administering Oracle WebLogic Server with Fusion Middleware Control.

Global Policy Attachment Support

WebLogic web services add support for global policy attachment using policy sets in this release of WebLogic Server. For more information, see the following topics in Securing Web Services and Managing Policies with Oracle Web Services Manager:

Security

This release of WebLogic Server includes the following new security features:

Creating a Custom Identity Keystore for a Network Channel

This version of WebLogic Server adds the ability to configure a network channel to use its own custom identity keystore, and other SSL attributes, that are separate from and that override the default keystore and SSL configuration settings for the Managed Server instance on which the channel is configured. This enables you to configure a WebLogic Server instance to use one identity and SSL configuration on one network channel, and another identity and SSL configuration on other channels.

For more information, see "Configuring an Identity Keystore Specific to a Network Channel" in Administering Security for Oracle WebLogic Server.

Authentication of Users Not Defined in Identity Store

In this version of WebLogic Server, the WebLogic Security Service has been enhanced to support the authentication of users who are not defined in the identity store of the security realm, but who instead are created as virtual users who are assigned subject principals based on attributes contained in X.509 client certificate passed in during the SSL handshake.

The WebLogic Identity Assertion provider is not configured by default to authenticate virtual users. However, by customizing this provider's configuration, you can enable this capability in a WebLogic domain.

The following features are provided to support this enhancement:

  • The WebLogic Identity Assertion provider is enhanced to optionally accept a client certificate passed in as an X.509 type token and to support virtual users.

  • A new interface is provided, X509SubjectComponentMapper, which extends the default user name mapper interface so that additional subject components from X.509 certificate attributes can be mapped to subject principals.

  • A Virtual User Authentication provider is included to supply the identity assertion virtual user LoginModule.

For more information, see "Authenticating a User Not Defined in the Identity Store" in Administering Security for Oracle WebLogic Server.

Logging Enhancements

In this release of WebLogic Server, the WebLogic logging services include the following changes:

  • The ability to configure java.util.logging logger levels. This new feature allows subsystems such as web services to simply use the java.util.logging APIs to log messages without having to manage the logging configuration. Configuring the java.util.logging logger levels can be managed by the logging system available in the environment.

    In addition, subsystem code does not need be aware of the environment in which it is running; for example, standalone WebLogic Server, the Oracle Fusion Middleware Infrastructure environment, and so on.

    For more information, see "Configuring java.util.logging Logger Levels" in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.

  • The Server Logging Bridge has been added to the root logger of the java.util.logging logger tree when WebLogic Server starts. This eliminates the need to explicitly configure the Server Logging Bridge.

    Note:

    See "Server Logging Bridge" in Upgrading Oracle WebLogic Server for important instructions about configuration changes that may be necessary when upgrading a WebLogic domain in which the Server Logging Bridge is configured.

WebLogic Diagnostic Framework

In this release of WebLogic Server, the WebLogic Diagnostic Framework includes the following changes:

  • WLST command changes, described in WLST.

  • WLDF Runtime Control changes

    In the prior version of WebLogic Server, when you used the WLDF Runtime Control to deploy a diagnostic system module based on an external resource descriptor, the WLDF Module name was derived from the external resource descriptor.

    In this release, if you deploy multiple instances of a diagnostic system module using the WLDF Runtime Control, WLDF now assigns the diagnostic resource name specified in the createSystemResourceControl command as the WLDF Module name. This makes it possible to correlate Harvester records and Watch rule notifications to the specific instances of a diagnostic system module that has been deployed.

    For more information, see "WLDF Runtime Control" in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

  • If multiple WLDF JDBC archive schemas exist in the same database, you can specify the particular schema to use for accessing JDBC-based archive tables in that database. This provides a way to distinguish among them when accessing the diagnostic archives. For more information, see "Configuring JDBC Resources for WLDF" in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

  • Example of using WLST to configure the Watch and Notification component and Harvester

    A set of scripts that demonstrate using WLST to configure the Watch and Notification and Harvester components have been added to the WebLogic Server code examples suite. These scripts are shown and described in the following sections in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server:

    If you install the WebLogic Server code examples and start the WebLogic Server samples domain, you can find these examples under the title "Configuring the Watch and Notification System and Harvesting Data Using WLST" when the samples web page is launched.

    For information about installing and configuring the WebLogic Server code examples, see "Sample Applications and Code Examples" in Understanding Oracle WebLogic Server.

WLST

This section describes new WebLogic Server WLST commands and changes to existing WebLogic Server WLST commands in this release.

The following WLST commands have been added in this release:

The following modifications were made to existing WLST commands in this release.

Upgrade

In WebLogic Server 12.1.3, the Reconfiguration Wizard now supports automatic reconfiguration of Node Manager from a per host Node Manager configuration to a per domain Node Manager configuration. The Node Manager home directory can be located in the domain home directory or in a custom location. In addition, per domain Node Manager configurations are automatically updated by the domain reconfiguration process.

For more information, see "Determining Node Manager Upgrade Procedure" in Upgrading Oracle WebLogic Server.

New Configuration Features

This section describes the configuration changes that have been implemented in this release of WebLogic Server.

-Dcom.oracle.cie.config.showProfile Java System Property

In WebLogic Server 12.1.3, the -Dcom.oracle.cie.config.showProfile Java system property has been added. When this property is set to true in the CONFIG_JVM_ARGS environment variable, the initial FMW Configuration Wizard screen contains options that allow you to specify whether the new domain is an expanded or compact domain.

For more information, see "Setting the CONFIG_JVM_ARGS Environment Variable" in Creating WebLogic Domains Using the Configuration Wizard and "Domain Topology Profiles" in Domain Template Reference.

unpack Command -initialize Parameter

An initialize parameter has been added to the unpack command. This parameter applies only to WebLogic domains in which other Fusion Middleware products are installed with WebLogic Server. By using this parameter during an unpack operation, you can initialize all or some of the config-mapping.xml values in the Service Table and OWSM data store, or not initialize any of these values.

For more information, see "Parameters of the unpack Command" in Creating Templates and Domains Using the Pack and Unpack Commands.

Deployment Validation Plug-In Support

This release of WebLogic Server includes an API for implementing a deployment validation plug-in that can intercept applications at the start of the deployment process and validate them prior to their deployment. The deployment validation plug-in support includes MBeans for enabling and configuring the plug-in.

For more information, see "Using a Deployment Validation Plug-In with WebLogic Server" in Deploying Applications with the WebLogic Deployment API.

Standards Support, Supported Configurations, and WebLogic Server Compatibility

The following sections describe WebLogic Server standards support, supported system configuration, and WebLogic Server compatibility:

Standards Support

This release of WebLogic Server supports the following standards and versions.

Java Standards

Table 1 lists currently supported Java standards.

Note:

See "WebLogic Server Security Standards" in Administering Security for Oracle WebLogic Server for the currently supported security standards, such as JAAS, JASPIC, JACC, JCE, and so forth.

While WebLogic Server 12.1.3 is a Java EE 6 compliant server, some Java EE 7 technologies have been added incrementally to this release; for example, JSR 356 Java API for WebSocket.

Table 1 Java Standards Support

Standard Version

Contexts and Dependency Injection for Java EE

1.0

Dependency Injection for Java EE

1.0

Expression Language (EL)

2.2, 2.1, 2.0

Only JSP 2.0 and greater supports Expression Language 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.0

JavaBeans Activation Framework

1.1

Java EE

6.0

Java EE Application Deployment

1.2

Java EE Bean Validation

1.0

Jave EE Common Annotations

1.1

Java EE Connector Architecture

1.6

Java EE EJB

3.1, 3.0, 2.1, 2.0, and 1.1

Java EE Enterprise Web Services

1.3, 1.2, 1.1

Jave EE Interceptors

1.1

Java EE JDBC

4.0, 3.0

Java EE JMS

1.1, 1.0.2b

Java EE JNDI

1.2

Java EE JSF

2.1.*, 2.0, 1.2, 1.1

Java EE JSP

2.2, 2.1, 2.0, 1.2, and 1.1

JSP 1.2. and 1.1 include Expression Language (EL), but do not support EL 2.x or greater.

Java EE Managed Beans

1.0

Java EE Servlet

3.0, 2.5, 2.4, 2.3, and 2.2

Java RMI

1.0

JavaMail

1.4

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

7, (6 and 7 clients)

JMX

2.0, when running WebLogic Server on JDK 6 or later

1.4, when running WebLogic Server on a JDK before JDK 6

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.1

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 Standards

For the current list of standards supported for WebLogic web services, see "Features and Standards Supported by WebLogic Web Services" in Understanding WebLogic Web Services for Oracle WebLogic Server.

Other Standards

Table 2 lists other standards that are supported in this release of WebLogic Server.

Note:

See "WebLogic Server Security Standards" in Administering Security for Oracle WebLogic Server for additional information on standards relating to security, such as SSL, TLS, and XACML, and so forth.

Table 2 Other Standards

Standard Version

SSL

v3

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 Hierarchical Role Based Access Control (RABC) Profile of XACML

2.0

Internet Protocol (IP)

Versions:

  • v6

  • v4


For more information about IPv6 support for all Fusion Middleware products, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network.

Supported Configurations

For the most current information on supported configurations, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network.

Licensing Information

For the most current information on Oracle Fusion Middleware Licensing, see Licensing Information.

WebLogic Server Compatibility

For the most current information on compatibility between current version of WebLogic Server and previous releases, see "WebLogic Server Compatibility" in Understanding Oracle WebLogic Server.

Deprecated Functionality (WebLogic Server 12c)

Information about deprecated functionality for WebLogic Server 12c Release 2 can be found on My Oracle Support at https://support.oracle.com/. Search for "Deprecated Features" in the Search Knowledge Base field.

WebLogic Full Client

The WebLogic full client, wlfullclient.jar, is deprecated as of WebLogic Server 12.1.3.

Log4j

The use of Log4j with the WebLogic logging service, as an alternative to Java logging, is deprecated as of WebLogic Server 12.1.3.

LogMBean.ServerLoggingBridgeUserParentLoggersEnabled Attribute

The ServerLoggingBridgeUserParentLoggersEnabled attribute on the LogMBean is deprecated as of WebLogic Server 12.1.3.

weblogic.Admin

The weblogic.Admin utility is deprecated in this release of WebLogic Server and will be removed in a future release.

weblogic.management.username and weblogic.management.password

As of WebLogic Server 12.1.1, the boot username and password system properties weblogic.management.username and weblogic.management.password have been deprecated and will be removed in a future release, and you will no longer be able to specify the username and password in the command for starting WebLogic Server in production mode.

As an alternative, Oracle recommends that you use the boot.properties file to specify the boot username and password for WebLogic Server. For more information about the boot.properties file, see "Boot Identity Files" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

For information about other methods you can use to provide user credentials, see "Provide User Credentials to Start and Stop Servers" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

Maven 11x Plug-In Deprecated

The weblogic-maven-plugin plug-in delivered in WebLogic Server 11g Release 1 is deprecated in this release. Oracle recommends that you instead use the WLS 12.1.2 Maven plug-in. See "Using the WebLogic Development Maven Plug-in" in Developing Applications for Oracle WebLogic Server for complete documentation.

JSP Tags for XML Processing

As of WebLogic Server 12.1.2, XSLT JSP tags and the WebLogic XSLT JSP Tag Library have been deprecated and will be removed in a future release. You can use JAXP to transform XML data. For more information, see "Transforming XML Documents" in Developing XML Applications for Oracle WebLogic Server.

weblogic.websocket and weblogic.websocket.annotation

As of WebLogic Server 12.1.3, the packages weblogic.websocket and weblogic.websocket.annotation are deprecated and will be removed in a future release. After these packages have been removed, you will no longer be able to use these packages for connections over the WebSocket protocol.

To ensure compatibility of your WebSocket applications with future releases of WebLogic Server, use the JSR 356 Java API for WebSocket instead of the deprecated packages.

For more information, including code examples, see "Using the WebSocket Protocol in WebLogic Server" in Developing Applications for Oracle WebLogic Server.

ActiveCache

ActiveCache is deprecated as of WebLogic Server 12.1.2.

Server Argument to WLST Diagnostics Commands

The Server argument to the following WLST diagnostics commands has been deprecated:

  • captureAndSaveDiagnosticImage

  • createSystemResourceControl

  • destroySystemResourceControl

  • disableSystemResource

  • enableSystemResource

  • listSystemResourceControls

The Server argument is being replaced by the Target argument. For more information, see "Diagnostics Commands" in WLST Command Reference for WebLogic Server.

URL Format for REST Management

The URL format for REST management APIs has changed in 12.1.3. The URL format introduced in 12.1.2 will continue to work, but is deprecated in this release of WebLogic Server.

Node Manager Log File Rotation Properties

As of WebLogic Server 12.1.3, the following Node Manager log file rotation properties are deprecated and may be removed in a future release:

  • FileSizeKB—use process.FileSizeKB

  • FileTimeSpan—use process.FileTimeSpan

  • FileTimeSpanFactor—use process.FileTimeSpanFactor

  • NumberOfFilesLimited—use process.NumberOfFilesLimited

  • RotatedFileCount—use process.RotatedFileCount

  • RotatationTimeStart—use process.RotationTimeStart

  • RotationType—use process.RotationType

For more information, see "Log File Rotation" in Administering Node Manager for Oracle WebLogic Server.

Node Manager Properties

As of WebLogic Server 12.1.3, the following Node Manager properties are deprecated and may be removed in a future release:

  • CipherSuite—use CipherSuites

  • CoherenceStartScriptEnabled—use coherence.StartScriptEnabled

  • CoherenceStartScriptName—use coherence.StartScriptName

  • DomainRegistrationEnabled

  • IfConfigDir—use weblogic.IfConfigDir

  • Interface—use InterfaceName=MinIP-MaxIP,NetMask=xxx

  • JavaHome—use weblogic.startup.JavaHome

  • NetMask—use InterfaceName=MinIP-MaxIP,NetMask=xxx

  • StartScriptEnabled—use weblogic.StartScriptEnabled

  • StartScriptName—use weblogic.StartScriptName

  • StopScriptEnabled—use weblogic.StopScriptEnabled

  • StopScriptName—use weblogic.StopScriptName

  • UseMACBroadcast—use weblogic.UseMACBroadcast

For more information, see "Node Manager Properties" in Administering Node Manager for Oracle WebLogic Server.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through 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.


Oracle Fusion Middleware What's New in Oracle WebLogic Server, 12c (12.1.3)

E41902-02

Copyright © 2007, 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license 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. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you 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 on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.