Cloud Control Components


Cloud Control core components:
·         OMR:  Oracle Management Repository
·         OMS:  Oracle Management Services
·         OMA/Agent:  Oracle Management Agent with Plug-ins
·         GUI interface / Cloud Control and EMCLI command line interface

Definition:

Target:  is any software or system for which there is a plug-in.  Each agent plug-in is specific to a particular target type and offers special management capabilities to suite that target type

Target Type:  managed by cloud control includes Exadata, Exadata Logic, Oracle database, listener, fusion middle ware, Oracle application server web logic, PeopleSoft, E-Business Suite, SOA, and third party products.

Communication between the core components:
Agent -->uploads data àthe OMS via http/4889 or https/4900.
OMSàcommunicates with the Agent via http or https on port 3872
OMS àcommunicate with OMR via JDBC on port 1521.  OMS and OMR should have good bandwidth and low-latency connection

OMAs or Agents: Java applications are installed on their own ORACLE_HOME.  They run on hosts and gather metrics data about the monitored hosts.  They communicate via HTTP or secured HTTPS traffic with OMS to upload metric data. As Administrator, you can use Plug-in or initiate a discovery or configure Auto Discovery to promote the discovered target and managed targets.

Plug-in:  Have both the agent-side and OMS-side components.  It’s installed by default and gathers configuration, monitor availablity and performance

OMS:  Is J2EE application deployed on Oracle Web Logic Server.    You can push the agent to any host that can access across the network using a secure SSH connection. 

OMR:  Is in Oracle database.  It includes about 4000 schemas objects belonging to the sysman user.  It can be installed in an existing database or in RAC database for HA requirements.

Auto Discovery of Targets:  Agent-based (needs host name(s) and Agent-less (IP scan over the network

No comments:

Post a Comment