Skip Headers

Oracle Enterprise Manager Configuration Guide
Release 9.2.0.2

Part Number A96673-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page Go to next page
View PDF

1
Introduction

This chapter describes key concepts and requirements associated with deploying Oracle Enterprise Manager and its separately licensable Management Packs:

Product Architecture

Oracle Enterprise Manager is Oracle's single, integrated solution for administering and monitoring global enterprises. Enterprise Manager is based upon a lightweight, three-tier architecture that offers flexible deployment options, round-the-clock reliability, and unparalleled scalability.

The product's three-tier architecture is comprised of the following:

This architecture, which underlies the Enterprise Manager framework, is described in more detail below.

Figure 1-1 Three-Tier Architecture

Text description of three_ti.gif follows.

Text description of the illustration three_ti.gif

First Tier: Centralized Consoles

The primary responsibility of first-tier Enterprise Manager clients is to present the user interface to administrators for all their management tasks.

Depending on what has been installed and licensed, first tier clients could consist of the following components:


Note:

Beginning with Release 9.0, Oracle DBA Studio functionality has been fully integrated within the Console.





Note:

Oracle Management Pack for SAP R/3 is available on its own CD-ROM in your CD Pack; it is not installed with the database.




The Oracle Enterprise Manager Console is designed to reduce the complexity of managing your Oracle Database Server, as well as the network components, software, and hardware that support the database.

Because these first-tier Consoles and applications depend upon the second-tier Management Servers for the bulk of their application logic, these clients are able to run without the overhead and processing burden of housing critical management services.

Second Tier: Central, Scalable and Reliable Oracle Management Servers

The second-tier component of Oracle Enterprise Manager, the Management Server, is the framework engine. The Management Server maintains centralized intelligence and distributed control between clients and managed nodes. It is responsible for all back-end application logic and critical services for maintaining an enterprise. The critical services include the event system, paging and e-mail notifications, reporting, job system, and others.

This middle tier processes requests from first-tier clients, stores the information in a database repository, and distributes tasks for third-tier Intelligent Agents to perform.

The repository also serves as a persistent back-end store where it maintains system data, application data, and the state of managed targets distributed throughout the environment. Data stored in the repository can be shared between any number of administrators accessing one or more Management Servers connected to a single repository.

Third Tier: Managed Targets and Autonomous Intelligent Agents

The third tier in the Enterprise Manager framework consists of managed targets and Intelligent Agents. Managed targets, which can include nodes, databases, web servers, application servers, applications, and others, rely on Intelligent Agents to execute tasks given by the Management Server. Once tasks are assigned, autonomous Intelligent Agents will perform the work as scheduled regardless of the state of the managed targets, Management Server, or clients. Examples of such tasks include executing SQL scripts, monitoring available space in a tablespace, performing weekly database backups, monitoring the real-time database physical I/O rate, or monitoring the availability of the application server.

Architectural Extensibility

To offer vital framework functionality the Enterprise Manager architecture can be easily extended on each tier. The first tier enables any number of clients to access one or more second-tier Management Servers. Deploying additional Management Servers provides increased scalability and reliability as well as a choice between grouping the Management Servers together with one repository or dividing them into smaller sets, each set with its own repository. The former configuration enables all administrators to share data contained in the single repository, while the latter offers autonomous units which never interact with each other. Lastly, the number of third-tier managed services and Intelligent Agents can increase with business demands.

Figure 1-2 Architectural Extensibility

Text description of extensib.gif follows.

Text description of the illustration extensib.gif

Across all three-tiers, the Enterprise Manager architecture establishes the foundation for the robust Enterprise Manager framework.

Deployment Options

Enterprise Manager's three tier architecture enables the highest level of reliability and scalability. However, not all enterprises need to implement Enterprise Manager as a three tier system. That is, not all businesses need to deploy each of the three tiers, nor need all companies deploy each tier on a separate machine. Because of the flexibility of Enterprise Manager's architecture, many deployment options are available.

Figure 1-3 Deployment Options

Text description of dbconnec.gif follows.

Text description of the illustration dbconnec.gif

Through analyzing your environment, determining your general administrative needs, and careful planning, you can effectively choose the deployment option best suited for your enterprise.

Available deployment options are described in this section.

Client/Server Deployment

A client/server deployment is one where only the Console and management applications are deployed. Neither the middle tier Management Server nor the Intelligent Agent are installed and used. In this standalone configuration, the client connects directly to the managed target and performs administration tasks.

You should use this type of deployment model if the following conditions apply:

Three Tier Deployment

A three tier deployment involves the installation and configuration of the entire Enterprise Manager framework: Console, Management Server/Repository, and Intelligent Agent.

You should use this type of deployment model when you require the following features:

For optimal performance with a three tier deployment of Enterprise Manager, follow these guidelines:


