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

Previous
Previous
 
Next
Next
 

6 Installing Oracle Management Agent in Silent Mode

This chapter describes how you can install Oracle Management Agent (Management Agent) in silent mode. In particular, this chapter covers the following:

Overview

Installing a Management Agent in silent mode is only an alternative to installing it using the Add Host Targets Wizard. While the Add Host Targets Wizard requires you to use its GUI-rich interview screens for providing all installation details, the silent mode requires you to use a response file for providing installation details and deployment scripts to install Management Agents on hosts.

Installing in silent mode is useful when you want to install an additional Management Agent on a destination host from the destination host itself, without using the Add Host Targets Wizard.

You can install Management Agents in silent mode using the following methods:

Using the AgentPull Script

To install a Management Agent using the AgentPull.sh (AgentPull.bat for Microsoft Windows) script, you must do the following:

  1. Download the AgentPull.sh (AgentPull.bat for Microsoft Windows) script onto the destination host where the Management Agent needs to be installed, using a web browser or a data transfer tool.

  2. Execute the script on the destination host to install a Management Agent.

In this method, you do not need to download the Management Agent software onto the destination host before executing the script.

Using the agentDeploy Script

To install a Management Agent using the agentDeploy.sh (agentDeploy.bat for Microsoft Windows) script, you must do the following:

  1. Download the Management Agent software for the required platform onto the Oracle Management Service (OMS) host, using EMCLI.

  2. Transfer the Management Agent software to the destination host where you want to install the Management Agent. Unzip the software.

  3. Execute the agentDeploy.sh (agentDeploy.bat for Microsoft Windows) script on the destination host to install a Management Agent.

Using the RPM File

To install a Management Agent using the .rpm file, you must do the following:

  1. Download the .rpm file onto the Oracle Management Service (OMS) host using EMCLI.

  2. Transfer the .rpm file to the destination host where you want to install the Management Agent.

  3. Install the .rpm file on the destination host to install a Management Agent.


Note:

  • The Management Agent .rpm file is available only for Linux x86 and Linux x86-64 platforms.

  • From Enterprise Manager 12c Release 1 (12.1.0.1), installing a Management Agent by downloading the Management Agent .rpm file from Oracle Technology Network (OTN) is not supported.


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

<agent_base_directory>
    |_____core
         |_____12.1.0.2.0
    |_____plugins
    |_____plugins.txt
    |_____plugins.txt.status
    |_____agent_inst
    |_____sbin
    |_____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

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

    When you repoint your existing Management Agents to a new OMS, you cannot move the targets monitored by the Management Agents, the target history, and the Management Agent history. The monitored targets and the history data is lost.

  • If you upgrade a 12c Release 1 (12.1.0.1) Management Agent installed on a host to 12c Release 2 (12.1.0.2), and you want to install another Management Agent on the same host, reporting to a different OMS, ensure that you install the Management Agent after downloading the Management Agent software, and specifying the s_agentSrvcName parameter, as described in Installing Using agentDeploy Script.


Before You Begin

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

Prerequisites

Before installing a Management Agent in silent mode, ensure that you meet the following prerequisites:

Table 6-1 Prerequisites for Installing Oracle Management Agent in Silent Mode

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 the Enterprise Manager certification matrix, follow the steps outlined in Oracle Enterprise Manager Cloud Control Basic Installation Guide.

For information about platforms receiving future support, refer to My Oracle Support note 793512.1.

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.

If you choose to install a Management Agent using a .rpm file, ensure that the rpm-build package is installed on the host. To verify this, run the following command:

rpm -qa | grep rpm-build

cURL Utility

(For installing using the AgentPull script only)

Ensure that you install the cURL utility on the destination host.

You can download the cURL utility from the following URL:

http://curl.haxx.se/dlwiz/?type=bin

Note: The zip and unzip utilities must be present on the destination host, and must be of version 6.0 or higher. Also, for destination hosts running on Microsoft Windows, Oracle recommends that you install cURL in c:\.

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.

/etc/hosts File Requirements

Ensure that the /etc/hosts file on the host has the IP address, the fully qualified name, and the short name in the following format:

172.16.0.0 example.com mypc

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'

To set the time zone on a destination host that runs on Microsoft Windows, from the Start menu, select Control Panel. Click Date and Time, then select the Time Zone tab. Select your time zone from the displayed drop down list.

To view a list of the time zones you can use, access the supportedtzs.lst file present in the <AGENT_HOME>/sysman/admin directory of the central agent (that is, the Management Agent installed on the OMS host).

Note:

  • If you are installing a Management Agent on a host that runs on Microsoft Windows Server 2003, and you encounter an error when you use the Asia/Kolkata time zone, see the My Oracle Support note 1530571.1.

  • 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 Environment Variable Requirements

(For installing using the AgentPull script only)

(For Microsoft Windows) Ensure that the location of zip.exe and unzip.exe is part of the PATH environment variable.

For example, if zip.exe and unzip.exe are present in c:\Program Files\bin, then c:\Program Files\bin must be part of the PATH environment variable.

Path Validation Requirements

Validate the path to all command locations. For more information, refer to 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.

Port Requirements

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

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.

/var/tmp Requirements

(For installing using the .rpm file only)

Ensure that the /var/tmp directory has at least 700 MB of free space.

/usr/lib/oracle Requirements

(For installing using the .rpm file only)

Ensure that the /usr/lib/oracle directory has at least 2 GB of free space.

Agent Base Directory Requirements

Ensure that the agent base directory is empty and has at least 1 GB of free space.

Ensure that the directory name does not contain any spaces.

Ensure that the installing user owns the installation base directory. 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 installation 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.

Agent Instance Home Requirements

(For installing using the agentDeploy script only)

Ensure that the agent instance home location you specify in the response file is empty.

Permission Requirements

  • Ensure that you have write permission in the agent instance home.

  • Ensure that you have write permission in the temporary directory.

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 central inventory directory is not in a shared file system. If it is already in a shared file system, then create a new inventory in a non-shared file system. You can optionally migrate the products that were previously installed in the shared file system to this new inventory in the non-shared file system.

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

    If you do not have these permissions on the default inventory (typically in the location mentioned in the /etc/oraInst.loc file) on any remote host, then ensure that you enter the path to an alternative inventory location using the INVENTORY_LOCATION or -invPtrLoc arguments as described in Table 6-6. Note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.

Agent User Account Permissions and Rights

(For installing using the AgentPull or agentDeploy scripts only)

(For Microsoft Windows) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that the agent user account has permissions and rights to perform the following:

  • Act as part of the operating system.

  • Adjust memory quotas for a process.

  • Replace process level token.

  • Log in as a batch job.

To verify whether the agent user has these rights, follow these steps:

  1. Launch the Local Security Policy.

    From the Start menu, click Settings and then select Control Panel. From the Control Panel window, select Administrative Tools, and from the Administrative Tools window, select Local Security Policy.

  2. In the Local Security Policy window, from the tree structure, expand Local Policies, and then expand User Rights Assignment.

Permissions for cmd.exe

(For installing using the AgentPull or agentDeploy scripts only)

(For Microsoft Windows) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that you grant the Cmd.exe program Read and Execute permissions for the user account that the batch job runs under. This is a restriction from Microsoft.

For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site:

http://support.microsoft.com/kb/867466/en-us


Installation Procedure

This section describes the actions involved in installing a Management Agent in silent mode. It consists of the following:

Installing a Management Agent in Silent Mode

This section explains the methods of installing a Management Agent in silent mode. It consists of the following:

Installing Using AgentPull Script

To install a Management Agent using the AgentPull script, follow these steps:

