Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 1 (12.1.0.1) Part Number E24089-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can install Oracle Management Agent (Management Agent) using its .rpm
file. In particular, this section covers the following:
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 installation base directory:
<installation_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
Before you begin installing a Management Agent, keep these points in mind:
Agent RPM is available only for Linux 32-bit and Linux 64-bit platforms.
You procure the Management Agent software from the OMS host and transfer it to the destination host for installation. The Management Agent software contains the core binaries required for installation, the response file to be edited and passed, and the configure.pl
script.
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, then the Management Agent software available by default is only for Linux x86.
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 the software for the desired 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.
You can install only on one host at a time, therefore use this approach when you want to install only on a few hosts.
You cannot run any preinstallation or postinstallation scripts as part of the installation process. Of course, you can run manually them after the installation ends.
By default, 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
You must not install two Management Agents on the same host. This disrupts the communication with the OMS.
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:
|
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. |
|
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. |
|
Permission Requirements |
Ensure that the agent base directory you specify in the properties file is empty and has write permission |
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. |
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 |
|
Installation Base Directory Requirements |
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 |
Permission Requirements |
|
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 |
|
To install a Management Agent using its .rpm
file, follow these steps:
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-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.
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
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.
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
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
Run the following command to complete the installation:
/etc/init.d/config.pl
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,
|
BASEDIR |
(Optional) Enter the absolute path to the installation base directory where you want to install the Management Agent. For example,
If you do not enter the path to the installation base directory, then by default, the Management Agent is installed in the following location:
|
ORACLE_HOSTNAME |
(Only for Virtual Hosts) Enter the virtual host name where you want to install the Management Agent. |
After you install the Management Agent, follow these steps:
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
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
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
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,
/home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/perl/bin/perl /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0 -agentDir /home/john/programs/oracle/EMGC_Main_20SH/agent -pluginIdsInfoFile /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /home/john/programs/oracle/EMGC_Main_20SH/agent/agent_inst
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.