2 Installing Enterprise Manager

This chapter describes the possible deployment paths, or installation options, available for Enterprise Manager and provides basic instructions for installing with Oracle Universal Installer. This chapter contains the following sections:

Configuring Host Names
Enterprise Manager Installation Options
Using Oracle Universal Installer

Note:
For information on migrating to Oracle Enterprise Manager 10g from previous versions of Enterprise Manager, see Oracle Enterprise Manager Advanced Configuration.

Configuring Host Names

Before you can begin installing Enterprise Manager on a UNIX system, Oracle Universal Installer requires that fully qualified host name information appears in the configuration files for your system. A fully qualified host name includes both the name of the system and its domain.

Verify that /etc/hosts.* has the following format:

<IP_ADDRESS> <FULLY_QUALIFIED_HOSTNAME> <SHORT_HOSTNAME> <ALIASES>

The following example shows a properly configured /etc/hosts.* file:

148.87.9.44 oasdocs.us.oracle.com oasdocs oracleinstall

In addition to /etc/hosts, ensure the following files use the fully qualified host name:

/etc/nodename
/etc/inet/hosts
/etc/hostname.*
/etc/net/ticlts/hosts
/etc/net/ticots/hosts
/etc/net/ticotsord/hosts
/etc/inet/ipnodes

See Also:

For more information on the host name file configuration, refer to the Oracle Application Server Installation Guide. After you have properly configured the host name information, reboot your system before beginning the installation.

Enterprise Manager Installation Options

The following pre-defined installation options described in Table 2-1 determine which components will be installed on your system. During installation, you are prompted to choose one of the following options.

Table 2-1 Enterprise Manager Installation Options

Installation Option	Description	Memory Pre-requisite^Foot 1
Enterprise Manager 10g Grid Control Using a New Database	Installs the Enterprise Manager Grid Control framework^Foot 2 onto the host machine, creating the Management Repository on a new Enterprise Edition Oracle9i Database Release 1 (9.0.1.5). Oracle recommends installing Enterprise Manager on a separate disk from the Oracle Database containing the Management Repository.	1024 MB
Enterprise Manager 10g Grid Control Using an Existing Database	Installs the Enterprise Manager Grid Control framework onto the host machine, creating the Management Repository on a qualified existing database, which may be local to the host or remote.	512 MB
Additional Management Service	Installs the Enterprise Manager Grid Control framework, without the Management Repository, onto the host machine. Allows you to specify an existing Management Repository, either local or remote.	512 MB
Additional Management Agent	Installs the Management Agent on the target machine you want to monitor with Grid Control. The Management Service and Management Repository are not required on the same machine as the Management Agent, but must exist within the enterprise. The Management Agent may be installed on a cluster node.	No minimum requirement

^Footnote 1This pre-requisite check is performed by the Oracle Universal Installer prior to installation and is set in the oraparam.ini file supplied with the product.
^Footnote 2The Enterprise Manager Grid Control framework consists of the Management Repository, Management Service, Management Agent, and OracleAS J2EE and Web Cache, against which the middle-tier Management Service Web application is deployed.

Note:

Enterprise Manager Java Console and Change Management Pack are available on the separate Database Client CD-ROM.

See Also:

Refer to Oracle Enterprise Manager Concepts for more detailed information about Grid Control, the Management Repository, Management Service, and Management Agent, and how they work together.

Refer to "Performing Silent Installations" for information on using a response file to install in silent mode.

Note:

If you have chosen to perform a full Enterprise Manager Grid Control installation in either a new or an existing database, and the installation fails to start the Management Agent installation after installing the Management Service, perform the following steps:

Set the EM_REPOS_PWD environment variable to the value you specified for the SYSMAN password during installation.
Run the Univeral Installer with the following command:

./runInstaller -responseFile OMS_HOME/install/agent.rsp

This will start the Management Agent portion of the Enterprise Manager Grid Control installation.

Enterprise Manager 10g Grid Control Using a New Database

Select this option, the default, if you want Enterprise Manager Grid Control and all its required dependencies installed on a single host machine. If you choose this installation option, you do not need an existing Enterprise Edition database.

Enterprise Manager 10g Grid Control Using an Existing Database

Select this option if you want to perform a complete Enterprise Manager Grid Control installation and have a qualified existing database in which to create the Management Repository. The database can be local or remote to the machine on which you're installing. Real Application Clusters databases must be on a shared disk.

See Also:

Refer to the "System and Network Configuration" chapter of the Oracle High Availability Architecture and Best Practices guide for information on cluster configuration recommendations.

Table 1-3, "Software Requirements" includes information on the versions of the Oracle Database and Real Application Clusters Database that qualify for Management Repository creation.

Attention:

The hardware requirements for the Management Repository and the operating system patch requirements for the host machine must be satisfied regardless of whether you choose to create a new database or use an existing database for the Management Repository during the installation session.

If you plan to use an existing database for your Management Repository creation, check all software requirements for the database and host, as well as for the repository.

For hardware and software requirements, refer to Chapter 1. For a list of required patches, refer to Appendix A.

Note:

