Oracle Enterprise Manager (OEM) Grid Control is monitoring software for Oracle Database, Fusion MiddleWare (FMW including OAS & SOA Suite), Oracle E-Business Suite, Siebel, SAP ….
This post covers overview of various components in OEM Grid Control
Oracle Enterprise Manager (OEM) / Grid Control Component
1. Oracle Management Agent: is software that sits on all nodes(machines) which you would like to monitor. Configuration file for Management Agent is $OH/ <hostname>_<sid>/ sysman/ config/ emd.properties. Agent uploads managed data (from server its monitoring) to Management Service via HTTP Server (URL of management Service HTTP Server is defined by REPOSITORY_URL parameter in emd.properties)
Management Agent software also includes inbuilt HTTP Listener (different from standalone HTTP Server) to accept messages(data) from Management Service and this URL is defined by parameter EMD_URL in emd.properties.
Management Agent Log & Trace files are in $AGENT_HOME (or $OH/ <hostname>_<sid>) / sysman/ emagent.log, emagent.trc, emagentfetchlet.log, emagentfetchlet.trc , emagent.nohup
2. Oracle Management Service : Management Service upload data (from Management Agent via HTTP Server) to Management Repository (sysman schema in oracle database) using JDBC. Configuration file for Management Service is $OH/<hostname>_<sid>/ sysman/ config/ emoms.properties.
Repository connection details are defined by parameter emdRepSID, emdRepServer, emdRepConnectDescriptor and emdRepUser in emoms.properties
Management Service also monitors Management Agent (to check its up and running), submit enterprise manager jobs and other functions using EMD_URL (Management Agent runs inbuilt HTTP listener) defined in emoms.properties
Management Service Log & Tracefiles are in $AS_HOME (or $OH/ <hostname>_<sid>) / sysman/ emoms.log, emoms.trc
3. Oracle Management Repository : is Database Schema (sysman) to store Enterprise Manager Data. Management Service connects to Management Repository using JDBC
4. Oracle Enterprise Manager (OEM) Grid Control Console: is browser based tool to monitor and manage targets. Administrator uses console (URL on browser using webcache post of Grid Control Server) which connects to Webcache Port of OEM Grid Console.
Webcache in turn forward request to HTTP server of OEM Grid Middle Tier. HTTP Server retrieve data from Management Repository via Management Service.
5. HTTP Server: recieve requests from webcache, pulls data from Repository via Management Serviceand return response back to Webcache. HTTP Server also receive data from Management Agents, forward it to Management Service to store them in Management Repository.
6. Webcache : acts as web accelerator; forward request from Users (console) to HTTP Server and response back from HTTP server to Users (Console)
Communication between Management Agent & Service
Management Agent connect to Management Service via HTTP Server of Grid Control Middleware where as Management Service connect directly (using HTTP protocol) to Management Agent (Agent software include inbuilt http server)
Related Posts for OEM
- Oracle Enterprise Manager (OEM) – Basics
- Enterprise Manager – iAS Console : Changes in 10.1.3
- OEM DBConsole startup issues on 10g R2 database for 11i/R12
- Installing Oracle Enterprise Manager (OEM) Grid – Management Agent
- Install Application (11i/R12) Management Pack 3.0 with OEM Grid Control
- Oracle Enterprise Manager (OEM) Grid Control 10.2.0.1 Installation & Startup overview
- Book Review : Middleware Management with Oracle Enterprise Manager Grid Control
- Join Oracle Enterprise Manager 11g (Grid Control) Launch Live/New York on April 22, 2010
- Oracle Enterprise Manager (OEM) Grid Control 11g is now available to download
- Oracle Enterprise Manager (OEM) 12C (22.214.171.124 Cloud) #em12c : Overview and Installation
- Install Oracle Enterprise Manager (OEM) 12c : 126.96.36.199 #em12c
- OEM 12c to Monitor Identity and Access Management : You are not yet licensed to use the Management Pack Plus for Identity Management
- OID/OVD WebLogic 11g monitoring using OEM 12c (188.8.131.52) : High Level Steps
- Step by Step instruction to configure Identity Management Monitoring (OID/OVD) using OEM 12c
- Managing Oracle Fusion Middleware using OEM12c : Lessons Learned
- OEM 12c : How to Monitor Service Listening on Port on Host using Service / Beacon : Step by Step
- Troubleshoot : Oracle HTTP Server (OHS) marked down in #OEM12c or Fusion Middleware Control
- OEM 12c Integration with Fusion Middleware WebLogic : Compliance Score xx% is below critical threshold : Troubleshooting