Download the AgentPull Script onto the Destination Host

  1. If the destination host runs on UNIX, access the following URL from the host:

    https://<OMS_HOST>:<OMS_PORT>/em/install/getAgentImage

    If the destination host runs on Microsoft Windows, access the following URL from the host:

    https://<OMS_HOST>:<OMS_PORT>/em/install/getAgentImage?script=bat

    Save the file as AgentPull.sh (AgentPull.bat for Microsoft Windows) to a temporary directory, say /tmp (c:\temp for Microsoft Windows).


    Note:

    You can also use the following command to obtain the AgentPull.sh script:

    curl "https://<OMS_HOST>:<OMS_PORT>/em/install/getAgentImage" --insecure -o AgentPull.sh

    To use this command, ensure that you have the cURL utility installed, as described in Table 6-1.


  2. (Only for UNIX Operating Systems) Provide the execute permission to the AgentPull.sh script by running the following command:

    chmod +x <absolute_path_to_AgentPull.sh>

    For example, run the command chmod +x /tmp/AgentPull.sh.

Install the Management Agent Using the AgentPull Script

  1. Identify the platforms for which the Management Agent software is available on the OMS host. Run the AgentPull.sh script (AgentPull.bat for Microsoft Windows) specifying the -showPlatforms option to display the platforms for which the Management Agent software is available on the OMS host.

    <absolute_path_to_AgentPull.sh> -showPlatforms

    Example 6-1 shows a sample output of the command.

    Example 6-1 Output of Running AgentPull.sh Using -showPlatforms

    Platforms Version
    Linux x86-64 12.1.0.2.0
    Microsoft Windows x64 (64-bit) 12.1.0.2.0
    IBM AIX on POWER Systems (64-bit) 12.1.0.2.0
    
  2. If the destination host runs on UNIX, and the OMS host runs on Microsoft Windows, run the following command:

    dos2unix <absolute_path_to_AgentPull.sh>

    For example, run the command dos2unix /tmp/AgentPull.sh.

  3. Create a response file agent.rsp (in any location on the destination host) specifying the parameters described in Table 6-2.

    Example 6-2 shows the contents of a sample response file.

    Example 6-2 Response File Contents

    LOGIN_USER=sysman
    LOGIN_PASSWORD=welcome
    PLATFORM="Linux x86-64"
    VERSION=12.1.0.2.0
    AGENT_REGISTRATION_PASSWORD=wel246come
    
  4. Run the AgentPull.sh script (AgentPull.bat for Microsoft Windows) specifying the RSPFILE_LOC and AGENT_BASE_DIR parameters.

    <absolute_path_to_AgentPull.sh> RSPFILE_LOC=<absolute_path_to_responsefile> AGENT_BASE_DIR=<absolute_path_to_agentbasedir>

    For example, run the following command:

    /tmp/AgentPull.sh RSPFILE_LOC=/tmp/agent.rsp AGENT_BASE_DIR=/scratch/agent

    The AgentPull.sh script supports certain options, such as -download_only, which downloads the Management Agent software, but does not deploy the Management Agent. These supported options are described in Table 6-5.

Installing Using agentDeploy Script

To install a Management Agent using the agentDeploy script, follow these steps:

Download the Management Agent Software onto the OMS Host Using EMCLI

  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=sysman -password=<password>

    For example,

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


    Note:

    • The user name must always be sysman. Do not enter any other user name.

    • If you have configured a load balancer for a multiple OMS setup, ensure that you run the EMCLI commands on one of the local OMS hosts, and not on the load balancer hosts.

    • If you have configured a load balancer for a multiple OMS setup, and you choose to use the EMCLI setup command, ensure that you pass the OMS host and port as parameters, and not the load balancer host and port.

      For example, emcli setup -url=https://<OMS_HOST>:<OMS_PORT>/em -user=sysman -password=sysman


  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-3 shows a sample output of the command.

    Example 6-3 Output Showing Software Availability for Different Platforms

    ---------------------------------------------------
    Version = 12.1.0.2.0
    Platform Name = Linux x86-64
    ---------------------------------------------------
    Version = 12.1.0.2.0
    Platform Name = Oracle Solaris on x86-64 (64-bit)
    ---------------------------------------------------
    Version = 12.1.0.2.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, acquire and apply the Management Agent software for the required platform using Self Update.

    For information on how to acquire and apply the Management Agent software for a platform using Self Update, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.

  4. Download the Management Agent software from Oracle Software Library to a temporary directory on the OMS host:

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

    For example,

    ./emcli get_agentimage -destination=/tmp -platform="Linux x86-64" -version=12.1.0.2.0

    Ensure that you run the EMCLI get_agentimage command only on the OMS host. This command fails if you run it on any other host.


    Note:

    In the command, note the following:
    • -destination is a directory on the OMS host where you want the Management Agent software 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 software; 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 software that you want to download; 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 core Management Agent software to the destination directory you entered. For example, for Linux x86-64, you will see the file 12.1.0.2.0_AgentCore_226.zip. For information on the contents of this core software, see Understanding the Contents of the Downloaded Management Agent Software.

Transfer the Management Agent Software to the Destination Host

  1. Transfer the downloaded ZIP 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.

Install the Management Agent Using the agentDeploy Script

  1. On the destination host, extract the contents of the ZIP file using the unzip utility:

    unzip /tmp/<software_zip_file> -d <software_extract_location>

    For example,

    unzip /tmp/12.1.0.2.0_AgentCore_46.zip -d /tmp/agtImg

  2. Edit the response file agent.rsp as described in Table 6-3.

    <software_extract_location>/agent.rsp

  3. Invoke the deployment script and pass the response file:

    <software_extract_location>/agentDeploy.sh AGENT_BASE_DIR=<absolute_path_to_agentbasedir> RESPONSE_FILE=<absolute_path_to_responsefile>


    Note:

    • Instead of creating a response file, you can choose to pass response file parameters explicitly while invoking the deployment script.

      The mandatory response file parameters are OMS_HOST, EM_UPLOAD_PORT, and AGENT_REGISTRATION_PASSWORD.

      For example,

      /tmp/agtImg/agentDeploy.sh AGENT_BASE_DIR=/scratch/agent12c OMS_HOST=example.com EM_UPLOAD_PORT=14511 AGENT_REGISTRATION_PASSWORD=2bornot2b

    • When you pass the arguments while invoking the deployment script, these values need not be given with double quotes. However, when you provide them in a response file, the values need to be in double quotes (except for the argument b_startAgent).

    • In addition to passing the agent base directory and a response file (or individual mandatory arguments with installation details), you can also pass other options that are supported by the deployment script. For more information, see Understanding the Options Supported by the agentDeploy Script.


  4. Run the root scripts when you are prompted. For more information, see After You Install.

Installing Using RPM File

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

Download the RPM File onto the OMS Host

  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-4 shows a sample output of the command.

    Example 6-4 Output Showing Software Availability for Different Platforms

    ---------------------------------------------------
    Version = 12.1.0.2.0
    Platform Name = Linux x86-64
    ---------------------------------------------------
    Version = 12.1.0.2.0
    Platform Name = Oracle Solaris on x86-64 (64-bit)
    ---------------------------------------------------
    Version = 12.1.0.2.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, acquire and apply the Management Agent software for the required platform using Self Update.

    For information on how to acquire and apply the Management Agent software for a platform using Self Update, see Oracle Enterprise Manager Cloud Control Basic Installation 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-64" -version=12.1.0.2.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.2.0-1.0.i386.rpm

Transfer the RPM File to the Destination Host

  1. 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.

Install the Management Agent Using the RPM File

  1. On the destination host, install 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.2.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/oracle-agt RESPONSE_FILE=<location_to_agent.properties>
    

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

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

  3. Run the following command to complete the installation:

    /etc/init.d/oracle-agt RESPONSE_FILE=<location_to_agent.properties>

Creating a Response File for Installing Using AgentPull Script