The Enterprise Manager Repository Configuration Assistant will fail if the SYSMAN user already exists in the database you specify for the Management Repository. The configuration assistant will also fail if a Management Repository already exists in the database.

Refer to the "Maintaining and Troubleshooting the Management Repository" chapter in Oracle Enterprise Manager Advanced Configuration for instructions on how to drop the existing Repository from the database.

Additional Management Service

Select this option if you need to add an additional Management Service to your environment because the current Management Service is running out of CPU or RAM resources.

See Also:

Refer to the "Reconfiguring the Management Agent and Management Service" chapter of Oracle Enterprise Manager Advanced Configuration for information on controlling the Management Service.

For information on assigning custom port numbers for Enterprise Manager components, refer to the "Assigning Custom Ports (the "Static Ports" Feature)" section.

Additional Management Agent

Select this option to install the Management Agent in an Oracle home directory on a specified host target. Each host you wish to monitor must have an Agent installed.

Note:

Enterprise Manager does not support uploading data to the same Management Repository from two Management Agents running on the same host.

You can install the Management Agent in the following ways:

On each host computer, run Oracle Universal Installer from the Enterprise Manager CD-ROM and select the Additional Management Agent installation type. This method installs one Agent at a time in interactive GUI mode. You may also perform silent installations using a response file.

Use the agentDownload script to install and deploy Management Agents to many managed hosts through HTTP or over the network.

See Also:

For a full and detailed explanation on installing Management Agents using the agentDownload script, refer to Appendix C in this guide.

For information on assigning custom port numbers for Enterprise Manager components, refer to the "Assigning Custom Ports (the "Static Ports" Feature)" section.

Attention:

If you install the Management Agent on a system where you have already installed an Oracle Application Server instance, you must install the Management Agent from a user account that belongs to the group used to install the Application Server. Otherwise, you won't be able to monitor the application server metrics.

To see which group was used to install the Application Server, type ls -l on the command line in the directory containing opmn.xml: <AS_ORACLE_HOME/opmn/conf.
To see the groups to which you belong, type groups on the command line. You may be a member of several groups. Note that it is not enough to be a member of the group used to install the Application Server; that group must be your current group.
To see which user/group you are currently using, type id on the command line. Use the newgrp command to change to the group used to install the Application Server. Oracle recommends installing all software using a single group.

Using Oracle Universal Installer

Enterprise Manager installation uses the Oracle Universal Installer, a Java-based graphical user interface (GUI) application that enables you to install Oracle components from a CD, multiple CDs, or the Web.

See Also:

For information on using Universal Installer to install Oracle software, refer to the Oracle Universal Installer Concepts Guide.

Performing Silent Installations

The Management Agent supports silent installations in which you can install components without displaying screens or responding to questions. In silent installations, a response file provides the necessary installation information, normally answered by the user, using stored values.

Note:

You do not need to set the DISPLAY environment variable for silent installations in Universal Installer.

Table 2-2 shows the response files made available for each installation type. The response files are available on the installation CD-ROM at:

Disk1/stage/Response

Table 2-2 Available Response Files for Silent Installation

Installation Option	Response File
Enterprise Manager 10g Grid Control Using a New Database	em_with_new_db.rsp
Enterprise Manager 10g Grid Control Using an Existing Database	em_using_existing_db.rsp
Additional Management Service	additional_mgmt_service.rsp
Additional Management Agent	additional_agent.rsp

See Also:

For more information on silently installing Management Agents on multiple hosts using the agentDownload script, refer to Appendix C.

Starting the Installer

Start the Oracle Universal Installer by running the runInstaller script from the from the top directory of Disk 1:

$ ./runInstaller

To specify a response file for a silent installation, use the following command:

$ ./runInstaller -responseFile <responsefile_name> <optional_parameters>

See Also:

Refer to the "Creating and Customizing Response Files" chapter of the Oracle Universal Installer Concepts Guide for more information on silent installations.

After you enter the ./runInstaller command, the installation runs pre-requisite checks on:

Operating System Version
Operating System Packages
Operating System Patches
TEMP and SWAP space
DISPLAY Colors
Additional Patches
Kernel version (for Linux)

These pre-requisite checks can be viewed in the initialization parameters file located in the following directory of the product-specific installation CD-ROM:

Disk1/install/oraparam.ini

If a pre-requisite check fails, you are prompted to continue or stop the installation process. You may install the missing software at this point or discontinue the installation. Note, however, that you may have newer patches that supersede the required patches. Refer to Appendix A for patching information.

Once you continue, follow the installation instructions on the screen. At any time while installing Enterprise Manager, you can click Help for information about the screens.

Assigning Custom Ports (the "Static Ports" Feature)

You can specify custom port numbers for components, instead of having the installer assign default port numbers. This feature is called the "static ports" feature. To use static ports, you set up a file with component names and desired port numbers. The installer uses the values from the file instead of the default port numbers.

This file is typically called the staticports.ini file, but you can name it anything you wish. The "Format of the staticports.ini File" section describes the file format.

See Also:

For more information on assigning custom port numbers for installation components, refer to the Oracle Application Server 10g Installation Guide for Solaris Operating Systems.

