How to Override the Default Coherence*Web Cache Configuration with a Custom Cache Configuration File (Doc ID 1440139.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Coherence - Version 2.5.1 to 3.7.1
Information in this document applies to any platform.

Goal

To explain how to override the default Coherence*Web cache configuration file, session-cache-config.xml, with a custom cache configuration.

For example, these scenarios would all lead to the customized configuration not being used:

  1. Customized session-cache-config.xml that is not on the classpath.
  2. Customized session-cache-config.xml that is not on the classpath, but whose location is specified using -Dtangosol.coherence.cacheconfig=/path/to/session-cache-config.xml
  3. Customized cache configuration file that is not called session-cache-config.xml, either on or off the classpath.
  4. Customized cache configuration file that is not called session-cache-config.xml, either on or off the classpath, but whose location is specified using -Dtangosol.coherence.cacheconfig=/path/to/session-cache-config.xml

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms