1 Pre-Installation Requirements

This chapter introduces you to Enterprise Manager and its components, and provides pre-installation requirements and certifications. This chapter also lists all targets that Enterprise Manager is certified to manage.

Oracle recommends reading this chapter before proceeding with your installation so that you will have a better understanding of the requirements and certifications for the Enterprise Manager installation environment.

The following topics are covered in this chapter:

Planning Your Installation
Enterprise Manager Components Overview
Pre-Installation Considerations for Enterprise Manager
Pre-Installation Requirements for Enterprise Manager
Running the Prerequisite Checker in Standalone Mode

Note:

Ensure you also read the Enterprise Manager Grid Control Release Notes that accompany the product.

Planning Your Installation

The following sections will give you a better understanding of the Oracle Enterprise Manager Grid Control installation process and facilitate a successful installation.

Enterprise Manager Components Overview: The Enterprise Manager Components Overview section in this chapter briefly describes each Enterprise Manager component.
Pre-Installation Considerations for Enterprise Manager: This section provides information on the pre-installation requirements that facilitate successful installation of Enterprise Manager. You must ensure these requirements are met before starting the Enterprise Manager installation.
Installing Enterprise Manager: This chapter provides detailed information on how to use the Oracle Universal Installer to install Enterprise Manager.
Deploying the Management Agent: This chapter provides information on the various methods of mass-deploying the Management Agent.
Post-Installation Configuration Tasks: This chapter describes the tasks that need to be completed after the installation.

Enterprise Manager Components Overview

Enterprise Manager is Oracle's single, integrated solution for administering and monitoring targets that are based on the Oracle technology stack. See Chapter1, "Certified Enterprise Manager Targets" for a list of Oracle targets and components that Enterprise Manager can manage.

Oracle Enterprise Manager includes the Oracle Management Agent, Oracle Management Service, and Oracle Management Repository Database, as well as the Grid Control Console, which is a browser-based central console through which administrators can perform all monitoring, administration, and configuration tasks for the enterprise.

Table 1-1 explains the different Enterprise Manager components and how they work together to manage your enterprise.

Table 1-1 Enterprise Manager Grid Control Components

Component	Definition
Grid Control Console	From the Grid Control console, you can monitor and administer your entire computing environment from one location on the network. All the services within your enterprise, including hosts, databases, listeners, application servers, Collaboration Suite applications, and Web applications are easily managed from one central location (console).
Management Agent	The Oracle Management Agent is a process that is deployed on each monitored host. It is responsible for monitoring all targets on the host, for communicating that information to the middle-tier Management Service, and for managing and maintaining the host and its targets.
Management Service	The Oracle Management Service is a J2EE Web application that renders the user interface for the Grid Control console. It works with all Management Agents to process monitoring and Jobs information, and uses the Management Repository as its data store.
Management Repository	The Oracle Management Repository consists of objects such as RDBMS jobs, packages, procedures, views, and two tablespaces in an Oracle Database that contain all available information about administrators, targets, and applications managed within Enterprise Manager. The Management Service uploads the monitoring data it receives from the Management Agents to the Management Repository. The Management Repository then organizes the data so that it can be retrieved by the Management Service and displayed in the Grid Control console. Because data is stored in the Management Repository, it can be shared between any number of administrators accessing the Grid Control console.

Enterprise Manager - Topology

Figure 1-1 Typical Enterprise Manager Topology

Pre-Installation Considerations for Enterprise Manager

This section provides information about the Oracle Universal Installer and other concepts you should be aware of when you plan the installation.

Licensing Information
Oracle Directory
Multiple Oracle Home Support

Licensing Information

Although the installation media in your media pack contain many Oracle components, you are permitted to use only those components for which you have purchased licenses. Oracle Support Services does not provide support for components for which licenses have not been purchased.

Oracle Directory

If you choose to install Enterprise Manager Grid Control using a new database on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, then one or more Oracle base directories already exist. In the latter case, Oracle Universal Installer offers you a choice of Oracle base directories into which to install Oracle Database.

You are not required to create an Oracle base directory before installation, but you can do so if desired. You can set the ORACLE_BASE environment directory to point to this directory, which the Oracle Universal Installer will recognize.

Note:

You can choose to create a new Oracle base directory, even if other Oracle base directories exist on that system.

Multiple Oracle Home Support

Enterprise Manager is installed on multiple Oracle homes. This means that a typical Enterprise Manager Grid Control installation creates three Oracle homes in different Oracle home directories. For example, oms10g, db10g, and agent10g.

Note:

You must ensure that you install this product into a new Oracle home directory. You cannot install products from one release of Enterprise Manager into an Oracle home directory of a different release. For example, you cannot install 10g R2 (10.2) software into an existing Oracle 9i home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation will fail.

