How to Override the Default Coherence*Web Cache Configuration with a Custom Cache Configuration File
(Doc ID 1440139.1)
Last updated on NOVEMBER 18, 2024
Applies to:
Oracle Coherence - Version 2.5.1 to 3.7.1Information 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:
- Customized session-cache-config.xml that is not on the classpath.
- 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
- Customized cache configuration file that is not called session-cache-config.xml, either on or off the classpath.
- 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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |