Management attributes are included on the ConnectionManagerMBean MBean and are viewable on the Proxy HTTP Report and the HTTP Servers tab in the Coherence-JVisualVM Plug-in. HTTP Acceptor Management – Management information is now provided for proxy servers and includes the number of connections across each proxy server and the total messages that were sent and received. For more information, see ' Getting a Cache Instance' in Developing Applications with Oracle Coherence. For more information, see ' Excluding Caches from Being Federated' in Administering Oracle Coherence.Ĭoherence Session API – The Coherence Session API provides applications with a new way to get a reference to a NamedCache instance. For more information, see ' Federated Session Caches' in Administering HTTP Session Management with Oracle Coherence*Web.ĭisabling Federation – Federated caching can be disabled for specific caches. For more information, see ' DestinationMBean' in Managing Oracle Coherence.įederating HTTP Sessions – HTTP Session caches can now be federated. Updated Federation Management – The DestinationMBean MBean now includes management information for replicateAll operations. For more information, see ' Plugging in a Cache Store Implementation' in Developing Applications with Oracle Coherence. For more information, see ' Defining Federation Participants' in Administering Oracle Coherence.įederation Support for Read-Through Caching – Cache entries that are loaded into a cache using a CacheStore implementation can now be federated across clusters. Simplified Federation Participant Configuration – An address port is no longer required when configuring Federation participants. For more information, see ' Using the Dynamic Recovery Quorum Policy' in Administering Oracle Coherence. For more information, see ' Support for Oracle Data Types' in Integrating Oracle Coherence.ĭynamic Active Persistence Quorum Policy – The dynamic recovery quorum policy is used with active persistence and automatically configures the persistence recovery quorum based on a predefined algorithm. Support for Oracle SDO_GEOMETRY and XMLType types – Oracle-specific data types that are supported by EclipseLink can be used by HotCache. For more information, see ' Warming Caches with HotCache' in Integrating Oracle Coherence. Warming Caches – HotCache can be used to warm caches by loading an initial dataset. For more information, see ' Configuring HotCache JPA Properties' in Integrating Oracle Coherence.

HotCache JPA properties – JPA properties can be used to configure HotCache behavior. HotCache Enhancements – Coherence includes new HotCache functionality. For more information, see ' Federating Events to Custom Participants' in Administering Oracle Coherence. Custom participants are implemented as event interceptors and are configured as part of a federation topology. For example, cache data can be federated to a database, message bus, log file, and so on. Custom Federation Participants – Custom participants allow applications to federate data to multiple non-Coherence end-points or resources.

Oracle coherence release schedule