Table 6-2 describes the various parameters you can include in the response file while installing a Management Agent using the AgentPull script.

Table 6-2 Creating a Response File for Installing Oracle Management Agent Using AgentPull Script

Parameter Description

LOGIN_USER

(Mandatory) Enter the Enterprise Manager console login user name.

For example, LOGIN_USER=sysman

LOGIN_PASSWORD

(Mandatory) Enter the Enterprise Manager console login password.

For example, LOGIN_PASSWORD=welcome1

PLATFORM

(Mandatory) Enter the platform for which you want to download the Management Agent software.

For example, PLATFORM="Linux x86-64"

Note: The value of this parameter must be in " ".

VERSION

(Optional) Enter the version of the Management Agent software you want to download.

For example, VERSION=12.1.0.2.0

If you do not specify this parameter, it is assigned the OMS version.

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 locked. 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.

For example, AGENT_REGISTRATION_PASSWORD=Wel456come

CURL_PATH

(For Microsoft Windows destination hosts only)

(Optional) Enter the absolute path of the installed cURL utility.

For example, CURL_PATH=c:\Program Files\curl

If you do not include this parameter, it is assigned the value c:\.


Creating a Response File for Installing Using agentDeploy Script

Table 6-3 describes the various parameters you must include in the response file while installing a Management Agent using the agentDeploy script.

Table 6-3 Creating a Response File for Installing Oracle Management Agent Using agentDeploy Script

Parameter Description

OMS_HOST

(Mandatory) Enter the OMS host name.

For example, OMS_HOST=example.com

EM_UPLOAD_PORT

(Mandatory) Enter the upload port (HTTP or HTTPS) for communicating with the OMS.

For example, EM_UPLOAD_PORT=14511

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 locked. 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.

For example, AGENT_REGISTRATION_PASSWORD=Wel456come

AGENT_INSTANCE_HOME

(Optional) Enter a directory location on the destination host where all Management Agent-related configuration files can be stored. For this parameter, you can do one of the following:

  • Leave it blank.

    In this case, by default, an instance directory titled agent_inst is created in the agent installation base directory.

    For example, if the installation base directory is /john/oracle/, then the instance directory is defaulted to /john/oracle/agent_inst

  • Enter the absolute path to a custom directory.

    Although you can enter any location as a custom location, Oracle recommends you to maintain the instance directory inside the installation base directory.

    For example, AGENT_INSTANCE_HOME=/john/oracle/instance_dir/inst_mydir

AGENT_PORT

(Optional) Enter a free port on which the Management Agent process should be started. The same port is used for both HTTP and HTTPS.

For example, AGENT_PORT=1832

If you do not enter any value, then either 3872 or any free port between 1830 and 1849 is honored.

b_startAgent

(Optional) Enter TRUE if you want the Management Agent to start automatically once it is installed and configured. Otherwise, enter FALSE.

For example, b_startAgent=TRUE

If you do not include this parameter, it defaults to TRUE.

ORACLE_HOSTNAME

(Optional) Enter the fully qualified domain name of the host where you want to install the agent.

For example, ORACLE_HOSTNAME=example.com

If you do not include this parameter, it defaults to the physical host name.

s_agentHomeName

(Optional) Enter the name of the Oracle home you want to see created for the Management Agent.

For example, s_agentHomeName=agent12cR2

If you do not include this parameter, it defaults to agent12cn, where n is 1 for the first Management Agent installed on the host, 2 for the second Management Agent installed on the host, and so on.

s_agentSrvcName

(Optional) Enter the customized Management Agent service name.

For example, s_agentSrvcName=agentsrvc1

If you do not include this parameter, it defaults to Oracle+<oracle_home_name>+Agent.

Note: If you upgrade a 12c Release 1 (12.1.0.1) Management Agent installed on a host to 12c Release 2 (12.1.0.2), and you want to install another Management Agent on the same host, ensure that you install the Management Agent after downloading the Management Agent software, and specifying the s_agentSrvcName parameter.


