When you size the Oracle Enterprise manager management Service (OMS), what are the three
key criteria that you need to keep in mind?
A.
Amount of jobs to dispatch
B.
Volume of notifications to send out
C.
Number of agents (including state and metric data) uploading information
D.
Volume of deployment procedures
E.
Amount of history kept in the repository
Explanation:
Oracle Management Service is a Web-based application that orchestrates with the
Management Agents and the Management Plug-ins to discover targets, monitor and manage
those targets, and store the collected information in a repository for future reference and analysis.
Oracle Management Service also renders the user interface for Enterprise Manager Cloud
Control. Oracle Management Services is deployed to the Oracle middleware home (middleware
home), which is the parent directory that contains the Oracle WebLogic Server home, the Oracle
Management Service home, the Management Agent home, the plug-in home, the Java
Development Kit (JDK), the Oracle Management Service instance base directory, the Oracle Web
tier directory, the Oracle common directory, and other relevant configuration files and directories.
While deploying the Oracle Management Service, the Enterprise Manager Cloud Control
Installation Wizard installs Oracle WebLogic Server if it does not already exist in your environment.
As a result, an Oracle WebLogic Server administration console is also installed.
Reference: OracleEnterprise Manager Cloud Control Introduction
I doubt on B. Any explanation?
Not B. Should be A.
Sizing Your Enterprise Manager Deployment
Additional Configurations
– Large Concurrent UI Load
– Large Job System Load ——> A
– Large Repository Side Available Load (Release 12.1.0.3 and above)
– Large Number of Agents (Release 12.1.0.3) ———-> C
– Changing OMS Properties
– Modifying Database Settings ————-> E
– BI Publisher Configuration
http://docs.oracle.com/cd/E24628_01/install.121/e24089/toc.htm
ACE