When you start the installer, specify the appropriate parameter and the full path to the staticports.ini file on the command line. Make sure that you use the correct parameter for the installation type that you are using. If you use the incorrect parameter, the installer assigns default ports to all components.

Table 2-3 shows the parameters for specifying the static ports file on the command line, where <full path> denotes the full path to the local staticports.ini file.

Table 2-3 Parameters for Installing Using Static Ports File

Installation Type	Parameter
Enterprise Manager 10g Grid Control Using a New Database	oracle.sysman.top.em_seed:s_staticPorts=<full path>
Enterprise Manager 10g Grid Control Using an Existing Database	oracle.sysman.top.em_noseed:s_staticPorts=<full path>
Additional Management Service	oracle.sysman.top.oms:s_staticPorts=<full path>
Additional Management Agent	oracle.sysman.top.agent:s_staticPorts=<full path>

For example, to install an additional Management Agent, in the Disk1 directory, type the following command at the command line:

./runInstaller oracle.sysman.top.agent:s_staticPorts=<full path>

Note:

If you do not specify the full path to the staticports.ini file, the installer changes the current directory to a different one from the directory from which you started the installer, and the installer will not be able to find the file. In this event, the installer will assign default ports for all components, and it will do this without displaying any warning.

Copy the staticports.ini file from the Disk 1 CD-ROM to your hard disk. The file is located at:

Disk1/stage/Response/staticports.ini

Edit the local copy (the file on the hard disk) to include the desired port numbers.

You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, the installer uses the default port number for that component.

When installation is complete, you can check the ORACLE_HOME/install/portlist.ini file to view the assigned ports.

Notes:

When choosing port numbers, consider the following:

Port numbers cannot be greater than 65536.
If you use a port number less than 1024 for a component, you must run the component as the root user.
If you use a port number less than 1024 for a component, the installer will not be able to start up the component at the end of installation. You may need to configure the component first before you can start it up. See the appropriate component documentation for details.

The installer verifies that the ports specified in the file are available by checking memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.

If the installer detects that a specified port is not available, it displays an alert. The installer will not assign a port that is not available. To fix this:

Edit the staticports.ini file to specify a different port, or shut down the application that is using the port.
Click Retry. The installer re-reads thestaticports.ini file and verifies the entries in the file again.

Tip:

The staticports.ini file uses the same format as the ORACLE_HOME/install/portlist.ini file, which is created after an Oracle Application Server installation. If you have installed Oracle Application Server and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

Format of the staticports.ini File

The staticports.ini file has the following format. Replace port_num with the port number that you want to use for the component.

# Enterprise Manager
Enterprise Manager Central Console port = port_num
Enterprise Manager Central Agent port = port_num
Oracle Management Service Upload (non-SSL) port = port_num

# J2EE and Web Cache
Oracle HTTP Server port = port_num
Oracle HTTP Server Listen port = port_num
Oracle HTTP Server SSL port = port_num
Oracle HTTP Server Listen (SSL) port = port_num
Oracle HTTP Server Diagnostic port = port_num
Oracle HTTP Server Jserv port = port_num
Java Object Cache port = port_num
DCM Java Object Cache port = port_num
Oracle Notification Server Request port = port_num
Oracle Notification Server Local port = port_num
Oracle Notification Server Remote port = port_num
Application Server Control port = port_num
Application Server Control RMI port = port_num
Oracle Management Agent port = port_num
Web Cache HTTP Listen port = port_num
Web Cache HTTP Listen (SSL) port = port_num
Web Cache Administration port = port_num
Web Cache Invalidation port = port_num
Web Cache Statistics port = port_num
Log Loader port = port_num

# Business Intelligence and Forms
Discoverer OSAgent port = port_num
Reports Services SQL*Net port = port_num

# Infrastructure
Oracle Internet Directory port = port_num
Oracle Internet Directory (SSL) port = port_num
Oracle Certificate Authority SSL Server Authentication port = port_num
Oracle Certificate Authority SSL Mutual Authentication port = port_num

Error Conditions that Will Cause the Installer to Resort to Default Ports

Check your staticports.ini file carefully because a mistake can cause the installer to use default ports without displaying any warning. Here are some things that you should check:

If you specify the same port for more than one component, the installer will use the specified port for the first component, but for the other components, it will use the components’ default ports. The installer does not warn you if you have specified the same port for multiple components.
If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.
If you misspell a component name, the installer assigns the default port for the component. Names of components in the file are case sensitive. The installer does not display a warning for lines with unrecognized names.
If you specify a non-numeric value for the port number, the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.
If you misspell the parameter on the command line, the installer does not display a warning. It continues and assigns default ports to all components.
If you specify a relative path to the staticports.ini file (for example, ./staticports.ini) on the command line, the installer will not find the file. The installer continues without displaying a warning and it will assign default ports to all components. You must specify a full path to the staticports.ini file.
If the parameter you specify on the command line does not match the installation type that you are performing (for example, if you specify the parameter for middle tier but you are installing the infrastructure), the installer does not give a warning. It continues and assigns default ports to all components.