This section describes the changes to documentation.
Topics
Japanese Text Displays in Some Search Results Topics Avitek Medical Records
Online Help For Configuring the RDBMS Security Store is Incorrect
Documentation Update for the WebServerMBean MaxPostSize Attribute
Documentation Update for Specifying the Logging Implementation
Updates to the WebLogic Plug-In Enabled Attribute Description
weblogic.wsee.wstx.wsat Package is Incorrectly Marked as Deprecated
Issue
Impacted Platforms: All
The Search function in the Samples viewer does not work when accessing the Examples documentation by selecting Oracle WebLogic > WebLogic Server > Examples > Documentation from the Windows Start menu.
Workaround
To search the Sample Applications and Code Examples, you must start the Examples server and navigate to http://localhost:7001/examplesWebApp/docs/core/index.html. Click Instructions and then Search.
Issue
Impacted Platforms: All
The samples viewer Search function may sometimes return topics that display the Japanese and English versions of some Avitek Medical Records topics simultaneously.
Workaround
No workaround available.
Issue
Impacted Platforms: All
After extracting the WebLogic Server documentation library ZIP files that are available from http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html, the HTML pages may not display properly in some cases for the following libraries:
E12840_01 (WebLogic Server 10.3.0 documentation library)
E12839_01 (WebLogic Server 10.3.1 documentation library)
E14571_01 (WebLogic Server 10.3.3 documentation library)
Workaround
For library E12840-01, after extracting the E12840_01.zip library file, if the HTML pages are not formatting correctly, perform the following steps:
/global_resources directory in the directory structure./global_resources directory to the root directory of the same drive.For libraries E12839-01 and E14571-01, this issue occurs only on Windows operating systems. If the HTML pages of the extracted library are not formatting correctly, try extracting the ZIP file using another extraction option in your unzip utility. For example, if you are using 7-Zip to extract the files, select the Full pathnames option. Note that you cannot use the Windows decompression utility to extract the library ZIP file.
Issue
Impacted Platforms: All
As of WebLogic Server 12.1.2, the Configuration Wizard no longer supports configuring the RDBMS security store. To configure the RDBMS security store, you must use WLST. The following Administration Console online help incorrectly describes using the Configuration Wizard to configure the RDBMS security store:
Workaround
For information on configuring the RDBMS security store using WLST, see Managing the RDBMS Security Store in Oracle Fusion Middleware Administering Security for Oracle WebLogic Server.
Issue
Impacted Platforms: All
A previous version of the documentation in Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server incorrectly indicated that you can override the WebLogic Server JSF version by bundling a different version of JSF with your application.
Workaround
If you encounter any issues with your JSF implementation, Oracle recommends visiting My Oracle Support at http://support.oracle.com/ and filing a support issue.
Issue
Impacted Platforms: All
The WebLogic Server Administration Console online help in this release contains some references to J2EE and J2SE.
Workaround
These references should instead be to Java EE and Java SE, respectively. For more information on the Java version naming updates, see http://www.oracle.com/technetwork/java/javase/overview/javanaming-2227065.html.
Issue
Impacted Platforms: All
The documentation for the WebServerMBean MaxPostSize attribute incorrectly states the following: The maximum post size this server allows for reading HTTP POST data in a servlet request, excluding chunked HTTP requests (Transfer-Encoding: chunked).
Workaround
The correct description for this attribute is as follows: The maximum post size this server allows for reading HTTP POST data in a servlet request.
Issue
Impacted Platforms: All
As of this release of WebLogic Server, Log4j is deprecated. Related, the functionality to set the logging implementation using the WebLogic Server Administration Console was removed. As a result, the task describing this functionality in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help, Specify the logging implementation, is no longer applicable.
Workaround
No workaround available.
Issue
Impacted Platforms: Generic
Updates to the WebLogic Plug-In Enabled attribute description.
Workaround
The WebLogic Plug-In Enabled attribute appears on the Server > Configuration > General and Cluster > Configuration > General WebLogic Server Administration Console pages.
The updated description for this attribute at the server level is as follows:
Specifies whether this server uses the proprietary WL-Proxy-Client-IP header.
There are three values you can select in WebLogic Plug-In Enabled:
Select Yes to specify that this server instance uses the proprietary WL-Proxy-Client-IP header, which is recommended if the server instance will receive requests from a proxy plug-in. If this server instance is a member of a cluster that will received proxied requests, enable the WebLogic plug-in at the cluster level. For servers that are members of a cluster, the setting at the cluster level overrides the server's setting. When the WebLogic plug-in is enabled at the cluster level, a call to getRemoteAddr will return the address of the browser client from the proprietary WL-Proxy-Client-IP header instead of the Web server.
Select No to disable the weblogic-plugin-enabled parameter (weblogic-plugin-enabled=false) in the config.xml file.
Select Default for this server instance to use the value selected for WebLogic Plug-in Enabled for the cluster.
The updated description for this attribute at the cluster level is as follows:
Specifies if this cluster will receive requests from a proxy plug-in or HttpClusterServlet.
There are three values you can select in WebLogic Plug-In Enabled:
Select Yes if the cluster will receive requests from a proxy plug-in or HttpClusterServlet. A call to getRemoteAddr will return the address of the browser client from the proprietary WL-Proxy-Client-IP header, instead of the Web server.
Select No to disable the weblogic-plugin-enabled parameter (weblogic-plugin-enabled=false) in the config.xml file.
Select Default for this cluster to use the value selected for WebLogic Plug-In Enabled for the domain.
For non-clustered servers that will receive proxied requests, this attribute may be set at the server level, on the Server > Configuration > General page.
WeblogicPluginEnabled is duplicated both in ClusterMBean and ServerMBean. ClusterMBean overrides ServerMBean.
Issue
Impacted Platforms: All
The weblogic.wsee.wstx.wsat package, which includes the weblogic.wsee.wstx.wsat.Transactional annotation, is incorrectly marked as deprecated in the Oracle Fusion Middleware Java API Reference for Oracle WebLogic Server.
Workaround
You can continue to use this annotation in this release.