Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1) Part No. B12012-01 |
|
![]() |
![]() |
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.
Enterprise Manager is Oracle's single, integrated solution for administering and monitoring targets that are based on the Oracle technology stack. See Table 1-6 for a list of Oracle targets and components that Enterprise Manager can manage.
Oracle Enterprise Manager Grid Control framework includes the Oracle Management Agent, Oracle Management Service, and Oracle Management Repository, as well as Grid Control, 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 Framework Components
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 to deploy other applications. 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 | Disk Space Requirements | Memory Requirements |
---|---|---|
Management Repository | Allocating 1 GB of 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.
The Management Repository is created within two tablespaces that initially require 120 MB of disk space: 20 MB for the MGMT_TABLESPACE tablespace and 100 MB for the MGMT_ECM_DEPOT_TS tablespace. 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 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 240 MB of initial disk space is required. | For the host running the Management Service, the minimum memory recommended is 1 GB. |
Management Agent | At least 310 MB of initial disk space is required.
For logging, tracing, and temporarily stored data collections, allocate an additional 50 MB. |
The Management Agent requires approximately 20 MB 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 Enterprise Manager framework 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 Enterprise Manager framework 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 memory can help alleviate potential resource problems (for instance, adding a second disk spindle dedicated to the Enterprise Manager framework on a system), understanding and accounting for resource allocation is the best way to achieve strategic setup and good performance.
Table 1-3 describes the software requirements for each Enterprise Manager component.
Table 1-3 Software Requirements
Component | Software Requirements |
---|---|
Management Repository | The embedded Oracle9i Database Release 1 (9.0.1.5), Enterprise Edition, is supported for Management Repository creation. Otherwise, you may only install the Management Repository into one of the following existing databases:
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 | No additional software requirements. |
Management Agent | 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.
For example: export TNS_ADMIN=$HOME/mydir/network Standard Oracle Net file locations are:
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. For more information about configuring Oracle Net, refer to the Oracle Net Services Administrator's Guide. |
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 the Installed Components button on the Oracle Universal Installer screen and explore the list of components. |
This section contains certification information for each Enterprise Manager component, including the Management Repository, Management Service, and Management Agent. Browser certifications for Grid Control are also given.
Also included in this section are the certifications for all targets managed by Enterprise Manager.
Table 1-4 describes the operating system platforms certified for each Enterprise Manager component: Management Repository, Management Service, and Management Agent.
Table 1-4 Certified Operating Systems for Enterprise Manager Components
Platform (Version) | Repository? | Service? | Agent? |
---|---|---|---|
Solaris Operating System (SPARC 32-bit) (8, 9) | X | X | X |
Solaris Operating System (SPARC 64-bit) (8, 9) | X | X | X |
HP-UX 64-bit (11.0, 11i) | X | X | X |
HP Tru64 (5.1b) | X | X | X |
IBM AIX 64-bit (5L) | X | X | X |
Red Hat Enterprise Linux ES andAS (2.1) | X | X | X |
Red Hat Enterprise Linux (3) | X | X | X |
United Linux 1.0 (Service Pack 3) | X | X | X |
Windows NT 4.0 (Service Pack 6a) | X | N/A | X |
Windows 2000 (Service Pack 4) | X | N/A | X |
Windows XP (Professional Edition) | X | N/A | X |
Windows 2003 (Standard Edition) | X | N/A | X |
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-5 lists the browser versions that are certified for the Solaris, Windows, and Linux operating systems for Enterprise Manager Grid Control.
Table 1-5 Browser Certifications for Grid Control
Operating System | Browser | Version |
---|---|---|
Solaris | Netscape Navigator | 7.0.1, 7.1.0 |
Windows | Netscape Navigator
Microsoft Internet Explorer |
4.78, 4.79, 7.0.1, 7.1.0
5.5 (Service Pack 1); 6.0 (Service Pack 2) |
Linux | Mozilla | 1.3.1 |
Microsoft Pocket PCFoot 1 | 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-6 identifies the Oracle targets and components that Enterprise Manager Grid Control can manage.
Table 1-6 Oracle Targets and Components
Supported Targets | Version |
---|---|
Oracle Application ServerFoot 1 | 9.0.2.x
9.0.3.x 9.0.4.x |
Oracle DatabaseFoot 2 and Listener | 8.1.7.4
9.0.1.5 and higher 9.2.0.4 and higher 10.1.0.2 |
Oracle Real Application Clusters Database | 9.2.0.4 and higher
10.1.0.2 |
Management Service and Management Repository | 9.0.1.5 and higher
9.2.0.4 and higher 10.1.0.2 |
Management Agent | 10.1.0.2 |
Host | All supported platforms. See Table 1-4. |
Oracle Collaboration Suite | 9.0.4.1.x |
BeaconFoot 3 | 10.1.0.2 |
Web ApplicationFoot 4 | N/A |