This appendix provides a detailed reference of the report file deployment descriptor elements and includes a brief overview of the descriptor. See Appendix C, "Report Group Configuration Elements," for a detailed reference of the report group deployment descriptor elements.
This appendix includes the following sections:
The report file deployment descriptor specifies a report for displaying management information that is based on MBeans. The coherence.jar/reports directory contains many predefined report files. Modify the reports or create new reports as required. See Chapter 6, "Analyzing Report Contents," for additional information about the predefined reports.
The report file deployment descriptor schema is defined in the coherence-report-config.xsd file, which is located in the root of the coherence.jar library and at the following Web URL:
http://xmlns.oracle.com/coherence/coherence-report-config/1.0/coherence-report-config.xsd
The <report-config> element is the root element of the deployment descriptor and typically includes the XSD reference, the namespace reference, and the location of the coherence-report-config.xsd file. For example:
<?xml version='1.0'?> <report-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/coherence/coherence-report-config" xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-report-config coherence-report-config.xsd">
Notes:
The schema that is located in the coherence.jar library is always used at run time even if the xsi:schemaLocation attribute references the Web URL.
Omit the xsi:schemaLocation attribute to disable schema validation.
When deploying Oracle Coherence into environments where the default character set is EBCDIC rather than ASCII, ensure that the deployment descriptor file is in ASCII format and is deployed into its run-time environment in the binary format.
Table B-1 lists all nonterminal report file deployment descriptor elements.
Used in: row
The column element contains information to generate a report column. The column element supports the use of an id attribute to uniquely identify the column. The ID is used within the column-ref subelement.
Table B-2 describes the subelements of the column element.
| Element | Required/ Optional |
Description |
|---|---|---|
|
|
Optional |
Specifies an
|
|
|
Optional |
Specifies an attribute or method name on the MBean. For composite data types, the |
|
|
Optional |
Specifies the column header. The value of the |
|
|
Optional |
Specifies a character that separates column or array values. Valid values are |
|
Optional |
Specifies information necessary to construct a JMX query to find all MBeans contributing to the report or column. |
|
|
|
Optional |
Specifies whether the column value is hidden in the report. Valid values are |
|
|
Optional |
Specifies a reference to a column identifier. The reference passes a column value as an argument to a filter or another column. |
|
|
Optional |
Specifies the name of the calculation to apply to the associated MBean attribute values. This element is only valid when the
|
|
Optional |
Specifies an argument column or a filter reference |
|
|
|
Optional |
Specifies the data type of a constant column. Valid values are |
|
|
Optional |
Specifies the value of a constant column |
|
|
Optional |
specifies whether the column is included in the |
|
|
Optional |
Specifies whether the column is included as part of a subquery. Valid values are |
|
|
Optional |
Specifies if a negative value is returned to the query. Negative values are considered |
Used in: filters
The filter element defines a filter to use in the report. The filter element supports the use of an id attribute to uniquely identify the filter. Use the ID when referring to a filter with the filter-ref element. Filters can be referenced from within a params element and a query element.
Table B-3 describes the subelements of the filter element.
| Element | Required/ Optional |
Description |
|---|---|---|
|
|
Optional |
Specifies an
|
|
Optional |
Specifies an argument column or a filter reference |
Used in: column, filter, query
Table B-5 describes the subelements of the params element.
| Element | Required/ Optional |
Description |
|---|---|---|
|
|
Required |
Specifies a reference to a filter ID. The reference passes a filter as an argument to a query or another filter. |
|
|
Required |
Specifies a reference to a column identifier. The reference passes a column value as an argument to a filter or another column. |
The query element contains information necessary to construct a JMX query to find all MBeans contributing to the report or column. Enter queries within a <pattern> element.
The following example includes all node MBeans in the report or column:
<query> <pattern>Coherence:type=Node,*</pattern> </query>
The following example that includes only the Cluster MBean in the report or column:
<query> <pattern>Coherence:type=Cluster</pattern> </query>
The pattern string allows macro substitutions with run-time values that come from report columns. For example, to provide a cache name in the query pattern, define a reporter.cacheName system property and use the following construct:
<report>
...
<query>
<pattern>Coherence:type=Cache,name={CacheName},*</pattern>
</query>
<row>
<column id="CacheName">
<type>property</type>
<name>reporter.cacheName</name>
</column>
</row>
</report>
Sometimes a query pattern is known to result in a list of MBean names that have a well-known key attribute. Use the key attribute to retrieve an attribute from a related (joined) MBean. For example, because the Coherence:type=Service,* pattern is known to result in MBeans in the Coherence:type=Service,nodeId=NNN format, the following configuration below prints the MemberName attribute from a corresponding NodeMBean along with the ServiceName attribute for the ServiceMBean.
<report>
...
<query>
<pattern>Coherence:type=Service,*</pattern>
<params>
<column-ref>MemberName</column-ref>
<column-ref>NodeId</column-ref>
<column-ref>ServiceName</column-ref>
</params>
</query>
<row>
<column id="MemberName">
<type>attribute</type>
<name>MemberName</name>
<query>
<pattern>Coherence:type=Node,nodeId={NodeId}</pattern>
</query>
</column>
<column id="NodeId">
<type>key</type>
<name>nodeId</name>
</column>
<column id="ServiceName">
<type>key</type>
<name>name</name>
</column>
</row>
</report>
Table B-6 describes the subelements of the query element.
| Element | Required/ Optional |
Description |
|---|---|---|
|
|
Required |
Specifies a JMX query or object name to include in the report |
|
|
Optional |
Specifies a reference to a filter ID. The reference passes a filter as an argument to a query or another filter. |
|
Optional |
Specifies an argument column or a filter reference |
Used in: report-config
The report element contains information necessary to generate a JMX-based report. A report can include any number of report elements; however, a report file typically contains a single report definition.
Table B-7 describes the subelements of the report element.
| Element | Required/ Optional |
Description |
|---|---|---|
|
|
Optional |
Specifies a descriptive heading for the associated report or column. |
|
|
Required |
Specifies the file name for the generated report. The file name is either absolute or relative to a directory that is specified in the corresponding report group deployment descriptor. If the specified file exists, then the new report lines are appended to the file; otherwise, a new report file is created. The file name may contain three macros:
Note: A process running the reporter requires read, write, and create access to the report output directory. |
|
|
Optional |
Specifies a character that separates column or array values. Valid values are |
|
|
Optional |
Specifies whether the report includes description and column headers. Valid values are |
|
Optional |
Specifies a group of filters for the report |
|
|
Required |
Specifies information necessary to construct a JMX query to find all MBeans contributing to the report or column |
|
|
Required |
Specifies information to generate a report row |
Root Element
The report-config element is the root element of the report configuration deployment descriptor and contains the report definition.