The name and location of the default report group configuration file is specified in the operational configuration deployment descriptor within the node. A custom report group configuration file can be specified by either using an operational override file or a system property.
The report group configuration file is only loaded if JMX management is enabled. The examples in this section demonstrate enabling JMX management on nodes that host an MBean server.
3.5.1.1 Overriding the Default Report Group Configuration File
The name and location of a custom report group configuration file can be specified using an operational override file. This mechanism overrides the default name and location of the report group configuration file.
Edit the file and enter a node that specifies the name of the report group configuration file. If the report group configuration file is not located in the classpath, enter the full (or relative) path to the file as well. The element also supports the use of a URL when specifying the location of a report group configuration file.
The following example demonstrates starting a cache server using an operational override file and a report group configuration file that are located in COHERENCE_HOME .
3.5.1.2 Using the Report Group Configuration File System Property
The tangosol.coherence.management.report.configuration system property is used to specify a custom report group configuration file to be used instead of the default report-group.xml file. The system property provides an easy way to switch between different configurations and is convenient during development and testing. Continue reading “3.5.1 Specifying a Custom Report Group Configuration File”