Note:

For information on defining Management Regions, a feature introduced with Enterprise Manager release 9i, see the Oracle Enterprise Manager Administrator's Guide.

For information on the repository views for Management Regions, see Appendix H, "Repository Views Addendum".




Certifications

Regardless of the deployment method selected, the following operating system certifications apply to the various components of Oracle Enterprise Manager Release 9.2.0:

Table 1-1 Operating System Support
Console Integrated Applications1 Management Packs2 Management Pack for SAP R/33 Thin Client4,7 Management Server Intelligent Agent5 Paging Server Web Site7

Windows NT 4.0 with Service Pack 6a

-Workstation

- Server

- Terminal Server

x

x

x

x

x

x

x

x

x

Windows NT 4.0 with Service Pack 6a Active Directory

x

Windows 2000 with Service Pack 2 6

- Professional Edition

- Server

- Advanced Server

- Terminal Service

x

x

x

x

x

x

x

x

x

Windows 2000 with Service Pack 2 Active Directory

x

Windows XP

- Professional

x

x

x

x

x

x

x

Windows 98

- Second Edition

x

x

x

x

x

Solaris 32 bit

- 2.8

- 2.7

- 2.6

x

x

x

x

x

x

Solaris 64 bit

- 2.8

x

x

x

x

x

x

HP/UX 64 bit

-11.0

x

x

x

x

x

x

IBM AIX 64 bit

- 4.3.3, 5.1

x

x

x

x

x

x

HP Tru64

- 5.1 & 5.1a

x

x

x

x

x

x

Intel Linux 32 bit

- SuSE SLES7 Kernel 2.4.7, glibc 2.2.2

- RedHat Advanced Server 2.1, kernel 2.4.9, glibc2.2.4-25

x

x

x

x

x

x



1 Integrated applications for Release 9i include Integrated applications include: Oracle Forms Server Manager, Oracle Policy Manager, OLAP Services, Oracle Cube Viewer, and Oracle Directory Manager

2 Management Packs include the Diagnostics Pack, Tuning Pack, Change Management Pack, and Management Pack for Oracle Applications. The following components of the Management Packs are not ported to Unix platforms: Trace in Diagnostics Pack, and SQL Analyze, Expert, Index Tuning Wizard in Tuning Pack.

3 Management Pack for SAP R/3 Release 9.2 has not been released.

4 Thin Browser client includes: the base Enterprise Manager; the Enterprise Security Manager; the entire Change Management Pack; and the Performance Manager, Lock Monitor, Performance Overview, Top SQL, and Top Sessions of the Diagnostics Pack; and the Tablespace Map, Reorg Wizard, Outline Manager, and Graphical Explain Plan of the Tuning Pack.

5The Intelligent Agent runs on the same Operating Systems as the RDBMS. Also, the Intelligent Agent is certified with the Active Directory shipped with Windows 2000 and Windows NT.

6 Windows 2000 Datacenter is not a certified/supported operating system for any Enterprise Manager Oracle9i component.

7If you choose to run Enterprise Manager from a browser, then the following certifications also apply.


Note:

For platform-specific details, refer to the given platform's release notes.




System and Hardware Requirements

After determining how to deploy Enterprise Manager and verifying certifications, ensure that the following system and hardware requirements are satisfied prior to installation and configuration.


Note:

Hard disk space requirements for FAT Windows-based operating systems could be as much as four times those indicated below.




For hardware and system requirements for other platforms, such as HP-UX and others, refer to the corresponding installation guides.

Oracle Enterprise Manager Client

Requirements are listed below for a machine running only the Enterprise Manager Client. The Client includes the Console, Management Packs and integrated applications.

Table 1-2 Console, Management Packs, and Integrated Applications
Minimal Recommended

Available Hard Disk Space

135 MB

N/A

Processor and RAM

Pentium 166 MHz with 128 MB RAM

or

SPARC 20 166 MHz with 128 MB RAM

Pentium 266 MHz with 256 MB RAM

or

SPARC Ultra 1 266 MHz with 128 MB RAM




Note:

Processor and RAM requirements identified above are applicable to both an installed Enterprise Manager Client as well as to a thin, web-based Client.




Management Server or Management Server and Client

Requirements are listed below for a machine running only the Management Server Release or for an Oracle Management Server machine which also runs the Enterprise Manager Client:

Table 1-3 Management Server or Management Server and Client
Minimal Recommended

Available Hard Disk Space

115 MB

N/A

Processor and RAM

Pentium 266 MHz with 128 MB RAM

or

SPARC Ultra 1 266 MHz with 128 MB RAM

Pentium 300 MHz with 256 MB RAM

or

SPARC Ultra 1 300 MHz with 256 MB RAM




Note:

