• Find us:
    +1-669-900-5138   |   +44-203-372-5553
  • Free Newsletter

    Get Latest Updates

  • Make Training Enquiry


  • Categories

  • Archive

  • Oracle Enterprise Manager (OEM) – Basics

    Posted by "" in "oem" on 2009-06-18

    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.trcemagentfetchlet.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)


    5 Responses to “Oracle Enterprise Manager (OEM) – Basics”

    1. […] What is OEM Grid Control Management Agent ? Management Agent is software installed on node (machine) which you are planning to monitor. Agent collects information on target node (Host, Database, Listener, Application Server …) and transports that information to Oracle Management Service(OMS) which inturn pass on that information to Management Repository (Oracle Database). For overview of OEM Grid Control and various components Click Here […]

    2. […] This post covers installation of Oracle Application Management Pack (AMP) on existing Oracle Enterprise Manager Grid Control Component (Oracle Management Service & Oracle Management Agent) . To know more about OEM Grid Control components click here […]

    3. […] Oracle Enterprise Manager (OEM) Grid Control Installation & Startup overview Posted in January 6th, 2010 byAtul Kumar in installation, oem  Print This Post This post covers installation overview of Oracle Enterprise Manager Grid Control 10g R5 and start/stop of OEM Grid Control components (OEM Repository, Management Server and Agents) If you are new to Oracle Enterprise Manager (OEM) then go through OEM Architecture here […]

    4. arvind says:

      We’re having issues on OEM grid as usually we get the shared_pool issue. SGA is 3 gigs and grid is monitoring only 12 servers.

      I believe there is certain memory leakage. Could you please guide me on this.

    5. Michael says:

      Hi working with enterprise manager 11g wanted to know if i can have the 3 separate OMS servers or EM servers clustered? I can’t find in the documentation how to accomplish this

    Leave a Reply

  • K21 Technologies is among the most experienced Oracle Gold Partner for Identity Access Management service providers. We work with application development companies and in-house technology division to help achieve significant returns on their IT security investment. Our clientele includes some of the globally renowned corporate, which speaks of our expertise in our field.

    We have the most talented and experienced team that can swiftly deploy security solutions even in complex IT ecosystem. Our clients highly appreciate our timely implementation, interactive training, on-demand support and community resources.

    K21 Technologies
    8 Magnolia Place, Harrow,
    London, HA2 6DS

    UK: +44(0)7476444481
    USA: +1-888-414-1821

  • 2014, K21 Technologies. All rights reserved DMCA.com
  • TOP