Pre-requisite

Before you get started with the install, you will have to make sure that you have the right resources on the machine that you are installing Grid Control on to. The following table shows the minimum recommended resource requirement for Linux or Windows environment. You will need to check the install guide for resource requirements if you are using a different platform.

If you are installing both OMS and Management Repository on the same machine, we recommend that you have at least 4GB of RAM for better performance. You must be wondering why Enterprise Manager Grid Control requires so much resource! You have to understand that Oracle Enterprise Manager Grid Control is not a development tool but an administration tool for managing production targets such as databases and middleware. OMS runs an instance of Oracle Application Server 10g and the repository is based on an Oracle database.

Operating system requirements

Once you have ensured that you have sufficient resources on the machine on which you plan to install Oracle Enterprise Manager Grid Control, you have to then make sure that you meet the operating system's requirements. We recommend that you check the release notes available at Oracle Technology Network for your platform for the required patch level for your operating system.

If you are using a UNIX environment, the installation process requires a super user or (root) privileges on your box to run a script during the installation process. If you do not have system administration privileges on your machine, you will have to work with the system administrator to run the script before you can complete the installation. Here are some other operating system's requirements that your system must meet:

Downloading the software

The Oracle Enterprise Manager Grid Control software can be downloaded from Oracle Technology Network at the following location: http://www.oracle.com/technology/software/products/oem/index.html.

This book primarily covers 10gR5 features and hence, we recommend that you install this version. In order to install 10.2.0.5, you will need to download 10gR1 and the 10.2.0.5 patchset.

Both these binaries are large files and you will need around 15 GB of storage space to store the downloaded ZIP files, unzipped version of binaries, and actual installed binaries for the OMS, and the repository and storage space for the repository.

Installing OMS and repository

In this section, we will present you with some guidelines that you can use along with the install guide. We are assuming that you are installing Grid Control for the first time for a learning or testing purpose. Hence, we will focus on the simple install type where both OMS and Repository are installed on the same machine. Also, we assume that you will choose a new database for the management repository. This is the fastest way to install Grid Control. This will install database software and create the repository database.

Installing Grid Control 10gR1 or 10gR2

To get started with the install of Grid Control 10gR5, you will have to install 10gR1 on Linux 32 or 10gR2 on the Windows environment. Make sure that you have downloaded the binaries to your server. Let us assume that you are installing on a Linux 32 machine.

You can start Oracle Universal Installer by running the runInstaller (or setup.exe on Microsoft Windows) from the top-level directory of the software binaries.

The installer verifies the pre-requisites (O/S version, patch level, memory, and so on) when they get invoked. Some of the pre-requisite checks may fail and the installer may ask you to proceed or cancel the install.

As you proceed with the install, you will be prompted to choose the install type. For simplicity and for testing/training purposes we recommend that you choose the Enterprise Manager 10g Grid Control Using a New Database option, as shown in the following screenshot:

After this screen you will be prompted to enter the following information in three subsequent screens:

• Install location: This will contain directories where the OMS and repository database will get installed
• Oracle Inventory details: This will contain the directory to store the Oracle Inventory and the group that will have access to the Oracle Inventory
• National Language selection: This will let you choose the language to be used for the install

Database details for the repository are shown in the following screenshot:

You will also be asked to provide credentials for the database repository and super user (sysman) for the OMS, as shown in the following screenshot:

Make sure that you make a note of these passwords as you will need them in the future, to logon to the OMS or to manage the repository database.

The installer will first install the binaries and then run the Configuration Wizard to configure the OMS and the repository database. Before the Configuration Assistants are run, the installer will prompt you to run some configuration scripts and you need administration or (root) privileges to run these scripts. The Configuration Wizard will fail if you do not run these scripts.

After the install is successfully completed, the installer will provide you with the URL for the management console.

The default http port for the OMS is 4889, and you can access Grid Control by using the URL in the following format http://hostname:port/em. You will have to enter SYSMAN as your user ID and the password that you entered during the install process.

After a successful login, you will see the Grid Control, as in the following screenshot:

Installing Management Agent

You can either upgrade your existing Agent to 10gR5 or download 10gR5 Agent and install it on your target machine. Unlike the OMS, the agent does not require you to first install 10gR1. You can directly install the 10gR5 Agent. There are several ways to install the Agent, yet for simplicity, the OUI method is recommended. You will have to select the right option as shown:

The most important step in the Agent install is wiring or pointing your Agent to your OMS as in the following screenshot:

This helps the OMS to discover the Agent, and therefore the targets, managed by the agent. As soon as the agent is installed on the machine and it is started, the target machine will be automatically discovered in the OMS. You will able to verify that simply by logging into Enterprise Manager Grid Control and clicking on targets. We will discuss this further in Chapter 4,Managing Oracle WebLogic Server, when we discover an Oracle WebLogic Server.