You can install this release more than once on the same system, as long as each installation is done in a separate Oracle home directory.

Pre-Installation Requirements for Enterprise Manager

This section provides information about the minimum hardware and software requirements for Enterprise Manager components:

Enterprise Manager Hardware Requirements
Enterprise Manager Software Requirements

Enterprise Manager Hardware Requirements

This section lists the hardware requirements for various Enterprise Manager deployment sizes.

Recommended CPU and Memory Allocation for Enterprise Manager Deployments

Table 1–2 and Table 1–3 approximate the host, CPU, and physical memory requirements for a first-time Enterprise Manager installation (typical scenario with 2 - 3 GHz machines), based on experiences with real-world Enterprise Manager deployments.

CPU and Memory allocation for Oracle Management Service (OMS)

Table 1-2 CPU and Memory Allocation for Oracle Management Service

Deployment Size	Host	CPU/Host	Physical Memory/Host	Total Recommended Space
Small (100 monitored targets)	1	1 (3 GHz)	2 GB	2 GB
Medium (1,000 monitored targets)	1	2 (3 GHz)	2 GB	Number of OMS x 5 GB
Large (10,000 monitored targets)	1	2 (3 GHz)	2 GB	Number of OMS x 10 GB

CPU and Memory Allocation for the Repository Database

Table 1-3 CPU and Memory Allocation for Repository Database

Deployment Size	Host	CPU/Host	Physical Memory/Host	Total Repository Storage
Small (100 monitored targets)	1^Foot 1	1 (3 GHz)	2 GB	10 GB
Medium (1,000 monitored targets)	1	2 (3 GHz)	4 GB	30 GB
Large (10,000 monitored targets)	2	4 (3 GHz)	6 GB	100 GB

^Footnote 1Share Host with the Oracle Management Service for small deployments.

ATTENTION:

Oracle recommends that you allocate a minimum default size of 1 GB hard disk space for the MGMT_ECM_DEPOT_TS tablespace and allocate the rest of the recommended repository database space for the MGMT_TABLESPACE.

Oracle also recommends that you keep the auto-extend feature enabled for the tablespace datafiles.

Note that the space requirement increases as the number of monitored targets increase, along with the input/output performance demands on the storage devices.

Considering Resource Allocation

Carefully consider resource allocation when choosing the disk on which to install the Management Service and Management Repository database. Enterprise Manager's out-of-box monitoring starts generating information upon installation, meaning that resource consumption begins immediately. As such, consider the base system resource consumption prior to installing. Select your installation locations strategically, taking into account system load, memory usage, and disk input/output.

For example, you can split the input/output load across disks. Avoid installing the Management Repository database or the Management Service on the swap volume, a volume with a busy state (as per iostat) of 10% or more, or on a memory-constrained system. As with any data-intensive application, if your Management Repository is going to service a large number of targets, it is important to tune the database appropriately to maximize input/output capacity. Refer to the Database Performance Tuning Guide for more information.

While adding more resources can help alleviate potential problems (for instance, adding a second disk spindle dedicated to the Management Service on a system), understanding and accounting for resource allocation is the best way to achieve strategic setup and good performance.

Enterprise Manager Platform and Target Certification Requirements

This section contains certification information for each Enterprise Manager component, including the Management Repository, Management Service, and Management Agent. Browser certifications for the Grid Control console are also given.

Also included in this section are the certifications for all targets managed by Enterprise Manager:

Operating System Certifications
Browser Certifications for the Enterprise Manager Console
Certified Enterprise Manager Targets

Operating System Certifications

The operating system platforms certified for Enterprise Manager Grid Control components are the following:

Red hat Enterprise Linux 3.0
Red hat Enterprise Linux 4.0
SUSE Linux Enterprise Server 9.0

Required Packages

The system must be running the following (or later) package versions:

For Red Hat Enterprise Linux 3.0:
- glibc-2.2.4-31.7
- make-3.79
- binutils-2.11.90.0.8-12
- gcc-2.96
- openmotif21-2.1.30-11

For Red Hat Enterprise Linux 4.0:
- glibc-2.3.4-2.9
- make-3.79
- binutils-2.15.92.0.2-13
- gcc-3.4.3-22.1
- libaio-0.3.96
- glibgc-common-2.3.4-2.9
- setarch-1.6-1
- pdksh-5.2.14-30
- openmotif21-2.1.30-11
- sysstat-5.0.5-1
- gnome-libs-1.4.1.2.90-44.1
- libstdc++-3.4.3-22.1
- libstdc++devel-3.4.3-22.1
- compat-libstdc++-296-2.96-132.7.2
- compat-db-4.1.25-9
- control-center-2.8.0-12
- xscreensaver-4.18-5.rhel4.2

