iSelfSchooling.com  Since 1999     References  |  Search more  | Oracle Syntax  | Free Online Oracle Problem Solver

    .Home      .Subscribe     .Login      .Start Learning      .Certification      .Cancel      .Password Reminder      .Password Change     .Sign out

 

. Online Accounting        .Copyright & User Agreement   |
    .Vision      .Biography     .Acknowledgement

.Contact Us      .Comments/Suggestions       .Email2aFriend    |

 

Oracle 11g New Features

Online Oracle Training

 

Oracle 11g: Grid Control 



Grid Control Components - Important notes to remember


The following are the Oracle Enterprise manager Grid Control components:


1-       Oracle Management Repository (OMR): It is a container. It is a collection of schema objects within an Oracle database. It contains SYSMAN's schema objects. The OMR database listener monitors port 1521 by default for any incoming connection requests.


2-       Oracle Management Service (OMS): It receives information from OMA and passes them to OMR. It provides the Grid Control console Web pages from information within the OMR. It includes Oracle HTTP Server (OHS), Oracle Application Server containers for J2EE (OC4J), and OracleAS Web Cache. OracleAS Web Cache is configured to listen on port 7777 and OHS listens on port 7778 for connection by default.


3-       Oracle Management Agent (OMA): You need one OMA for each host server. It must be in its own ORACLE_HOME.  It collects information about target availability, configuration, and performance and passes that information to OMS. In most installation, the OHS listens to OMA traffic on port 4889 by default.
  
To access the Grid Control console
You use the following URL from Web browser.

(http://<oms host>.<domain>:<port>/em)

For example:

http://oracle.iselfschooling.com:7777/em.
  
Grid Control Console components
1.   Home: It shows a big picture of system availability, alerts, jobs, and status of targets. 
2.   Targets: It shows the status of targets such as hosts, databases, applications servers, Web applications, groups, and a global view called all targets.
3.   Deployments: It shows the software and hardware deployments including their patches. It manages configuration policies to ensure that you comply with generally accepted best practices. 
4.   Alerts: It shows and monitors the status of targets. 
5.   Jobs: It shows, schedules and executes user's or administrator's jobs. 
6.   Management System: It shows an overview of performance of your ecosystem. 

 

 

Good Luck!

 

Google
 
Web web site