Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 1 (12.1.0.1)
E24089-15
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

6 Installing Oracle Management Agent Using RPM File

This chapter describes how you can install Oracle Management Agent (Management Agent) using its.rpm file. In particular, this section covers the following:

Overview

Installing a Management Agent using its .rpm file is primarily a silent way of installing a Management Agent. In this method, you download the.rpm file to a temporary directory on the destination host, and install it directly on the destination host without using any response file. Since you install it directly on the destination host, it is best suited for installing a few Management Agents, one at a time.

Once the installation is complete, you will see the following default contents in the agent base directory:

<agent_base_directory>
    |_____core
         |_____12.1.0.1.0
    |_____plugins
    |_____agent_inst
    |_____sbin
    |_____plugins.txt
    |_____agentimage.properties

Note:

Using the .rpm file, you can also choose to install a Management Agent while provisioning an operating system on a bare metal host. For more information, see the Oracle Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching. This guide is available in the Enterprise Manager documentation library at:

http://www.oracle.com/technetwork/indexes/documentation/index.html



Note:

If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Oracle Management Service. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment.

Before You Begin

Before you begin installing a Management Agent, keep these points in mind:

Prerequisites

Before installing the Management Agent, ensure that you meet the following prerequisites.

Table 6-1 Prerequisites for Installing Oracle Management Agent Using RPM File

Requirement Description

Hardware Requirements

Ensure that you meet the hard disk space and physical memory requirements. For more information, see the chapter on hardware requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Operating System Requirements

Ensure that you install the Management Agent only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support.

To access this matrix, follow these steps:

  1. Log in to My Oracle Support, and click the Certifications tab.

  2. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Cloud Control.

  3. From the Release list, select 12.1.0.1.0, and click Search.

    Note: If you use Oracle Solaris 10, then ensure that you have update 9 or higher installed. To verify whether it is installed, run the following command:

    cat /etc/release

    You should see the output similar to the following. Here, s10s_u6 indicates that update 6 is already installed.

    Solaris 10 10/08 s10s_u6wos_07b SPARC

Package Requirements

Ensure that you install all the operating system-specific packages. For more information, see the chapter on package requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

User and Operating System Group Requirement

Ensure that the destination host where you want to install the Management Agent has the appropriate users and operating system groups created.

For more information, see the chapter on creating operating system groups and users in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Time Zone Requirements

Ensure that the host time zone has been set correctly. To verify the host time zone, run the following command:

echo $TZ

If the time zone displayed is incorrect, run the following commands, before running the agentDeploy.sh or agentDeploy.bat scripts, to set the correct time zone:

  • For Korn shell:

    TZ=<value>

    export TZ

  • For Bourne shell or Bash shell:

    export TZ=<value>

  • For C shell:

    setenv TZ <value>

For example, in the Bash shell, run the following command to set the time zone to America/New_York:

export TZ='America/New_York'

The time zones you can use are listed in <AGENT_HOME>/sysman/admin/supportedtzs.lst.

Note: If you had ignored a prerequisite check warning about wrong time zone settings during the Management Agent install, you must set the correct time zone on the host after installing the Management Agent. For information on setting time zones post install, refer After You Install.

Path Validation Requirements

Validate the path to all command locations. For more information, see the appendix on validating command locations in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

CLASSPATH Environment Variable Requirements

Unset the CLASSPATH environment variable. You can always reset the variable to the original value after the installation is complete.

Temporary Directory Space Requirements

Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied.

By default, the temporary directory location set to the environment variable TMP or TEMP is honored. If both are set, then TEMP is honored. If none of them are set, then the following default values are honored: /tmp on UNIX hosts and c:\Temp on Microsoft Windows hosts.

Agent Base Directory Requirements

Ensure that the installing user owns the agent base directory.

Ensure that the directory name does not contain any spaces.

Ensure that the installer user or the root user owns all the parent directories. Ensure that the root user owns the root directory.

For example, if the agent base directory is /scratch/OracleHomes/agent, and oracle is the installing user, then the /scratch/OracleHomes/agent directory must be owned by oracle, directories scratch and OracleHomes must be owned by either oracle or root user, and the root directory (/) must be owned by root user.

