Grid Control major components: OMA, OMS and OMR

Grid Control major components: OMA, OMS and OMR

The Grid Control framework schemdes:
 
● Oracle Management Repository (OMR)
● One or more Oracle Management Service (OMS)
● One or more Oracle Management Agent (OMA)
 
GC not only manages any mainstream Oracle products, but also detects custom (such as vrouters) targets.
 


OMAs collects target information (such as availability, configuration, and performance) and then transmits the information to OMS.
One OMA only talks to one OMS, but one OMS can serve multiple OMA
Then, OMS sends a copy of the received information to OMR.
One OMS only talks to one OMR, but one OMR can serve multiple OMS



(I) Oracle Management Agent
 
The OMA is responsible:
① All active monitoring
② Communication between Grid Control and all managed targets.
 
The OMA:
 
● Must be installed on each host server
 
A single management agent interfaces the OMS with all managed targets on the host server
 
● Must be in its own ORACLE_HOME
 
Management agents are installed in their own ORACLE_HOME, and
Controlled with the emctl utility
 
● Communicates with the OMS via HTTP or HTTPS



(Ii) Oracle Management Service
 
The OMS is responsible:
① Renders the user interface for Grid Control, works with all OMAs
② Stores persistent data in the OMR
 
The OMS:
 
● Receivdes member components:
I Oracle HTTP Server (OHS)
II Oracle Application Server Containers for J2EE (productname)
III OracleAS Web Cache
 
● Is a J2EE application deployed on Oracle Application Server 10 GB
 
● Connects to the OMR by using JDBC
 

You can connect to the GC via a Web browser through OHS and OracleAS Web Cache:
 
① OracleAS Web Cache is configured to listen for DBA's connections on port 7777
And pass the connection through to the OHS on port 7778
 
② OMAs connect to the application directly throughOHS, bypassing OracleAS Web Cache
In most installations, OHS listens for OMA traffic on port 4889.
 
(Iii) Oracle Management Repository
 
The OMR is responsible:
① Organizes the data processing ing from OMS so it can be retrieved by OMS and displayed on GC
 
The OMR:
 
● Resides in an Oracle database
● Includes schema objects belonging to SYSMAN
 
The OMR is installed in an Oracle database as a group of approximately 4,000 schema objects
These schema objects contain information about:
GC administrators, targets, and applications that are managed by GC
 
● Can be installed in a preexisting database
 
The OMR may be installed either in its own private database orin an existing database