Creating a Response File for Installing Using an RPM File

Table 6-4 describes the various parameters you can include in the agent.properties response file while installing a Management Agent using a .rpm file.

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

Parameter Description

OMS_HOST

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

For example, OMS_HOST=example.com

OMS_PORT

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

For example, OMS_PORT=1835

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 locked. 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.

For example, AGENT_REGISTRATION_PASSWORD=Wel456come

AGENT_USERNAME

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

For example, AGENT_USERNAME=sysman

AGENT_GROUP

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

For example, AGENT_GROUP=group1

AGENT_PORT

(Optional) Enter the port used for the Management Agent process.

For example, AGENT_PORT=1832

If you do not enter any value, then either 3872 or any free port between 1830 and 1849 is honored.

ORACLE_HOSTNAME

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

For example, ORACLE_HOSTNAME=example.com


Understanding the Options Supported by the AgentPull Script

Table 6-5 lists the options supported by the AgentPull.sh script. On Microsoft Windows, these options apply to the AgentPull.bat file.

Table 6-5 Understanding the Options Supported by AgentPull.sh/AgentPull.bat

Option Description

-download_only

Only downloads the Management Agent software. Does not deploy the Management Agent.

-showPlatforms

Displays the platforms for which the Management Agent software is available on the OMS host. Does not install the Management Agent.

-help

Displays command line help and describes the usage of the AgentPull.sh script.


Understanding the Options Supported by the agentDeploy Script

Table 6-6 lists the options supported by the agentDeploy.sh script. On Microsoft Windows, these options apply to the agentDeploy.bat file.

Table 6-6 Understanding the Options Supported by agentDeploy.sh/agentDeploy.bat

Option Description

-prereqOnly

Runs only the prerequisite checks. Does NOT actually install the Management Agent.

This option is useful when you want to verify whether your environment meets all the prerequisites for a successful Management Agent installation.

-ignorePrereqs

Skips running the prerequisite checks. Use this when you have already used the -prereqOnly option and verified the prerequisites, and only want to install the software binaries.

-invPtrLoc

Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the oraInst.loc file that contains the location of the OraInventory directory.

Important: If you enter a value for this option, do NOT use the INVENTORY_LOCATION option. Also note that this parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

INVENTORY_LOCATION

Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the OraInventory directory.

Important:

  • If you enter a value for this option, do NOT use the -invPtrLoc option.

  • Do NOT use this option if you already have the /var/opt/oracle/oraInst.loc on HP and Solaris platforms, and /etc/oraInst.loc file on all other UNIX platforms.

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

-help

Displays command line help and describes the usage of the deployment script.

-debug

Logs more debug messages useful for debugging and resolving errors.

-ignoreUnzip

Skips extracting the software binaries of the Management Agent software. Use this when you do not want to copy the binaries again, but only want to configure the available binaries.

-softwareOnly

Installs only the software binaries, and does NOT configure the installation. Use this when you want to perform a software-only installation of the Management Agent. For more information, see Chapter 9.

Note: This option does not apply if you are cloning using a ZIP file.

-configOnly

Configures the software binaries, and does not install any software binaries. Use this when you have performed a software-only installation using the -softwareOnly option, so that only the configuration is done to the copied software binaries. For more information, see Chapter 9.

Note: This option does not apply if you are cloning using a ZIP file.

-forceConfigure

Forcefully configures the Management Agent even when the OMS is unreachable. Use this option only when you are installing the Management Agent before installing the OMS, and when you know for sure that you will install the OMS later on the same host and port mentioned for the parameters OMS_HOST and EM_UPLOAD_PORT, respectively, in the response file you pass.

If you pass this option, then do not pass -configOnly, -softwareOnly, and -prereqOnly.

Note: When you pass this option, the Management Agent is configured to use HTTP (non-secure) communication. To establish a secure HTTPS communication between the Management Agent and the OMS, you must manually secure the Management Agent after the OMS is available.


Understanding the Contents of the Downloaded Management Agent Software

Table 6-7 describes the contents of the core Management Agent software you download before installing the Management Agent using the agentDeploy script.

Table 6-7 Contents of the Downloaded Management Agent Software

Files Description

12.1.0.2.0_PluginsOneoffs_<platform id>.zip

Plug-in ZIP file containing all the discovering plug-ins, which were installed with the OMS, Oracle Home discovery plug-in, and Oracle Home monitoring plug-in.

agentcoreimage.zip

Archived ZIP file containing the core agent bits and agent set-uid binaries.

agentDeploy.sh/agentDeploy.bat

Script used for deploying the Management Agent.

unzip

Utility used for unarchiving the ZIP files.

agentimage.properties

Properties file used for getting the version, platform ID, and so on.

agent.rsp

Response file to be edited and passed for installing the Management Agent.


Understanding the Contents of the Management Agent RPM File

If you choose to install a Management Agent using the .rpm file, the .rpm file you download contains an agent base directory. Table 6-8 describes the contents of this agent base directory:

Table 6-8 Contents of the Agent Base Directory Present in RPM File

Element Description

core/12.1.0.2.0

Contains the Management Agent software.

sbin

Contains the Management Agent binaries.

plugins.txt

Response file specifying the plug-ins deployed on the Management Agent.

plugins

Contains the plug-in software.

agentimage.properties

Properties file used for getting the version, platform ID, and so on.

agent.properties

Response file to be edited and passed for installing the Management Agent.

oracle-agt

Management Agent configuration script.


After You Install

After you install the Management Agent, follow these steps:

  1. (Only for UNIX Operating Systems) Manually run the following scripts as a root user. If you do not have SUDO privileges, then request your Administrator who has the privileges to run these scripts.

    • If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

      For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

      $HOME/oraInventory/oraInstRoot.sh


      Note:

      If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

      /usr/bin/sudo $HOME/oraInventory/oraInstRoot.sh


    • Run the root.sh script from the Management Agent home:

      $<AGENT_HOME>/root.sh


      Note:

      If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

      /usr/bin/sudo $<AGENT_HOME>/root.sh



    Note:

    You do not need to run the oraInstroot.sh and root.sh scripts if you are installing a Management Agent using a .rpm file.

  2. Verify the installation:

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

      $<AGENT_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 its Oracle home:

      $<AGENT_INSTANCE_HOME>/bin/emctl start agent


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

      $<AGENT_INSTANCE_HOME>/bin/emctl upload

  3. 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/agent/core/12.1.0.2.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_BASE_DIR>/agent/core/12.1.0.2.0/perl/bin/perl <AGENT_BASE_DIR>/agent/core/12.1.0.2.0/bin/AgentPluginDeploy.pl -oracleHome <AGENT_BASE_DIR>/agent/core/12.1.0.2.0 -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>

    For example,

    /u01/agent/core/12.1.0.2.0/perl/bin/perl /u01/agent/core/12.1.0.2.0/bin/AgentPluginDeploy.pl -oracleHome /u01/agent/core/12.1.0.2.0/ -agentDir /u01/agent -pluginIdsInfoFile /u01/agent/plugins.txt -action configure -emStateDir /u01/agent/agent_inst

  4. If you had ignored a prerequisite check warning about wrong time zone settings, run the following command and follow the steps it displays:

    $<AGENT_INSTANCE_HOME>/bin/emctl resetTZ agent

  5. 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 must 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 Oracle Management Agents 12c Release 1 or 2 (12.1.0.x ) hang frequently or do not respond on Solaris 9ux and 10ux operating systems, then refer to document ID 1427773.1 on My Oracle Support.

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

    When you repoint your existing Management Agents to a new OMS, you cannot move the targets monitored by the Management Agents, the target history, and the Management Agent history. The monitored targets and the history data is lost.