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. The schema file for this override file and the schema for the operational deployment descriptor are the same.

tangosol-coherence-override-eval.xml – This file overrides operational settings in the tangosol-coherence.xml file when Coherence is started in evaluation mode. The settings in this file are suitable for evaluating Coherence. The schema file for this override file and the schema for the operational deployment descriptor are the same.

3 Understanding Configuration

tangosol-coherence-override-prod.xml – This file overrides operational settings in the tangosol-coherence.xml file when Coherence is started in production mode. The settings in this file are suitable for production environments. The schema file for this override file and the schema for the operational deployment descriptor are the same.

coherence-cache-config.xml – This file is used to specify the various types of caches which can be used within a cluster. This file is typically referred to as the cache configuration deployment descriptor. The schema for this file is the coherence-cache-config.xsd file. See Appendix B, “Cache Configuration Elements,” for a complete reference of the elements in this file.

coherence-pof-config.xml – This file is used to specify custom data types when using Portable Object Format (POF) to serialize objects. This file is typically referred to as the POF configuration deployment descriptor. The schema for this file is the coherence-pof-config.xsd file. See Appendix D, “POF User Type Configuration Elements,” for a complete reference of the elements in this file.

Management configuration files – A set of files that are used to configure Coherence management reports. The files are located in the /reports directory within coherence.jar . The files include a report group configuration files ( report-group.xml , the default), which refer to any number of report definition files. Each report definition file results in the creation of a report file that displays management information based on a particular set of metrics. The schema for these files are the coherence-report-config.xsd file and the coherence-report-group-config.xsd file, respectively. See Managing Oracle Coherence for detailed information on using reports and a reference for the elements in these configuration files.

3.2 Specifying an Operational Configuration File

The tangosol-coherence.xml operational deployment descriptor provides operational and run-time settings and is used to create and configure https://hookupdate.net/es/christiandatingforfree-review/ cluster, communication, and data management services. At run time, Coherence uses the first instance of tangosol-coherence.xml that is found in the classpath.