If the agent base directory is mounted, then ensure that it is mounted with the setuid turned on.

Permission Requirements

  • Ensure that you (in fact, all users accessing the agent base directory) have read and execute permission on all the directories that lead up to the agent base directory.

    For example, if the agent base directory is /home/john/oracle/software/agent/, then you must have read and execute permissions on all the directories, mainly home, john, oracle, software, and agent.

  • Ensure that the /usr/lib/oracle directory exists, is empty, and has write permission.

Port Requirements

Ensure that the default ports described in What Default Ports Are Used? are free.

Installing User Requirements

If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group.

Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory.

For example, if the inventory owner is abc and the user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory.

Central Inventory (oraInventory) Requirements

  • Ensure that you allocate 100 MB of space for the Central Inventory.

  • Ensure that the Oracle Inventory (oraInventory) is not in a shared location. When you use the /etc/oraInst.loc file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location by following the instructions outlined in My Oracle Support note 1092645.1.

  • Ensure that you have read, write, and execute permissions on oraInventory on all remote hosts.


Installation Procedure

To install a Management Agent using its .rpm file, follow these steps:

  1. On the OMS host, from the OMS home, log in to the EMCLI client. EMCLI Client is available by default with every OMS installation, so you need not install the client separately.

    $<OMS_HOME>/bin/emcli login -username=<username> -password=<password>

    For example,

    $<OMS_HOME>/bin/emcli login -username=sysman -password=2benot2be

  2. Synchronize EMCLI:

    $<OMS_HOME>/bin/emcli sync

  3. Identify the platforms for which the Management Agent software is available on the OMS host:

    $<OMS_HOME>/bin/emcli get_supported_platforms

    This command lists all the platforms for which the Management Agent software is available on the OMS host. Example 6-1 shows a sample output of the command.

    Example 6-1 Output Showing Software Availability for Different Platforms

    ---------------------------------------------------
    Version = 12.1.0.1.0
    Platform Name = Linux x86
    ---------------------------------------------------
    Version = 12.1.0.1.0
    Platform Name = Oracle Solaris on x86-64 (64-bit)
    ---------------------------------------------------
    Version = 12.1.0.1.0
    Platform Name = HP-UX PA-RISC (64-bit)
    ---------------------------------------------------
    

    If the output lists the platform on which you want to install the Management Agent, then proceed to the next step. Otherwise, download the software for the required platform using the Self Update console.

    For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

  4. Download the .rpm file of the Management Agent from Oracle Software Library to a temporary directory on the OMS host

    $<OMS_HOME>/bin/emcli get_agentimage_rpm -destination=<download_directory> -platform="<platform>" -version=<version>

    For example,

    ./emcli get_agentimage_rpm -destination=/tmp -platform="Linux x86" -version=12.1.0.1.0


    Note:

    In the command, note the following:
    • -destination is a directory on the OMS host where you want the .rpm file to be downloaded. Ensure that you have write permission on this location.

      If the destination directory is titled with two or more words separated by a space, then enclose the directory name with double quotes.

      For example, if the destination directory is titled /tmp/linux agentimage, then enter the value as -destination="/tmp/linux agentimage"

    • -platform is the platform for which you want to download the .rpm file; this must match one of the platforms listed in the previous step for which the software is available on the OMS host.

    • -version is the version of the Management Agent for which you want to download the .rpm file; this is an optional argument. If you do not pass this argument, then the version is defaulted to the OMS version.


    The command downloads the .rpm file of the core Management Agent to the destination directory you entered. For example, oracle-agt-12.1.0.1.0-1.0.i386.rpm

  5. Transfer the downloaded .rpm file to a temporary directory (/tmp) on the destination host where you want to install the Management Agent. You can use any FTP software to transfer the file. For example, FileZilla.

  6. On the destination host, run the .rpm file as a root user to install the Management Agent:

    rpm -ivh <download_directory>/<rpm_file>

    For example,

    rpm -ivh /tmp/oracle-agt-12.1.0.1.0-1.0.i386.rpm


    Note:

    The following is the output of the command:
    Preparing... ########################################### [100%]
    Running the prereq
    1:oracle-agt ########################################### [100%]
    Follow the below steps to complete the agent rpm installation:
    1. Edit the properties file: /usr/lib/oracle/agent/agent.properties with the correct values
    2. Execute the command /etc/init.d/config.pl
    

  7. Edit the agent.properties file as described in Table 6-2. The file is availabe in the following location:

    /usr/lib/oracle/agent/agent.properties

  8. Run the following command to complete the installation:

    /etc/init.d/config.pl


