Database Reference
In-Depth Information
3.
You can modify and further customize the extracted XML report definition. The XML
format provides the report developer additional design features not available directly in
the EM12c console reports wizard. Most of Chapter 4 of the
Extensibility Programmer's
Reference
is dedicated to the documentation of XML elements for Information Publisher
reports, and you should use that as a reference.
Finally, place the created report definition files into
<STAGE>/oms/metadata/reports
and
package the new version of the plug-in. EDK will automatically pick up reports during
creation of the OPAR file as long as the report definitions are placed in the correct location.
4.
When the plug-in with reports is deployed on the OMS, its reports are available in the EM12c console in the
Information Publisher Reports section as SYSTEM reports. These reports cannot be deleted or modified by the EM12c
users. However, the reports can be cloned to create a copy that can be customized if required. 10g/11g Grid Control
allowed to mark some SYSTEM reports to be available directly on the target's home page in the Reports tab. This tab
has been removed from EM12c, because it provides UI customization of the target home page that far supersedes the
older capabilities of simply embedding reports.
Two reports in the category Performance Reports of the
oracle.samples.xsh1
plug-in are good examples to
study. The configuration report with this plug-in is using dummy data (selecting constants from DUAL table), so that
isn't a useful example to study.
It's useful to use the Metadata Registration Service (MRS) to update report definitions directly in the repository
without repackaging and redeploying the plug-in. See more details about MRS at the end of this chapter.
Enterprise Configuration Management
The EM12c Extensibility framework has full support for Enterprise Configuration Management (ECM). While 10g/11g
Grid Control supported ECM feature, it wasn't documented and officially supported for third-party plug-in developers
(even though ECM was used by Oracle's own plug-ins). EM12c added XML metadata definitions to ECM instead of
awkward PL/SQL-based definitions, and that allowed simple support for plug-in developers.
There are three steps to adding configuration management capabilities:
1.
Determine a configuration that needs to be collected. Organize that configuration in
one or more tables, where each table corresponds to a configuration item. Configuration
item can be single row or multirow, just like collecting monitoring metrics. If tables
defining a configuration have relations between them, it's possible to define the full ECM
schema with hierarchical relations. Think of it as ECM metadata describing configuration
information to EM12c so that it can be used in the same manner as for out-of-the-box
targets. ECM metadata is an XML file placed in the OMS staging area in the
<STAGE>/oms/metadata/snapshotlive
directory. Based on the ECM metadata, EM12c
creates custom tables and views in the
SYSMAN
schema of the repository.
2.
Each configuration item is collected as a metric defined in the target type metadata XML
file, with special settings required for configuration metrics. Thus, you need to define
special collection metrics in the target type metadata.
3.
Define special default collection items in the default collection metadata XML file.
Out of three examples provided in the EDK, only the
oracle.samples.xsh3
plug-in contains complete implementation
of ECM. The
oracle.samples.xsh1
and
oracle.samples.xsh2
plug-ins do have configuration metrics defined but are
missing ECM metadata, so no repository tables are created, which means configuration information gathered by the
agent is not actually loaded anywhere. Just ignore the metrics in the first two sample plug-ins. I suspect the developers
simply forgot to remove these metrics when splitting the demo plug-in into multiple examples.
Listing 10-19 contains the ECM metadata snippet from the
oracle.samples.xsh3
plug-in. This file should be
placed in the staging area in
<STAGE>/oms/metadata/snapshotlive
.
