Each report definition file results in the creation of a report file that displays management information based on a particular set of metrics. The files include a report group configuration files ( report-group.xml, the default), which refer to any number of report definition files.
The files are located in the /reports directory within coherence.jar. Management configuration files â A set of files that are used to configure Coherence management reports. See Appendix D, "POF User Type Configuration Elements," for a complete reference of the elements in this file. The schema for this file is the coherence-pof-config.xsd file. This file is typically referred to as the POF configuration deployment descriptor.
#Ipartition 3.5.1 portable#
See Appendix B, "Cache Configuration Elements," for a complete reference of the elements in this file.Ĭoherence-pof-config.xml â This file is used to specify custom data types when using Portable Object Format (POF) to serialize objects. The schema for this file is the coherence-cache-config.xsd file. This file is typically referred to as the cache configuration deployment descriptor. The schema file for this override file and the schema for the operational deployment descriptor are the same.Ĭoherence-cache-config.xml â This file is used to specify the various types of caches which can be used within a cluster. The settings in this file are suitable for production environments. Tangosol-coherence-override-prod.xml â This file overrides operational settings in the tangosol-coherence.xml file when Coherence is started in production mode. The schema file for this override file and the schema for the operational deployment descriptor are the same.
The settings in this file are suitable for evaluating Coherence.
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 development environments. By default, Coherence is started in developer mode and the settings in this file are used. Tangosol-coherence-override-dev.xml â This file overrides operational settings in the tangosol-coherence.xml file when Coherence is started in developer mode. See Appendix A, "Operational Configuration Elements," for a complete reference of the elements in the operational deployment descriptor. The schema for this file is the coherence-operational-config.xsd file. This file is typically referred to as the operational deployment descriptor. Tangosol-coherence.xml â This files provides operational and run-time settings and is used to create and configure cluster, communication, and data management services. However, the recommended approach is to provide configuration files that override the default configuration files. The files are for demonstration purposes only and can be reused or changed as required for a particular application or solution. The configuration files provide a default setup that allows Coherence to be used out-of-box with minimal changes. The easiest way to inspect these files and their associated schemas is to extract the Coherence library to a directory. The Coherence distribution includes a set of default XML configuration files that are included within the COHERENCE_HOME \lib\coherence.jar library. 3.1 Overview of the Default Configuration Files
0 kommentar(er)