Note:

Despite a successful installation, if you see some exceptions in the prerequisite error file, you can ignore the exception trace. This issue might happen when an operation attempts to retrieve an element from a collection using a key that does not exist in that collection. You can ignore this exception.

Editing agent.properties File

Table 6-2 describes the various parameters you must include in the response file.

Table 6-2 Creating a Response File for Installing Oracle Management Agent Using an RPM File

Parameter Description

s_OMSHost

(Mandatory) Enter the host name of the OMS to which you want to connect.

s_OMSPort

(Mandatory) Enter the upload port (HTTP or HTTPS) to communicate with the OMS.

AGENT_REGISTRATION_PASSWORD

(Mandatory) Enter a password for registering new Management Agents that join the Enterprise Manager system.

By default, the communication between the OMS and the Management Agents is secured, and any new Management Agents that join the Enterprise Manager system must be authenticated before they become part of the system. The password you enter here will be used for authenticating those new Management Agents.

agentUserName

(Mandatory) Enter the user name with which you want to install the Management Agent.

agentUserGroup

(Mandatory) Enter the group to which the Management Agent user should belong.

OraInvLoc

(Optional) Enter the absolute path to the Central Inventory where the Management Agent user has write permission.

For example,

OraInvLoc =/usr/lib/oraInventory

Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

BASEDIR

(Optional) Enter the absolute path to the agent base directory where you want to install the Management Agent.

For example,

/home/john/oracle/

If you do not enter the path to the agent base directory, then by default, the Management Agent is installed in the following location:

/usr/lib/oracle/core/12.1.0.1.0

ORACLE_HOSTNAME

(Only for Virtual Hosts) Enter the virtual host name where you want to install the Management Agent.


After You Install

After you install the Management Agent, follow these steps:

  1. Verify the installation:

    1. Navigate to the Management Agent instance home and run the following command to see a message that confirms that the Management Agent is up and running:

      $<INSTANCE_HOME>/bin/emctl status agent


      Note:

      If the status of the Management Agent is down for some reason, then manually start the Management Agent by running the following command from the Management Agent instance home:

      $<INSTANCE_HOME>/bin/emctl start agent


    2. Navigate to the Management Agent and run the following command to see a message that confirms that EMD upload completed successfully:

      $<INSTANCE_HOME>/bin/emctl upload agent

  2. Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed.

    $<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log

    For example,

    /u01/app/Oracle/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log

    If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl script from the Management Agent home.

    $<AGENT_HOME>/perl/bin/perl <AGENT_HOME>/bin/AgentPluginDeploy.pl -oracleHome <AGENT_HOME> -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>

    For example,

    /u01/app/Oracle/core/12.1.0.1.0/perl/bin/perl /u01/app/Oracle/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /u01/app/Oracle/core/12.1.0.1.0/ -agentDir /u01/app/Oracle/ -pluginIdsInfoFile /u01/app/Oracle/plugins.txt -action configure -emStateDir /u01/app/Oracle/agent_inst

  3. If you had ignored a prerequisite check warning about wrong time zone settings, follow these steps:

    1. Set the correct time zone on the required host.

      For information on how to set the time zone on a host, refer Time Zone Requirements in Table 6-1.

    2. Deinstall the Management Agent present on the host.

      For information on how to deinstall a Management Agent, refer Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

    3. Install a Management Agent on the host.

  4. By default, the host and the Management Agent get automatically added to the Enterprise Manager Cloud Control console for monitoring. None of the targets running on that host get automatically discovered and monitored.

    To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.

    For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.


Note:

If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Oracle Management Service. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment.