Database Reference
In-Depth Information
•
Derived Associations
: The EM12c Extensibility framework provides a mean to define
dependencies and other relations between target types, either by using one of the predefined
associations (such as
deployed_on
,
provided_by
, or
cluster_contains)
, or by defining new
associations. This provides EM12c with the topology of a complex system, such as a cluster
database or a web farm in which multiple monitored components are interconnected.
Associations are usually implemented along with configuration management to ensure that
a system topology is defined and configuration of the complete system can be managed.
Derived associations are defined in the
oracle.samples.xsh2
example plug-in.
•
Target Discovery
: Plug-in developers can enable automatic and guided discovery modes
in addition to manual targets addition process where EM12c users must configure a target
instance from scratch. This involves defining special discovery rules and scripts generally
implemented in Java or Perl. Use the
oracle.samples.xsh3
plug-in to study an example
discovery implementation.
•
Compliance Standards
: This feature allows you to define compliance rules. The rules can be
based on either the existing metrics and configuration collections in the repository (SQL or
PL/SQL based) or on the real-time collection targeted toward files, users, processes, database
objects, a Windows Registry entry, or an Active Directory entity. The rules are organized
hierarchically into compliance standards, and then compliance frameworks are defined based
on those standards. Extensive examples of defining compliance standards are in Chapter 12 of
the
Extensibility Programmer's Reference
. A Compliance Standards example implementation is
in plug-in
oracle.samples.xsh3
.
•
Management User Interface
: This is probably the most exciting new capability of EM12c
Extensibility, allowing plug-in developers to create a completely custom user interface and
to control the user experience. The custom user interface not only lets plug-in developers
control how collected metrics and configuration information is displayed, but also gives full
capabilities for an interactive user interface, including performing administrative actions
such as starting and stopping components, killing sessions or users, creating target resources,
and pretty much any other action that an administrator might need to perform. There are
two ways to create a custom user interface. The easier but more limited method is to use the
metadata-based management interface for defining pages, screen layout, and actions purely
declaratively via XML constructs. While it's a huge step compared to 10g and 11g, limited
interactive features are available. The more complex method is to use the Adobe Flex-based
framework, which gives complete control over the user experience and full interactive
capabilities, as well as allows you to package custom UI components with the plug-in.
A metadata-based declarative UI is implemented in
oracle.samples.xsh2
. A Flex-based UI
is implemented in
oracle.samples.xsh3
. However, there is only a prebuild Flex component,
and I couldn't locate it in the sources. For a more complete Flex-based example, use another
example in
<EDK>/samples/plugins/HostSample
.
•
Customized Incident Management
: This feature allows plug-in developers to customize
what you see on the Incident Manager page when selecting an incident. They can add
information in the incident details region, customize the diagnostic links, define a new guided
resolution region, as well as override the default search expression for My Oracle Support.
The documentation refers to registering incident management customizations by using only
MRS, but based on the target path where metadata is stored in OMS,
empdk
should be able to
package incident management customizations as part of a plug-in archive if it's placed under
either
<STAGE>/oms/metadata/events/custmzn
or
<STAGE>/oms/metadata/custmzn
.
Note that the best implementation of a Flex-based UI is in the
HostSample
demo located in the EDK in
<EDK>/samples/plugins/HostSample
. A
README
file explains how to build the plug-in as well as how to use Adobe Flash
Builder to open and work with the Flex-based UI, which is a great way to learn advanced UI development with EM12c.