Information listed above does not account for the database Repository. Refer to your database documentation for appropriate system and hardware requirements specific to an Oracle database.




Management Server, Client, HTTP Server, Intelligent Agent or Management Server and Client

Requirements are listed below for a machine running the Management Server Release 9.2, Enterprise Manager Client Release 9.2, Oracle HTTP Server Release, and Oracle Intelligent Agent 9.2 or for an Oracle Management Server machine which also runs the Enterprise Manager Client:

Table 1-4 Management Server or Management Server and Client
Minimal Recommended

Available Hard Disk Space

115 MB

N/A

Processor and RAM

Pentium II 866 MHz with 256 MB RAM

or

SPARC Ultra 1 266 MHz with 128 MB RAM

Pentium III 1GHz with 512 MB RAM

or

SPARC Ultra 1 300 MHz with 256 MB RAM




Note:

Information listed above does not account for the database Repository. Refer to your database documentation for appropriate system and hardware requirements specific to an Oracle database.




Enterprise Manager Web Site

Requirements are listed below for a machine running only the Enterprise Manager Web Site, which also includes the preconfigured Oracle HTTP Server.

Table 1-5 Enterprise Manager Web Site
Minimal Recommended

Available Hard Disk Space

275 MB

N/A

Processor and RAM

depends upon webserver

depends upon webserver



Java Runtime Environment (JRE)

Enterprise Manager has been certified on the following versions of the Java Runtime Environment (JRE):

Version Compatibility

The following matrix shows version compatibility between different Enterprise Manager components.

Table 1-6 Enterprise Manager - Intelligent Agent - Database Compatibility Matrix
Enterprise Manager Release... supports creation of its repository in Database Releases... and is supported by Intelligent Agent Releases... and manages Database Releases...

9.2.0

9.2.x

9.0.1.x

8.1.7.x

9.2.x

9.0.1.x

8.1.7.x

9.2.x

9.0.1.x

8.1.7.x

9.0.1

9.0.1.x

8.1.7.x See Note 1 and Note 2

8.1.6.x See Note 1 and Note 2

8.0.6.x

9.0.1.x

8.1.7.x

8.1.6.x

8.0.6.x

9.0.1.x

8.1.7.x

8.1.6.x

8.0.6.x

2.2.x

8.1.7.x

8.1.6.x

8.0.6.x

7.3.4.x

8.1.7.x

8.1.6.x

8.1.5.x

8.0.6.x

7.3.4.x

8.1.7.x

8.1.6.x

8.1.5.x

8.0.6.x

7.3.4.x

2.1.x

8.1.6.x

8.1.5.x

8.0.6.x

8.0.5.x

8.0.4.x

7.3.4.x

8.1.6.x

8.1.5.x

8.0.x

7.3.4.x

8.1.6.x

8.1.5.x

8.0.x

7.3.4.x

2.0.x

8.1.5.x

8.0.5.x

8.0.4.x

7.3.x

8.1.5.x

8.0.6.x

8.0.5.x

7.3.4.x

8.1.5

8.0.x

7.3.x

1.6.5.x

8.0.6.x

8.0.5.x

7.3.4.x

8.0.6.x

8.0.5.x

7.3.4.x

8.0.6

8.0.5.x

8.0.4.x

8.0.3.x

7.3.x



When creating your repository you should choose a database that is always available; will not be shutdown by other administrators, and does not compete for resources on the machine where it is running. Furthermore, Enterprise Manager's release 9i repository has been certified to reside in the following Oracle database releases (see Note 1):

Note 1

If your 9.2 repository is in database release 8.1.7.0 or 8.1.7.1, be aware that database base bug 1393049, which causes some SQL queries to return incorrect results, may affect Enterprise Manager in a variety of ways.

For example, the aforementioned database bug may manifest itself through Enterprise Manager through incorrect lists of events or jobs in history; incorrect list of event alerts; incorrect list of active jobs, invalid notifications being sent, and others.

To fix the problem, refer to the table below:

Table 1-7 Fixes for the Repository
If Repository Resides in Database Release Then Fix the Problem by

8.1.7.0 for all operating systems

Upgrading your database to release 8.1.7.2

8.1.7.1 for all operating systems

Upgrading your database to release 8.1.7.2

or

Apply one-off patch for bug 1765292



To avoid these known database problems entirely, Oracle recommends that you create your repository in Enterprise Edition or standard edition release 9.2, Enterprise Edition or standard edition release 9.0.1, or Enterprise Edition or standard edition release 8.1.7.2 or 8.1.7.1 (Sun SPARC Solaris only).

Note 2

If your repository is in database release 8.1.7.x for any operating system, Oracle recommends that you apply the patch for bug 1733170. Failure to apply this patch may result in intermittent Management Server faults due to segmentation violations.