Database Reference
In-Depth Information
Plug-ins
Plug-ins
take on a whole new meaning in EM12c. In earlier releases, plug-ins were largely system-monitoring utilities
used to monitor and manage non-Oracle (heterogeneous) software including databases and middleware. Partners
or Oracle Corporation itself usually built them. Some technically savvy customers built their own as well, but there
weren't many plug-ins overall.
In the EM12c release, a few of these monitoring plug-ins remain, but plug-ins have been greatly expanded to
include every target type being managed. As such, there is now an Oracle database plug-in to manage Oracle databases,
a Fusion Middleware plug-in to manage Oracle's middleware, a Fusion Application plug-in to manage Oracle's Fusion
Applications product suite, and so on. Because new releases of the Oracle software will include plug-ins used to
manage that software, this means EM12c (and later releases) will be able to monitor and manage those releases much
more quickly than has been the case in the past. Plug-ins can be downloaded, applied, and deployed using the new
Self Update functionality available from the Cloud Control console (if you have sufficient privileges to use it).
In addition, this modular plug-in architecture means that an agent is no longer configured to be able to monitor
any target type. Now, an agent will download only the plug-ins that are needed for the targets that the agent is
monitoring. This means the agents themselves are smaller than they were in previous releases. This change is one of
the biggest improvements in the architecture of the EM12c release.
A High-Availability EM12c Configuration
In the most basic of EM12c installations, the OMS and the repository can be physically located on a single machine.
However, Oracle recommends placing these two components on different machines. Figure
1-3
shows the simplest
installation.
Target with
OMA / plug-in
Target with
OMA / plug-in
OMS
Cloud Control
Console
Repository
Figure 1-3.
Basic EM12c architecture
