ENTERPRISE MANAGER 12C

ARCHITECTURE

Cloud Control console

Oracle Management Agent

Oracle Management Service

Oracle Management Repository

Plug-ins
 CLOUD CONTROL CONSOLE
The user interface that you use to access, monitor, and
administer your computing environment.

Accessed via a web browser-access the central console from

any location.

customize the EM12c console:

Choosing your home page
Moving regions around on a target home page
Adding regions than the defaults
Deleting regions
 ORACLE MANAGEMENT AGENTS

An agent is generally installed on each host that is monitored .

The agents are deployed from the console and then monitor all the targets
that have been discovered by the agents.

Used to control blackouts on those targets, execute jobs, collect metrics

Provide details such as availability, metrics, and job statuses back to the
oracle management service.

Downside : Backward compatibility

EM12c agent to talk to the EM12c oracle management service.
 ORACLE MANAGEMENT SERVICE
The OMS is a web-based application that communicates with the
agents and the OMR to collect and store information about all the
targets on the various agents.
The information itself is stored in the OMR not in the OMS.
The OMS is also responsible for rendering the user interface for the
console.
The OMS is installed into an oracle middleware home,
oracle weblogic server (including the weblogic server administration console),
an oracle management agent for the middleware tier,
the management service instance base directory,
the java development kit (jdk), and other configuration files.
 ORACLE MANAGEMENT REPOSITORY
Oracle database that stores all the information collected by the
various management agents.

It is composed of database users, tablespaces, tables, views, indexes,

packages, procedures, and database jobs.

the installation process for the OMR requires that a database already
exists for the repository.

need to have created the database somewhere in your environment

prior to installing the OMS.

Again, it is typically recommended for the repository to be created

in a dedicated database.
 PLUG INS
Earlier releases-monitor and manage non-oracle (heterogeneous)
software including databases and middleware.
Partners or oracle corporation itself usually built them. There
werent many plug-ins overall.
In EM12C, a few of these monitoring plug-ins remain, but plug-ins
have been greatly expanded to include every target type being
managed.
Oracle database plug-in -oracle databases,
A fusion middleware plug-in -oracles middleware ...
Can be downloaded, applied, and deployed using the new self
update functionality available from the cloud control console
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.
COMMUNICATION FLOW
 COMMAND-LINE TOOLS
Enterprise Manager Command Line Interface (EMCLI):

largely used for scripting operations that might need to be

repeated.
can be installed on any computer (not necessarily the OMS or
OMR) simply by downloading the tool via the Cloud Control
setup menu.
Cant perform all the operations that are performed through GUI

Enterprise Manager Control (EMCTL):

starting, stopping, and checking the status of the OMS, agent,

and Cloud Control itself.
To secure/unsecure agents and the OMS
starting and stopping blackouts and other operations.
 Repository Users
In terms of database users, the SYSMAN user. It is basically the
owner of the database schema containing the repository.
Apart from the SYSMAN account, other database users are created
in the repository during repository creation or upgrade.

CLOUD_ENGINE_USERand CLOUD_SWLIB_USER are used

to perform cloud operations.
MGMT_VIEW is used for report generation
SYSMAN_APM, SYSMAN_MDS, and SYSMAN_OPSS are
metadata schemas for Fusion Middleware components.
SYSMAN_BIP is used for Business Intelligence (BI) Publisher
integration.
SYSMAN_RO is a general-purpose, read-only user
 LOG AND TRACE FILES
AGENT LOG AND TRACE FILES

When an agent is started, it also starts a watchdog which will monitor the
agent and attempt to restart it if it fails.
OMS DIRECTORY STRUCTURE
OMS DIRECTORIES AND USES
 OMS LOG AND TRACE FILES
6main log and trace files for troubleshooting issues with the OMS.
These are located under the OMS instance base directory gc_instin
emctl.log contains output from emctlcommands.
emctl.msg is generated when the OMS restarts because of critical
errors.
emoms.log the log file for the console, contains information created
when the OMS performs an action (such as starting or stopping) or
generates an error.
emoms.trc contains more-detailed tracing information to support
troubleshooting errors.
emoms_pbs.log contains errors or warnings for background
modules such as the event and job systems.
emoms_pbs.trc contains more-detailed tracing information to
troubleshoot problems with background modules.
 TROUBLESHOOTING
EMDIAG- Utility for troubleshooting all 3 layers of stack
AGTVFY - for the agent tier
OMSVFY - for OMS tier
REPVFY for Repository tier
They can even be used when the tier itself is not running (or indeed when it is
broken).
When you run these commands, you can pass a level from 0 to 9
Start with the lowest value (0), fix issues that are reported from that command,
and then run it again at the next highest level
Levels from 0 to 4 report functional issues,
Levels 6 to 8 are reporting issues,
Level 9 is for internal diagnostics and should be run under oracle support guidance
$ ./agtvfy verify all -level 2 details
$ ./repvfy verify all -level 2 details