Oracle Enterprise Manager 12c Architecture, System Design and Sizing
Engage the Author Roddy Rodstein Today for your Oracle Project!
Copyright © 2012 Mokum Solutions, Inc. All rights reserved.
Distribution of the Oracle Cloud Cookbook or derivative of the work in any form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
Author: Roddy Rodstein
Table of Contents
Oracle Enterprise Manager 12c Cloud Control is Oracle's private and/or public cloud systems management solution for the entire Oracle stack. Oracle Enterprise Manager 12c is a systems management framework with product specific plug-ins for Oracle and non-Oracle technologies. Systems are managed and monitored from a Web GUI named Oracle Enterprise Manager 12c Cloud Control.
Firgue 1 shows Oracle Enterprise Manager 12c Cloud Control.
Oracle Enterprise Manager 12c is a systems monitoring and administration framework consisting of an Oracle database, Oracle WebLogic, a J2EE application, an application development frame work 11g (ADF) administrative Web GUI, server and client side plug-ins, and a client side agent. In the context of Oracle Enterprise Manager, the Oracle database repository is named the “Oracle Management Repository” or “OMR”. WebLogic is the J2EE platform called the “Oracle Management Service” or “OMS”, that runs the Oracle Enterprise Manager 12c J2EE application. The administrative Web GUI is named Oracle Enterprise Manager Cloud Control. The client side agents are named the “Oracle Management Agents” or “OMA”. The server and client side plug-ins share a unique name for the managed product or technology. For example, the server and client plug-ins for Oracle VM 3.0 are named Oracle Virtualization. Monitored hosts are referred to as targets. All of the Oracle Enterprise Manager components are commonly referred to as Oracle Enterprise Manager (OEM) or Enterprise Manager (EM).
The Oracle Management Repository is a Standard Edition or Enterprise Edition Oracle 11g Database that stores all of the information collected by the Oracle Management Agents and Plug-ins. The Oracle Management Agent and plug-ins are software applications that runs on all monitored hosts facilitating a two-way communication between the hosts and the Oracle Management Service. The Oracle Management Service is deployed on a WebLogic server or a cluster of WebLogic servers in the Oracle Middleware home. The Oracle Middleware home is the parent directory of the Oracle WebLogic Server home. The Oracle Management Service collects XML data from the Oracle Management Agents and plug-ins, and uploads the data into the Oracle Management Repository. The Oracle Management Repository formats the data and the Oracle Management Service visualizes the data in Oracle Enterprise Manager 12c Cloud Control. Administrative operations made using Oracle Enterprise Manager 12c Cloud Control are dispatched to targets from the Oracle Management Service. Oracle Enterprise Manager Cloud Control can be access using Firefox, Safari, Chrome and Internet Explorer on Linux, MAC, Unix and Windows workstations.
The Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a single host in an all-in-one configuration for evaluations or in an n-tier configuration for production. Traditionally, production Oracle Enterprise Manager environments are not be placed on a single server, nor should the Oracle Management Repository be shared with production or test databases on the same server.
Figure 2 shows a traditional multiple node Oracle Enterprise Manager 12c installation with the Oracle Management Repository hosted on a two-node RAC cluster, the Oracle Management Service hosted on a two-node WebLogic cluster with three monitored Oracle Linux hosts with the Oracle Management Agent.
Figure 2
Each of the Oracle Enterprise Manager components can be installed using the Oracle Universal Installer (OUI) GUI, or using silent installation scripts, or with the software only, configure later installation mode. The software only installation mode allows you to install only the Oracle Enterprise Manager software binaries without any configurations. The software only installation mode is ideal if you want to install the software at one point and configure the software later.
Oracle Enterprise Manager 12c Could Control, the Oracle Management Repository, the Oracle Management Service and the Oracle Management Agents and Plug-ins can be on different hosts throughout your enterprise. Understanding Oracle Enterprise Manager's intra component communication and data exchange will help you configure your firewalls in order to allow Oracle Enterprise Manager to operate in your enterprise. During the Oracle Enterprise Manager installation, the default communication ports for each component will be selected and assigned. If the default ports are modified be sure to use the new port assignments when you configure your firewalls.
Table 1 shows the default ports used by Oracle Enterprise Manager.
|
Service
|
Default Port
|
|
Enterprise Manager Upload HTTP Port
|
4889 - 4898
|
|
Enterprise Manager Upload HTTPS (SSL) Port
|
1159, 4899 - 4908
|
|
Management Agent Port
|
3872
|
|
Management Repository Database Port
|
1521
|
|
Cloud Control Console HTTP Port
|
7788 - 7798
|
|
Cloud Control Console HTTPS (SSL) Port
|
7799 -7809
|
|
EM Domain WebLogic Admin Server HTTP Port
|
7001
|
|
EM Domain WebLogic Admin Server HTTPS (SSL) Port
|
7101 - 7200
|
|
Cloud Control Managed Server HTTP Port
|
7201 - 7300
|
|
Cloud Control Managed Server HTTPS (SSL) Port
|
7301 - 7400
|
|
WebLogic Node Manager HTTPS (SSL) Port
|
7401 - 7500
|
|
JVM Diagnostics Managed Server
|
3800
|
|
JVM Diagnostics Managed Server (SSL)
|
3801
|
|
Application Dependency and Performance RMI Registry Port
|
51099
|
|
Application Dependency and Performance Java Provider Port
|
5503
|
|
Application Dependency and Performance Remote Service Controller Port
|
55000
|
Oracle Enterprise Manager 12c server sizing is calculated by a) total number of managed agents and targets, b) the future growth of your Oracle Enterprise Manager environment and c) your organization's high availability requirements. For example, if you know the total number of managed agents and targets, sizing WebLogic and the Oracle database is as simple as following Table 2, Table 3 and Table 4. As you add more agents and targets, it is important to consider the future growth of your Oracle Enterprise Manager environment as well as the ability to scale up or to scale out with additional CPU, RAM and storage.
Table 2 shows the minimum physical memory and storage requirements for the WebLogic server hosting the Oracle Management Service and the Oracle Management Agent.
|
Installation Type
|
Physical Memory (RAM)
|
Storage
|
|
Oracle Management Service
|
*6 GB
|
10 GB
|
|
Oracle Management Agent
|
* To use BI Publisher add 1.5 GB of RAM.
Table 3 shows the recommended Oracle Management Service minimum RAM and CPU cores requirements for WebLogic along with the recommended number of WebLogic hosts for a small, medium and large number of agents and targets.
|
Deployment Size
|
RAM
|
Intel or AMD
CPU Cores
|
Hosts
|
|
Small < 100 agents < 1000 targets
|
*6 GB
|
2
|
1
|
|
Medium < 1000 agents < 10,000 targets
|
*6 GB
|
4
|
1
|
|
Large > 1000 agents > 10,000 targets
|
*6 GB
|
4
|
2
|
* To use BI Publisher add 1.5 GB of RAM.
Table 4 shows the minimum RAM, CPU cores, storage and the number of hosts for the database server hosting the Oracle Management Repository..
|
Deployment Size
|
RAM
|
Intel or AMD CPU Cores
|
Storage
|
Hosts
|
|
Small < 100 agents < 1000 targets
|
2 GB
|
2
|
62 GB
|
1
|
|
Medium < 1000 agents < 10,000 targets
|
4 GB
|
4
|
225 GB
|
1
|
|
Large > 1000 agents > 10,000 targets
|
6 GB
|
4
|
345 GB
|
2
|
Table 5 shows the minimum storage requirements for a standalone Oracle Management Agent installation.
|
Platform
|
Storage
|
TMP Directory
|
|
Linux 32 bit
|
1.2 GB
|
400 MB
|
|
Linux x86_64
|
1.2 GB
|
400 MB
|
The Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a single host in an all-in-one configuration for evaluations or in an n-tier configuration for production. Traditionally, production Oracle Enterprise Manager environments are not be placed on a single server, nor should the Oracle Management Repository be shared with production or test databases on the same server. For production, the Oracle Management Repository as well as WebLogic should be on dedicated virtual or physical servers. If your Oracle Enterprise Manager environment starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager infrastructure.
For the Oracle Management Repository, scaling out means moving to RAC for the Oracle Management Repository database. An important consideration when scaling out an Oracle Enterprise Manager environment, is to determine if the underlying hardware where the Oracle Management Repository database runs is capable to transition to RAC? If the hardware is not capable to transition to RAC, it is possible to move and/or export the Oracle Management Repository database to a different system with more resources. If the Oracle Management Repository is hosted on an Oracle VM virtual machine, transitioning to RAC is a trivial operation.
Scaling out the WebLogic and Oracle Management Service tier entails adding a load balancing (SLB) solution to front end multiple WebLogic servers hosting the Oracle Management Service. Adding a load balancer with additional WebLogic servers introduces a virtual host name for the WebLogic cluster. Introducing a virtual host name into an existing Oracle Enterprise Manager environment will require a reconfiguration of all of your Oracle Management Agents to resolve to the new virtual host name. Reconfiguring a couple Oracle Management Agents is no trouble, although reconfiguring a lot of Oracle Management Agents would demand a long service window. When you deploy Oracle Enterprise Manager, consider using a virtual host name for the web tier.
An additional consideration when scaling out the WebLogic and Oracle Management Service tier is to provision shared storage to hosts the XML files and the software library.
