Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 2 (12.1.0.2) Part Number E24089-17 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can install Oracle Management Agent (Management Agent) in silent mode. In particular, this chapter covers the following:
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:
To install a Management Agent using the AgentPull.sh
(AgentPull.bat
for Microsoft Windows) script, you must do the following:
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.
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.
To install a Management Agent using the agentDeploy.sh
(agentDeploy.bat
for Microsoft Windows) script, you must do the following:
Download the Management Agent software for the required platform onto the Oracle Management Service (OMS) host, using EMCLI.
Transfer the Management Agent software to the destination host where you want to install the Management Agent. Unzip the software.
Execute the agentDeploy.sh
(agentDeploy.bat
for Microsoft Windows) script on the destination host to install a Management Agent.
To install a Management Agent using the .rpm
file, you must do the following:
Download the .rpm
file onto the Oracle Management Service (OMS) host using EMCLI.
Transfer the .rpm
file to the destination host where you want to install the Management Agent.
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 installing a Management Agent in silent mode, keep these points in mind:
You can install a Management Agent on only one host at a time by using the silent methods. Therefore, use this approach when you want to install a Management Agent on only a few hosts.
The Management Agent software, for the platform on which the destination host is running, must be present on the OMS host. The Management Agent software contains the core binaries required for installation, the response file to be edited and passed, the agentDeploy.sh
script (agentDeploy.bat
for Microsoft Windows), and the oracle-agt
script.
By default, the OMS host contains the Management Agent software for the platform on which the OMS host is running. For example, if the OMS host runs on the Linux x86-64 platform, then the Management Agent software available by default on the OMS host is for the Linux x86-64 platform only.
If you want to install a Management Agent on a platform that is different from the platform on which the OMS is running, you must download and apply the Management Agent software for the required platform, using the Self Update console.
For information on Self Update and how you can use it to download and apply the Management Agent software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
By default, the OMS host contains the Management Agent software for the platform on which the OMS is running. For example, if the OMS host is Linux x86-64, then the Management Agent software available by default is only for Linux x86-64.
If you want to install the Management Agent on a platform that is different from the one on which the OMS is running, then download and apply the software for the desired platform using the Self Update console.
For information on Self Update and how you can use it to download and apply the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
You must run the agentDeploy.sh
(agentDeploy.bat
for Microsoft Windows) and AgentPull.sh
(AgentPull.bat
for Microsoft Windows) scripts only from the destination host.
You cannot run any preinstallation or postinstallation scripts as part of the installation process. Of course, you can run them manually after the installation ends.
By default, the agentDeploy.sh
script (agentDeploy.bat
on Windows), AgentPull.sh
script (AgentPull.bat
for Microsoft Windows), and the .rpm
file configures only the following types of plug-ins:
All discovery plug-ins that were configured with the OMS from where the Management Agent software is being deployed.
Oracle Home discovery plug-in
Oracle Home monitoring plug-in
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. |
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. |
|
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
|
|
cURL Utility (For installing using the |
Ensure that you install the cURL utility on the destination host. You can download the cURL utility from the following URL:
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 |
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. |
|
Ensure that the
|
|
Time Zone Requirements |
Ensure that the host time zone has been set correctly. To verify the host time zone, run the following command:
If the time zone displayed is incorrect, run the following commands, before running the
For example, in the Bash shell, run the following command to set the time zone to America/New_York:
The time zones you can use are listed in 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 Environment Variable Requirements (For installing using the |
(For Microsoft Windows) Ensure that the location of For example, if |
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. |
|
Unset the |
Port Requirements |
Ensure that the default ports described in What Default Ports Are Used? are free. |
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 |
|
/var/tmp Requirements (For installing using the |
Ensure that the |
/usr/lib/oracle Requirements (For installing using the |
Ensure that the |
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 If the agent base directory is mounted, then ensure that it is mounted with the |
Agent Instance Home Requirements (For installing using the |
Ensure that the agent instance home location you specify in the response file is empty. |
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. |
|
|
Agent User Account Permissions and Rights (For installing using the |
(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:
To verify whether the agent user has these rights, follow these steps:
|
(For installing using the |
(For Microsoft Windows) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that you grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
This section describes the actions involved in installing a Management Agent in silent mode. It consists of the following:
Creating a Response File for Installing Using AgentPull Script
Creating a Response File for Installing Using agentDeploy Script
Understanding the Options Supported by the agentDeploy Script
Understanding the Contents of the Downloaded Management Agent Software
This section explains the methods of installing a Management Agent in silent mode. It consists of the following:
To install a Management Agent using the AgentPull
script, follow these steps:
Download the AgentPull Script onto the Destination Host
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 theAgentPull.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.
(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
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.
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.
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.
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.
To install a Management Agent using the agentDeploy
script, follow these steps:
Download the Management Agent Software onto the OMS Host Using EMCLI
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
$<OMS_HOME>/bin/emcli sync
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, download and apply the software for the required platform using the Self Update console.
For information on Self Update and how you can use it to download and apply the software, refer to the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
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
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
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
Edit the response file agent.rsp
as described in Table 6-3.
<software_extract_location>/agent.rsp
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.
Run the root scripts when you are prompted. For more information, see After You Install.
To install a Management Agent using a .rpm
file, follow these steps:
Download the RPM File onto the OMS Host
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
$<OMS_HOME>/bin/emcli sync
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, download and apply the software for the required platform using the Self Update console.
For information on Self Update and how you can use it to download and apply the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
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
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
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>
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
Run the following command to complete the installation:
/etc/init.d/oracle-agt RESPONSE_FILE=<location_to_agent.properties>
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_PASSWORD |
(Mandatory) Enter the Enterprise Manager console login password. For example, |
PLATFORM |
(Mandatory) Enter the platform for which you want to download the Management Agent software. For example, 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, 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, |
CURL_PATH (For Microsoft Windows destination hosts only) |
(Optional) Enter the absolute path of the installed cURL utility. For example, If you do not include this parameter, it is assigned the value |
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, |
EM_UPLOAD_PORT |
(Mandatory) Enter the upload port (HTTP or HTTPS) for communicating with the OMS. For example, |
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_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:
|
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, If you do not enter any value, then either 3872 or any free port between 1830 and 1849 is honored. |
b_startAgent |
(Optional) Enter For example, If you do not include this parameter, it defaults to |
ORACLE_HOSTNAME |
(Optional) Enter the fully qualified domain name of the host where you want to install the agent. For example, 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, If you do not include this parameter, it defaults to |
s_agentSrvcName |
(Optional) Enter the customized Management Agent service name. For example, 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 |
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_PORT |
(Mandatory) Enter the upload port (HTTP or HTTPS) to communicate with the OMS. For example, |
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_USERNAME |
(Mandatory) Enter the user name with which you want to install the Management Agent. For example, |
AGENT_GROUP |
(Mandatory) Enter the group to which the Management Agent user should belong. For example, |
AGENT_PORT |
(Optional) Enter the port used for the Management Agent process. For example, 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, |
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 |
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 |
-invPtrLoc |
Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the Important: If you enter a value for this option, do NOT use the |
INVENTORY_LOCATION |
Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the Important:
|
-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 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 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. |
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. |
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 the Management Agent, follow these steps:
(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 theoraInstroot.sh
and root.sh
scripts if you are installing a Management Agent using a .rpm
file.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
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
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
If you had ignored a prerequisite check warning about wrong time zone settings, follow these steps:
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.
Deinstall the Management Agent present on the host.
For information on how to deinstall a Management Agent, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
Install a Management Agent on the host.
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 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.