The following topics introduce the new and changed features of Oracle Coherence and other significant changes that are described in this guide, and provides pointers to additional information. This document is the new edition of the formerly titled User's Guide for Oracle Coherence*Web.
Oracle Coherence 12c (12.1.2) includes the following new and changed features for this document.
The use of Coherence container with applications running on WebLogic Server. Coherence container provides Coherence applications with the same benefits as other Java EE applications that are hosted on WebLogic Server. For more information, see Chapter 2, "Using Coherence*Web with WebLogic Server." See also, Oracle Fusion Middleware Developing Oracle Coherence Applications for Oracle WebLogic Server.
coherence-web.jar and the
coherence.jar files now appear on the WebLogic Server system classpath. This means that you do not have to include the
coherence-web.jar files in the web application's classpath. For more information, see "Overview of Coherence*Web".
Coherence cache configurations and services used by Coherence*Web are now defined in the
default-session-cache-config.xml file, which can be found in the
coherence-web.jar file. You can create your own custom session cache configuration by packaging a file named
session-cache-config.xml in your Web application. For more information see, "Using a Custom Session Cache Configuration File".
For 12c (12.1.2), this guide has been updated in several ways. Following are the sections that have been added or changed.
Added Apache Tomcat 7.x to the list of supported web containers. See "Supported Web Containers".
Added information on how the session ID is updated in Coherence *Web. See "Updating the Session ID".
Added information on how to strip WebLogic session affinity suffix from the session cookie so that Coherence*Web sessions can be shared with other application servers. See "Sharing Coherence*Web Sessions with Other Application Servers".
Added a table which describes the compatibility between versions of standalone WebLogic Server and Coherence. See "WebLogic Server and Coherence: Compatibility".
Added information on how to change the default name of the session cache configuration file. See "Customizing the Name of the Session Cache Configuration File".
Added information on the use of logging with Coherence*Web. See "Configuring Logging for Coherence*Web".
Added information on how to use a cache delegator to ensure that the local cache should be used for storing and retrieving the session instance before attempting to use the distributed cache. See "Getting Concurrent Access to the Same Session Instance".
Revised the instructions for using Coherence*Web with Oracle Portal. See Chapter 10, "Using Coherence*Web with WebLogic Portal."
Added information on how to use the Coherence*Web extension for Oracle Virtual Assembly Builder (OVAB). See Appendix E, "Oracle Coherence*Web Extension for OVAB."
There was an error in the listing of the sample
session-cache-config.xml file in Appendix D, "Session Cache Configuration File Without a Near Cache." This error has been corrected.