For SUSE Linux Enterprise Server 9:
- glibc-2.2.4-31.7
- make-3.79
- binutils-2.11.90.0.8-12
- gcc-2.96
- openmotif21-2.1.30-11

Required Kernel Parameters

The system must have at least the following recommended kernel parameters:

Red Hat Enterprise Linux 3.0 and SUSE Linux Enterprise Server 9 require the following kernel parameters:
- semmsl = 250
- semmns = 32000
- semopm = 100
- semmni = 128
- shmmax = 2147483648
- shmmni = 4096
- shmall = 2097152
- shmmin = 1
- shmseg = 10
- filemax = 65536
Red Hat Enterprise Linux 4.0 requires the following kernel parameters:
- semmsl = 250
- semmsl2 = 250
- semmns = 32000
- semopm = 100
- semmni = 128
- shmmax = 536870912
- shmmni = 4096
- shmall = 2097152
- filemax = 65536
- ip_local_port_range = 1024 65000
- rmem_default = 262144
- rmem_max = 262144
- wmem_default = 262144
- wmem_max = 262144

To check your kernel parameter settings, run the commands listed in the following table.

Table 1-4 Execute Commands to Check Kernel parameter Settings

Parameter	Command
semmsl, semmns, semopm, semmni	`# /sbin/sysctl -a \| grep sem`^Foot 1
shmall, shmmax, shmmni	`# /sbin/sysctl -a \| grep shm`
file-max	`# /sbin/sysctl -a \| grep file-max`
ip_local_port_range	`# /sbin/sysctl -a \| grep ip_local_port_range`
rmem_default	`# /sbin/sysctl -a \| grep rmem_default`
rmem_max	`# /sbin/sysctl -a \| grep rmem_max`
wmem_default	`# /sbin/sysctl -a \| grep wmem_default`
wmem_max	`# /sbin/sysctl -a \| grep wmem_max`

^Footnote 1This command displays the value of the four semaphore parameters in the order listed.

To change your kernel parameter settings, use any text editor to create or edit the /etc/sysctl.conf file to add or modify the necessary entries. You may need to reboot your system after changing kernel parameters.

Note:

Include lines only for the kernel parameter values that you want to change. For the semaphore parameters (kernel.sem), you must specify all four values in order.

If the current value of any of your system's kernel parameters is higher than the recommended value, keep your current value.

For example, your /etc/sysctl.conf file may look like this:

kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
rmem_default = 262144
rmem_max = 262144
wmem_default = 262144
wmem_max = 262144

By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system.

On SUSE systems only, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:

# /sbin/chkconfig boot.sysctl on

Browser Certifications for the Enterprise Manager Console

Table 1-5 lists the browser versions that are certified for the Linux and Solaris operating systems for the Grid Control console.

Table 1-5 Browser Certifications for Grid Control

Operating System	Browser	Version
Linux	Mozilla Firefox	1.3.1 1.0.4
Solaris	Netscape Navigator	7.0.1, 7.1.0, 7.2

Operating System

Browser

Version

Linux

Mozilla

Firefox

1.3.1

1.0.4

Solaris

Netscape Navigator

7.0.1, 7.1.0, 7.2

Note:

For Services monitoring, you can record and play back Web application transactions using the Transaction Recorder. The Transaction Recorder is only supported on Microsoft Internet Explorer 5.5 (Service Pack 1) and higher and is not supported on other browsers. Alternatively, if you do not have this requirement, you can configure Web transaction steps manually. Refer to the Enterprise Manager online help for details on creating Web transactions for monitoring.

Certified Enterprise Manager Targets

Table 1-6 identifies the Oracle targets and components that Enterprise Manager Grid Control can manage.

Table 1-6 Certified Oracle Targets

Supported Targets	Version
Oracle Application Server	9.0.2.x^Foot 1 9.0.3.x 9.0.4.0 and higher patchsets 10.1.2.0.0 10.1.2.0.1 10.1.2.0.2 10.1.3
Oracle Database^Foot 2, Listener	8.1.7.4 9.0.1.5 and higher patchsets 9.2.0.6 and higher patchsets 10.1.0.4 and higher patchsets 10.2
Oracle Real Application Clusters Database	9.2.0.4 9.2.0.6 and higher patchsets 10.1.0.3 and higher patchsets 10.2
Oracle Collaboration Suite	Release 2 (9.0.4.2) 10.1.1
Management Services and Repository^Foot 3	10.2
Management Agent^Foot 4	10.1.0.2 and higher patchsets
Enterprise Manager Website	10.2
Host	All supported platforms. Oracle recommends that the target host on which you are installing the agent have a static IP address and not DHCP.

