Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1)
Part No. B12012-03
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. The following topics are covered in this chapter:
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.
Make sure to read the Enterprise Manager Grid Control Release Notes that accompany the product. Particularly, the "Installation and Configuration" section will provide relevant and useful information.
Enterprise Manager is Oracle's single, integrated solution for administering and monitoring targets that are based on the Oracle technology stack. See "Certified Enterprise Manager Targets" for a list of Oracle targets and components that Enterprise Manager can manage.
Oracle Enterprise Manager Grid Control includes the Oracle Management Agent, Oracle Management Service, and Oracle Management Repository, as well as the Grid Control Console, a browser-based central console through which administrators can perform all monitoring, administration, and configuration tasks for the enterprise.
Table 1-1 explains what the different components are and how they work together to manage your enterprise.
Table 1-1 Enterprise Manager Grid Control Components
|Grid Control Console||The Enterprise Manager Web-based user interface for centrally managing your entire computing environment. The Grid Control Console is installed from a separate CD–ROM Pack that is shipped with the Oracle Database 10g Release 1 (10.1) CD–ROM Pack.
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 as one cohesive unit.
|Management Agent||The Oracle Management Agent, a process that is deployed on each monitored host, 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, works with all Management Agents to process monitoring and jobs information, and uses the Management Repository as its data store.
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 in this application server instance.
|Management Repository||The Oracle Management Repository consists of 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.
For information on tablespaces, refer to the "Managing Tablespaces" chapter of the Oracle Database Administrator's Guide.
For more information on these components, refer to Oracle Enterprise Manager Concepts.
Note:The Management Service is deployed on an Oracle Application Server instance that is installed as part of Enterprise Manager Grid Control. This application server instance is dedicated to the Management Service and should not be used for any other application deployments. As a result, you should not make any configuration changes to the application server instance.
This section provides information about the minimum hardware and software requirements for Enterprise Manager components:
Refer to Appendix A for patching information for all of Enterprise Manager's supported operating systems.
Table 1-2 describes the hardware requirements for each Enterprise Manager component.
Table 1-2 Hardware Requirements
|Component||Hard Disk Space Requirements||Operating Memory and CPU Requirements|
|Management Repository||Allocating 1 GB of hard disk space to the Management Repository should be sufficient for small environments with fewer than 25 managed targets. This requirement grows as the number of targets increases.
Make sure there is enough disk space available for these two initial tablespaces, or you will receive an error message.
|For a reasonably sized enterprise of around 500 targets, the minimum operating memory required for the repository node is 1 GB; the recommended size is 2 GB.
Performance increases as memory for the repository increases. With more memory, you can increase the
See Appendix B for recommended database initialization parameters.
|Management Service||At least 1.4 GB of initial disk space is required for Solaris; at least 500 MB for Windows.||For the host running the Management Service, the minimum memory recommended is 1 GB.
The minimum processor speed for the host is 1 GHz. For each additional Management Service, another 0.5 GHz is recommended.
|Management Agent||At least 350 MB of initial disk space is required for Solaris; at least 270 MB for Windows.
For logging, tracing, and temporarily stored data collections, allocate an additional 50 MB.
|The Management Agent requires approximately 20 MB of operating memory to monitor a database, and more to monitor an Application Server. This requirement increases as the number of targets monitored increases.
While resource consumption is minimal for Management Agents, enabling the Beacon capability increases requirements. For information on the Beacon capability, refer to the "About Beacons" and "Using Beacons to Monitor Web Application Availability" topics in the Enterprise Manager online help.
|Application Server CoreFoot 1||Approximately 500 MB of initial disk space is required.||For the host running the Application Server Core, the minimum memory recommended is 512 MB.|
Consider carefully 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 periostat) of 10% or more, or on a memory constrained system. As with any data intensive application, if your Management Repository will 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.
This section describes the software requirements for each Enterprise Manager component.
The embedded Oracle9i Database Release 1 (126.96.36.199), Enterprise Edition, is supported for Management Repository creation. Otherwise, you may only install the Management Repository into one of the following existing databases:
Oracle 10g Database Release 1 (10.1.0.3 or higher), Enterprise Edition
Oracle 10g Real Application Clusters Database Release 1 (10.1.0.3 or higher)
Oracle9i Database Release 2 (188.8.131.52 or higher), Enterprise Edition
Oracle9i Real Application Clusters Database Release 2 (184.108.40.206 or 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.
See Also:Refer to Appendix B for the recommended database initialization parameters.
To use the Oracle 10g Database Release 1 (10.1.0.3 or higher) for the Management Repository, the following requirements must be met:
The SYSMAN schema must not already exist. If it does exist, as it will when there is a seed database, you can drop the schema using RepManager before installation. For example:
OMS_HOME/sysman/admin/emdrep/bin/RepManager <host> <port> <sid> -action drop
Label Security must be installed.
The default system stats job must be disabled. As the SYS user, use the following query to check for this job:
SELECT STATE FROM DBA_SCHEDULER_JOBS WHERE JOB_NAME = 'GATHER_STATS_JOB';
If not disabled, use the following command to disable the job:
The Shared Pool Size must be at least 130MB. The pre-requisite checker determines this by querying the dynamic SGA components. For 10g databases, you do not have to set this value explicitly, but should make sure space is adequate.
Attention:If you want to create a Management Repository in an existing Oracle home directory, thick JDBC may be required in that home so that the LOADJAVA commands in the installation procedure can create the Management Repository.
Thick JDBC is not installed by default. To check for the "Oracle JDBC/OCI driver for JDK x.x" option, where x.x can take the values of 1.1, 1.2, 1.3, and 1.4, click Installed Components on the Oracle Universal Installer screen and explore the list of components.
The Management Service has no additional software requirements.
The Oracle Net files contain information about the databases and listeners running on the machine. Prior to the installation and starting of the Management Agent, if your Oracle Net files are in a non-standard location, you must set the
TNS_ADMIN environment variable to point to the directory with the valid files so that the targets on the machine can be added for monitoring and administration by Enterprise Manager.
Standard Oracle Net file locations are:
/var/opt/oracle/ for Solaris Operating System
/etc for HP-UX, HP Tru64, IBM AIX
All other Oracle Net file locations are non-standard.
Enterprise Manager's process for adding targets will use the directory in a standard location to obtain information about the Oracle Net configuration.
See Also:For more information about configuring Oracle Net, refer to the Oracle Net Services Administrator's Guide.
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.
Table 1-3 describes the operating system platforms certified for the Management Repository, Management Service, and Management Agent. Note the restrictions in the table footnotes.
Table 1-3 Certified Operating Systems for Enterprise Manager Components
|Operating SystemFoot 1||Version|
|Solaris Operating System (SPARC 32-bit, SPARC 64-bit)||8 and 9|
|HP-UX (64-bit)||PA-RISC 11iv1 (11.11)|
|HP-UX (64-bit)||Itanium 11iv2 (11.23)|
|IBM AIX (64-bit)||5.2|
|Red Hat Enterprise Linux ES/AS||2.1 and 3.0|
|Red Hat Enterprise Linux ES/AS||2.1 and 3.0 on ItaniumFoot 2|
|SuSE||SLES8 (Service Pack 3)|
|Microsoft Windows||NT 4.0 (Service Pack 6a)Foot 3|
|Microsoft Windows||2000 (Service Pack 4)|
|Microsoft Windows||XP (Professional Edition)|
|Microsoft Windows||2003 (Standard Edition)|
Note:Specific instructions for installing the Oracle Management Agent on the Windows platform are available on the Oracle Management Agent for Windows CD-ROM.
Table 1-4 lists the browser versions that are certified for the Solaris, Windows, and Linux operating systems for the Grid Control Console.
Table 1-4 Browser Certifications for Grid Control
|Solaris||Netscape Navigator||7.0.1, 7.1.0|
|Windows||Netscape NavigatorFoot 1
Microsoft Internet Explorer
|4.78, 4.79, 7.0.1, 7.1.0
5.5 (Service Pack 1); 6.0 (Service Pack 1)
|Microsoft Pocket PCFoot 2||Pocket Internet Explorer||2.0 (for HTTP), 3.0 (for HTTPS)|
Note:To record and play back Web application transactions using the Transaction Recorder, you must use Internet Explorer 5.5 (Service Pack 1) or higher. This feature is not supported on other browsers. Refer to Enterprise Manager online help for details on using Transaction Recorder.
Table 1-5 identifies the Oracle targets and components that Enterprise Manager Grid Control can manage.
Table 1-5 Certified Oracle Targets
|Supported Targets||VersionFoot 1|
|Oracle Application Server||9.0.2.xFoot 2
|Oracle DatabaseFoot 3 , Listener||220.127.116.11
18.104.22.168 and higher
22.214.171.124 and higher
10.1.0.2 and higher
|Oracle Real Application Clusters Database||126.96.36.199 and higher
10.1.0.2 and higher
|Oracle Collaboration Suite||Release 1Foot 4 (9.0.3.x)
Release 2Foot 5 (9.0.4.x)
|Management Services and Repository||10.1.0.3|
|Management AgentFoot 6||10.1.0.2 and higher|
|Enterprise Manager Website||10.1.0.3|
|Host||All supported platforms. See Table 1-3.|