3.1 Overview of the Default Configuration Files
This chapter describes each of the default configuration files that are distributed with Coherence and details how applications and solutions override these files when creating their own Coherence configurations.
The Coherence distribution includes a set of default XML configuration files that are included within the COHERENCE_HOME \lib\coherence.jar library. The easiest way to inspect these files and their associated schemas is to extract the Coherence library to a directory.
The configuration files provide a default setup that allows Coherence to be used out-of-box with minimal changes. The files are for demonstration purposes only and can be reused or changed as required for a particular application or solution. However, the recommended approach is to provide configuration files that override the default configuration files.
tangosol-coherence.xml – This files provides operational and run-time settings and is used to create and configure cluster, communication, and data management services. This file is typically referred to as the operational deployment descriptor. The schema for this file is the coherence-operational-config.xsd file. See Appendix A, “Operational Configuration Elements,” for a complete reference of the elements in the operational deployment descriptor.
tangosol-coherence-override-dev.xml – This file overrides operational settings in the tangosol-coherence.xml file when Coherence is started in developer mode. By default, Coherence is started in developer mode and the settings in this file are used. The settings in this file are suitable for development environments. Continue reading →