^Footnote 1For Application Server version 9.0.2.x, only the following components are supported: Oracle HTTP Server, OC4J, Web Cache, Oracle Internet Directory, and Single Sign-On.
^Footnote 2Enterprise Edition, Standard Edition, Personal Edition
^Footnote 3The Management Service and Repository versions correspond to the version of the Grid Control installation and not the version in which the repository is created.
^Footnote 4The Management Agent includes Beacon functionality.

Enterprise Manager Software Requirements

This section describes the software requirements for each Enterprise Manager component.

Management Repository Software Requirements

The embedded Oracle10g Database Release 1 (10.1.0.4), Enterprise Edition, is supported for Management Repository creation. Otherwise, you may only install the Management Repository in one of the following existing databases:

Oracle 10g Database Release 1 (10.1.0.3 and higher), Enterprise Edition
Oracle 10g Real Application Clusters Database Release 1 (10.1.0.3 and higher)
Oracle 9i Database Release 2 (9.2.0.6 and higher), Enterprise Edition
Oracle 9i Real Application Clusters Database Release 2 (9.2.0.6 and higher)

Note that the Enterprise Edition database you use for the Management Repository must have fine-grained access control turned on. When using an existing database for the repository, be sure that all software, patch, and tuning requirements are met for the existing database and host, as well as for the repository.

Management Service Software Requirements

The Management Service has no additional software requirements.

The Oracle Management Service is installed with and deployed on the Oracle Application Server. As a result, when you install the Oracle Management Service, the installation procedure first installs Oracle Application Server.

Specifically, the installation procedure installs the Oracle Application Server J2EE and Web Cache installation type. The Management Service is deployed on its own OC4J container in this application server instance.

Prerequisite Checks

The following table lists all the prerequisite checks that the installer performs for each installation type.

Table 1-7 Prerequisites Checks for Each Installation Type

Installation Type	Prerequisite	Checks
Installing Enterprise Manager Using New Database	oracle.sysman.top.em_seed	Required Packages on the machine Certified Versions (that is, whether the Oracle software is certified on the current Operating System) Whether the required GLIBC is installed on the machine Whether the machine has sufficient physical memory Kernel parameters Oracle home compatibility^Foot 1 Oracle home space check Checking host name Whether Oracle home is empty
Installing Enterprise Manager Using Existing Database	oracle.sysman.top.oms	Required Packages on the machine Certified Versions (that is, whether the Oracle software is certified on the current Operating System) Whether the required GLIBC is installed on the machine Whether the machine has sufficient physical memory Oracle home compatibility Whether Oracle home is empty Checking host name Oracle home space check
Installing Additional Management Service	oracle.sysman.top.oms	Required Packages on the machine Certified Versions (that is, whether the Oracle software is certified on the current Operating System) Whether the required GLIBC is installed on the machine Whether the machine has sufficient physical memory Oracle home compatibility Whether Oracle home is empty Oracle home space check Checking host name^Foot 2
Installing Additional Management Agent	oracle.top.agent	Required Packages on the machine Certified Versions (that is, whether the Oracle software is certified on the current Operating System) Whether the required GLIBC is installed on the machine The Targets monitored by the Agent Note that the Agent cannot monitor targets that have been installed by different users. Oracle home compatibility Checking host name Oracle home space check

^Footnote 1Disallowed component = oracle.rsf.oracore_rsf.
^Footnote 2The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP Address. It must be a valid host name.At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.

Running the Prerequisite Checker in Standalone Mode

You can run the prerequisite checker in standalone mode prior to starting the runInstaller. This helps you identify and resolve issues that might otherwise cause the installation to fail.

The following table lists the prerequisite checker that is run for each installation type followed by the command that you must execute to run these checks:

Table 1-8 Installation Type and the Corresponding Prerequisite Check

Installation Type	Prerequisite Check
Installing Enterprise Manager Using a New Database	oracle.sysman.top.em_seed
Installing Enterprise Manager Using an Existing Database	oracle.sysman.top.oms
Installing an Additional Management Service	oracle.sysman.top.oms
Installing an Additional Management Agent	oracle.sysman.top.agent

To run the prerequisite checker in standalone mode, execute the following command:

<DVD>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint <prerequisite check name>_Core -prereqLogLoc <log location>  -silent  -waitForCompletion

Substitute the data in <angled brackets> with the appropriate prerequisite check name. For example, if you want to run the prerequisite check for the first installation type, execute the following command:

<DVD>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint oracle.sysman.top.em_seed_Core -prereqLogLoc <log location>  -silent  -waitForCompletion