Installing management Agent (10.2.0.3)

22 07 2008

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. Software for OEM agent is available from oracle site.

You can install the Management Agent in the following ways:

· On each host computer, run Oracle Universal Installer from the Enterprise Manager DVD-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 Agent Deploy application to perform a fresh agent installation (standalone or cluster agent) or a shared agent installation.

· Use the nfsagentinstall script to install and deploy the shared Mangement Agent.

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

See Also:

See Chapter 5, ” Deploying the Management Agent” for a full and detailed explanation on installing Management Agents using the agentDownload script and the nfsagentinstall script.

See Appendix G, “Assigning Custom Ports” for information on assigning custom port numbers for Enterprise Manager components.

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 same OS Group group that was used to install the Application Server. Otherwise, you cannot 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 sufficient 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.

Prerequisites

Ensure the Agent Oracle home must not contain any other Oracle software installation.

Note:

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

To Install an Additional Management Agent Using OUI

1. Start the Oracle Universal Installer by running the runInstaller script in Linux (<DVD>/runInstaller) from the top directory of the DVD.

2. In the Specify Installation Type page, select the fourth option (Additional Management Agent), and specify the parent directory path and installation name.

Figure 3-20 Specify Installation Type

Specify Installation Type

Specify Installation Type

3. In the Specify Installation Location page, specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. The agent home created during the installation is placed as a sub-directory under this parent directory. For example: agent10g.

Note:

Ensure you do not use symbolic links to the Oracle home path.

The installer by default installs the selected products in the English language.

a. If you want to install the product in a different language, click Product Languages.

b. The Language Selection page appears. Make the required language selections here, and click Next. See Figure 3-3, “Language Selection” for details.

4. The Product Specific Prerequisites Check page appears.

This page displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

Depending on the status of the automatic checks, you must verify all warning and manual checks. To do this, select the appropriate prerequisite status check box and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the page. See Figure 3-5, “Product-Specific Prerequisite Checks” for more information.

Note:

You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. For more information on running these prerequisite checks in standalone mode, see Chapter1, “Running the Prerequisite Checker in Standalone Mode”for more information.

5. Click Next. The Specify Oracle Management Service Location page appears.

Figure 3-21 Specify Oracle Management Service Location

a. Specify the Management Service host name. For example: dlsun1444.acme.com. Use the fully-qualified host name (including domain).

ATTENTION:

When specifying the host name, ensure you do not include the protocol (that is, http:// or https://).

b. Enter the port number for the Management Service. The default port is 4889 and the default secure port number is 1159.

However, even if you are specifying a secure Management Service, you must still enter the non-secure port number (4889) here. You must connect over HTTP to receive the certificate before you can connect over HTTPS.

Note:

If your Management Service has been configured to use HTTPS, you are prompted to enter the Agent Registration password (used to secure the management Service environment). If you do not know the password, obtain it from the user who configured the Management Service for SSL.

6. Click Next. If the Management Service is found to be running in a secure mode, the Specify Agent Registration Password page appears. You must provide the correct password to enable communications between the new Management Agent and the SSL-enabled Management Service.

Figure 3-22 Specify Agent Registration Password

IMPORTANT:

If you do not know the password and choose to leave the Password field blank, you must do the following after installation to enable communication between the agent and secure OMS:

· Find out the correct password for the secure OMS environment. If you do not know the password, obtain it from the user who configured the Management Service for SSL.

· In the <AGENT_HOME>/bin directory, execute the following command:

·                emctl secure agent <password>
·                 

where <password> is the Agent Registration Password.

7. Click Next. The Summary page appears.

This page displays a summary of the options that you have selected during the installation process. Depending on the installation type, this page displays any or all of the following details:

· Global Settings

· Product Languages

· Space Requirements

· New Installations

For more information on each of the above-listed details, see the Enterprise Manager Online Help.

Verify the choices that you have made and click Install to start the installation. Enterprise Manager Installer starts installing the selected Oracle product.

8. During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog that is displayed (only for Linux). Figure 3-12, “Execute Configuration Scripts” provides details on this page .

. To execute these scripts, go to the terminal window, log in as root, and run these configuration scripts.

a. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

9. The Configuration Assistants page appears. At this point, the installer starts running the recommended configuration tools.

This page displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 3-4 to see the list of configuration tools that are run.

See Appendix D, “Executing the runConfig Command Line Tool” for information on executing the runConfig tool.

10. After successfully running all the recommended configuration tools, click Next. The End of Installation page appears.

This page displays some important information about the products you have installed. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.

For example, it might contain information about the URLs for particular Web applications. If necessary, write this information down so that you can remember it.


Actions

Information

Leave a comment