The Oracle Management Agent, a process that is installed/deployed on each monitored host, is responsible for monitoring all targets on the host, for communicating that information to the Management Service, and for managing and maintaining the host and its targets. This chapter contains the following sections:
You can install/deploy the Management Agent on remote hosts using any of the following installation mechanisms:
Agent Deploy is a J2EE application that is used for mass deployment of Management Agents. See Chapter6, "Installing the Management Agent Using Agent Deploy" for more information.
This installation type uses the nfsagentinstall
script. In this method of the agent installation, the agent bits are located on a shared Net App Filer disk. All the other hosts then share these bits and run the agent processes on each host. See Chapter6, "Sharing the Agent Oracle Home Using the nfsagentinstall Script" for more information.
agentDownload Script
This installation type makes use of the agentDownload
Script that is fully functional and self-documenting. If required, you can customize this script for installations on specific environments. See Chapter6, "Installing the Agent Using the agentDownload Script" for more information.
Cluster Agent Installation
This type of installation allows you to perform a standalone agent installation on a selected cluster node, or perform a cluster agent installation on a selected cluster. See Chapter 8, "Deploying Cluster Agent" for more information.
Management Agent Cloning
This type of installation allows you to clone an installed agent (also referred to as the master agent) on multiple destination Oracle homes. See Chapter 9, "Management Agent Cloning" for more information.
Interactive Installation Using Oracle Universal Installer
This type of installation is appropriate for first-time Agent installations. You can perform this installation by invoking the installer using Oracle Universal Installer (OUI). The Interactive type is typically a one-node installation. See Chapter3, "Installing a Management Agent" for more information.
This type of installation is done using the appropriate response files. These response files must be edited to prefill the correct values for an uninterrupted installation. You can also use a wrapper script that will perform these tasks and also execute the root.sh
script (UNIX only), making this type of installation a fully automated activity. See Chapter4, "Enterprise Manager Silent Installations" for more information.
You can perform a mass deployment of the Management Agent through the Web-based Agent Deploy application. This application is particularly useful when you want to perform remote installations.
For information about patches to be applied before performing cross-platform Agent push, see Section 5.4 of the Agent Best Practice paper located at http://www.oracle.com/technology/products/oem/pdf/10gr2_agent_deploy_bp.pdf.
Note:
You can use the Agent Deploy application to mass-deploy the Management Agent from a remote site.When you are required to perform a standalone installation of the Agent on a local machine, you can choose to either perform the installation using the Agent Deploy application, or use the agentDownload
script. See the section Chapter6, "About agentDownload Script", for more information.
Note:
Oracle recommends that you view the installation status output (emctl status) to ensure the installation was successful. You can view this status by executing the following command:<AGENT_HOME>/bin/emctl status agent
See AppendixA, "Management Agent Installation Fails" to view a sample of the emctl status
log and to troubleshoot possible errors that may occur during installation.
Caution:
If you are deploying the Management Agent in an environment having multiple Management Service installations that are using a load balancer, you should not access the Agent Deploy application using this load balancer. Oracle recommends that you access the Management Service directly.Ensure the following prerequisites are met before proceeding with the agent installation.
Set up SSH (Secure Shell) User Equivalence.
Validate the path to all command locations.
Modify response file for Big IP host and port.
Verify oraInventory
permissions on remote hosts.
User installing the agent is part of the same operating system group that installed Oracle Application Server and/or Oracle Collaboration Suite.
See Appendix C, "Agent Deploy Application - Installation Prerequisites" for more information.
Note:
You can view the prerequisite checks and installation status from the Status screen in the Agent Deploy application.WARNING:
Do not attempt to view the prerequisite check status while the prerequisite checks are still in progress. If you do so while the checks are still in progress, the application will display an error.
To access Agent Deploy application, complete the following steps:
Log in to the Grid Control console and go to the Deployments screen.
Click Install Agent under the Agent Installation section.
In the Agent Deploy home page that appears, select the appropriate installation option that you want to perform.
Note:
If you want to view the status of an earlier installation/upgrade session, click Agent Installation Status in the Deployments screen.Agent Deploy provides the following two options for deploying the Management Agent:
Note:
You can view the installation status from the Status screen in the Agent Deploy application.WARNING:
Do not attempt to view the installation status until the installation is complete. If you do so while the installation is still in progress, the application will display an error.
This option helps you perform a new installation of the Management Agent. The Agent Deploy application runs a prerequisite checker to ensure the environment meets the requirements for this installation type. See AppendixC, "Prerequisite Checks Executed by Agent Deploy" for more information.
To perform a new Management Agent installation, complete the following steps:
Select Fresh Install on the Agent Deploy application home page. The Installation Details screen appears.
In the Source Software section, select an installation source directory. This directory can either be the default directory that exists within the Oracle Management Service (OMS), for example <OMS_HOME>/sysman/agent_download/10.2.0.2.0/<platform>
, or any other location where the software is available.
Note:
At the time of downloading the agent installation software, if theagentDownload.rsp
file is overwritten, ensure the s_OMSHost
and s_OMSPort
values are specified correctly in the response file (agentdownload.rsp
) before proceeding with the installation steps.See Chapter6, "Downloading 10.2.0.3.0 Agent Installation Software for Different Platforms" for more information on obtaining agent binaries for different platforms.
To choose a location other than the default location from the Management Service, select Another Location, and specify the full path to the software location that you want to use.
Note:
Ensure that the path of the software location that you specify is accessible from all remote hosts.The application does not copy the software to the remote hosts, but will only access the software from the specified location.
After you download the agentDownload software, unzip and extract its contents into a new directory. Rename this new <directory>/$<platform>/agent
to <directory>/$<platform>/Disk1
and use the <directory>/$<platform>
as the source software location.
Caution:
The additional parameters that you specify later in the installation process depend on the source software location that you select here.if you select the default software location, you must specify additional parameters that are supported by the agentDownload
script. See Table D-1, "Parameters Supported by agentDownload Script" for a list of parameters supported by this script.
If you select an alternative location, you must specify additional parameters that are supported by Oracle Universal Installer (OUI). See Table D-2, "Parameters Supported by Oracle Universal Installer" for a list of parameters supported by OUI.
In the Version section on this screen, select the appropriate version of the agent that you want to install. The values available in this list will depend on the staged software that are available on the Management Service host.
Select the appropriate platform on which you want to perform this installation.
In the Hosts section, do the following:
Select the appropriate platform on which you want to perform this installation.
In the Provide Host List text box, specify all the hosts (host names or IP addresses) on which you want to perform the agent installation. Alternatively, click Get Host Names From File to browse and select the file that contains a list of all the required host names.
WARNING:
Ensure you do not specify duplicate entries of the host list. If there are duplicate host entries in this list, the application hangs.
Also ensure that you use the same host names for which the SSH has been set.
Note:
You can use either a comma (,) or a new line as a separator when specifying multiple hosts.Caution:
The Agent Deploy application picks up only the values in the first column of the Host List file that you specify/select.Ensure the host list format is appropriate, because the Agent Deploy application does not validate this format on the selected file.
A sample host list format is provided in Table 6-1, "Sample Host List Format".
Note:
For Enterprise Manager 10.2.0.1 and 10.2.0.2, use the ÒPopulate DetailsÓ button to populate the cluster node list or provide a comma-separated list.Select Cluster Install if you want to install the Agent on a cluster.
In the Cluster Node List text box, specify the cluster nodes. Alternatively, click Populate Defaults to populate this text box with all the host names that you had selected in step b.
Note:
The node names that you specify here are the machine short names.If you have set up the cluster over a vendor clusterware, the node names can be different from the machine names.
You can confirm the node names by executing olsnodes
from the <Oracle Clusterware home>
on one of the cluster nodes. If you are using Oracle Cluster release 9.2, confirm the node names by executing lsnodes
from the cluster Oracle home.
See Chapter8, "Installing the Agent on Oracle Clusterware" for more information.
In the Cluster Name text box, specify a unique cluster name. If you are extending a cluster, specify the existing cluster name here. The cluster name that you specify here identifies that cluster in the Grid Control console.
Note:
When you select the cluster installation option, Agent Deploy performs the agent installation only on those cluster nodes that you have specified, irrespective of the number of hosts that make up that cluster.For example, if you choose to perform a cluster installation on a cluster having 10 nodes, but specified only 5 nodes, Agent Deploy installs the agent only on the 5 nodes of the cluster that you have specified.
If you are extending an existing cluster, ensure that the cluster name you specify is the same as the existing cluster. You must also specify all the nodes of the existing cluster along with the new node on which you are installing the cluster agent.
In the OS Credentials section, specify the appropriate operating system user credentials. Select Run root.sh (on UNIX machines only) if you want Agent Deploy to execute this script.
Note:
Theroot.sh
script executes after the configuration assistants are run, and before executing postinstallation scripts (if any).
If you do not select this option here, you must manually run root.sh
on each node.
Agent Deploy uses sudo
to run this script. You must specify the invoking user's password here. You must also ensure that the targetpw
is not set in the /etc/sudoers
file.
Note:
The OS credentials that you specify here must be the same for all the selected hosts.In the Destination section, specify the absolute path for the Installation Base Directory. This directory is created on all the specified hosts, and the Agent Oracle home directory is created as a subdirectory under this directory.
Note:
For the Agent push to be successful, ensure that you extract the agentDownload kit before performing the Agent push.Note:
Ensure you have write permissions on the installation Base Directory that you specify.Specify the port on which the Agent will communicate. The default port value for 10.2 Management Agent is 3872.
Note:
If the port that you specify is not available, you are prompted to specify an alternative port. If you do not specify a port here, the Agent Deploy application automatically picks up a free port (3872 or in the range of 1830 - 1849).In the Additional Parameters text box, specify any additional parameters that you want to pass during installation.
Caution:
The additional parameters that you specify here depend on the software source location that you have selected.Default Management Service Location: If you have selected the default software source directory, the additional parameters that you specify must be supported by the agentDownload
script, as the Agent Deploy application uses the agentDownload.<platform>
script to perform the installation. See Table D-0, "Additional Parameters Supported by agentDownload Script" for a list of all the parameters supported by the agentDownload
script.
Another Location: If you have selected an alternative software location, the additional parameters that you specify must be supported by Oracle Universal Installer (OUI), as Agent Deploy then uses OUI to perform the installation. See Table D-1, "Additional Parameters Supported by Oracle Universal Installer" for a list of parameters supported by OUI.
Note:
If the same parameters that you specify here are also specified independently (from the command-line option), the value of the parameters that you specify here take precedence over the other.For example, if the installation base directory is specified independently, and -b
option is specified here, the latter value (-b
) is used in the installation.
The important parameters for Agent Installation are -b, -c, -n
, -z
and optionally -i, -p, -t, -d
.
Specify the Management Service Registration Password if you want to secure communications between the agent and Management Service. Alternatively, the super administrator can approve the addition of new agents to Enterprise Manager after the installation is complete.
Note:
An unsecure agent cannot upload data to the secure Management Service. Oracle also recommends for security reasons that you change the Management Service password specified here after the installation is complete.In the Additional Scripts section, specify any preinstallation and/or postinstallation scripts that you want to execute.
Select Run as Superuser if you want to run these scripts as root
.
Note:
The preinstallation and/or postinstallation scripts that you specify must be available on all the hosts. These files are not copied onto the hosts from the software source location during installation.Click Continue to start the installation process. As part of this process, Agent Deploy performs some prerequisite checks before proceeding with the installation. When all the prerequisite checks are complete, the application displays the results. You can choose to either retry the prerequisite check on all those failed hosts, or ignore the result and proceed to install the Agent.
Note:
After the installation and configuration phase, the Agent Deploy application checks for the existence of the Central Inventory (located at/etc/oraInst.loc
). If this is the first Oracle product installation, Agent Deploy executes the following scripts:
orainstRoot.sh
- UNIX Machines only: This creates oraInst.loc that contains the central inventory.
root.sh
- UNIX Machines only: This runs all the scripts that must be executed as root
.
If this is not the first Oracle product installation, Agent Deploy executes only the root.sh
script.
Note:
For more information on the prerequisites check, installation, and configuration logs that are created, see AppendixF, "Agent Deploy Log Files".Consider the following scenarios while performing cluster installation:
You are performing a new Agent installation on a cluster that does not have an Agent.
This is a scenario where you have an existing cluster (cr1
with three nodes n1, n2, and n3) but without an agent installation on any of the nodes. Here, if you specify only two nodes (n1 and n2) for an agent installation, Agent Deploy updates the inventory for these two nodes and the agent is installed and running.
Now, you want to install the agent on the third node (n3) and specify the cluster name as cr1
and all three hosts and nodes (n1, n2, and n3) this time. Agent Deploy updates the n1 and n2 inventory to include n3 and the agent is installed.
Caution:
In a scenario such as the one above, you must specify the same cluster name and include all the existing nodes of that cluster.You are extending a cluster, but do not include all the existing nodes.
This is a scenario where you want to install an agent on the node (n4) that is an extension of the existing cluster (cr1 with nodes n1, n2, and n3.) But during the agent installation, you specify only the new node (n4) in the Cluster Node List text box. Agent Deploy installs the agent on n4, but does not update the inventory of the other three nodes (n1, n2, and n3) to include n4.
To ensure that the inventory of all the nodes of an existing cluster are updated, you must specify all the hosts and nodes of that cluster along with the new node (n4 in this example.)
If you have specified just the one node and the existing cluster name (cr1), Agent Deploy still creates a new cluster with the same name.
If you have specified just the one node and did not specify a cluster name, Agent Deploy computes a default cluster name and create a new cluster.
You are installing the Agent on two clusters of the same name, but with different nodes.
You have two clusters with the same name but with different nodes, for example crs
(with n1, and n2) and crs
(with n3 and n4), and you want both clusters to be managed by the same OMS. To distinguish the two clusters in the Grid Control console, you must do the following:
When you are installing the agent on the first crs
cluster (with nodes n1 and n2), enter a unique cluster name and perform the installation. Now, enter a different cluster name for the other crs
cluster (with nodes n3 and n4) and perform the Agent installation.
Now, you can view these clusters in the Grid Control console under unique cluster names that you specified during agent installation.
To deploy and install an agent on multiple hosts using an existing Shared Agent Installation, you must have already performed a complete Enterprise Manager product installation (including the agent). Another prerequisite when using this option is that the directory where the agent is installed should be NFS-mounted, meaning the directory must be a shared location on all remote hosts.
The Agent Deploy application runs a prerequisite checker to ensure the environment meets the requirements for this installation type. See AppendixC, "Prerequisite Checks Executed by Agent Deploy" for more information.
Caution:
NFS agent deployment is not supported on a cluster. If you want the agent to monitor a cluster and Oracle RAC, you must use the agent deployment with the cluster option, and not the NFS (network file system) deployment method.Note:
You can also perform a Shared Agent Oracle home installation using thenfsagentinstall
script. See Chapter6, "Sharing the Agent Oracle Home Using the nfsagentinstall Script" for more information.The following sections briefly discuss the shared agent home concepts, and also list the prerequisites before starting the installation.
This is a directory for storing configuration files such as emd.properties
, targets.xml
, log files
, and so on, on each host. Every host that shares the agent binaries has its own EMSTATE
directory.
The EMSTATE
directories of agents on different hosts should be local to the host instead of on the mounted drive, for security reasons.
Since the EMSTATE
directory contains the targets pertaining to each host, it is highly recommended to have it on a local host.
The initial space required for EMSTATE
directories is 1 MB. Since all the upload files, collection files, and log files are stored in this directory, the size of the directory will increase. Consequently, Oracle recommends that you allocate sufficient space for the EMSTATE
directories after taking these factors into account.
Currently, no packages are required by the agent to run on the shared hosts.
When you are performing an agent installation using a shared Oracle home, ensure all the specified hosts have the same operating system credentials and file system structure, including the following:
Same User names and Group names
Same user identifiers (UID) and group identifiers (GUID)
This is important for the agent from the remote host (NFS-mounted) to execute certain programs (for example, ORACLE_HOME/bin/nmo
) that are otherwise not accessible to other users.
To perform a new Management Agent installation:
Select Shared Agent Home on the Agent Deploy application home page. The Installation Details screen appears.
In the Hosts section:
Select the appropriate Platform on which you want to perform this installation.
In the Provide Host List text box, specify all the hosts (host names or IP addresses) on which you want to perform the Agent installation. Alternatively, click Get Host Names From File to select the file that contains a list of all the required host names.
WARNING:
Do not specify duplicate entries of the host list. If there are duplicate host entries in this list, the application hangs.
Use the same host names for which the SSH has been set.
Note:
You can use a comma (,) or just white space as a separator when specifying multiple host names.Caution:
If the Installation Base Directory is shared among the hosts that you have specified in the host list, the installer is invoked from one of these hosts (typically, the first host in that list).While the installation is performed on only one host, the application executes the configurations on all nodes in the list. That is, the preinstallation, postinstallation, and collect logs are executed on all the nodes.
After the installation is complete, the Installation Status screen displays the status of only this host (from which the installer was invoked). It may not necessarily list the status of all the hosts specified in the host list.
In the OS Credentials section:
Specify the appropriate operating system user credentials.
Select Run root.sh (on UNIX machines only) if you want Agent Deploy to execute this script. Agent Deploy uses sudo
to run this script. You must specify the invoking user's password here. You must also ensure that the targetpw
parameter is not set in the /etc/sudoers
file.
Caution:
If you do not want to execute the scripts as root during the installation, ensure you run these scripts manually before performing any other installation on that machine.Note:
The OS credentials that you specify here must be the same for all the selected hosts.In the Destination section:
Specify the complete path to the NFS Agent Location. This is the shared directory location on the source agent host that must be visible (NFS-mounted) from all remote hosts.
Specify an appropriate EMState Directory Location. This is a directory for storing configuration files such as emd.properties
, targets.xml
, log files
, and so on, on each host. Every host that shares the agent has its own EMSTATE
directory.
In the Port section, specify the appropriate port on which the agent will communicate. This is a mandatory field.
Note:
If the port that you specify is busy (not available), you are prompted to specify an alternative port. If you do not specify a port value here, the installation will fail.In the Additional Parameters section, specify the parameters that you may want to pass during installation. You can specify multiple parameters, separated by a space.
Note:
Besides the timezone parameter (-z
), you can also specify all the parameters that are supported by the agentDownload script. See AppendixD, "Additional Parameters Supported by agentDownload Script" for more information.In the Management Server Security section:
Specify the Management Service Registration Password if you want to secure communications between the Agent and Management Service. Alternatively, the super administrator can approve the addition of new agents to Enterprise Manager after the installation is complete.
Note:
An unsecure agent cannot upload data to the Management Service. Oracle also recommends for security reasons that you change the Management Service password specified here after the installation is complete.In the Additional Scripts section:
Specify any preinstallation and/or postinstallation scripts that you want to execute. These scripts are optional. If you do not want to customize your installation, leave these fields blank and continue.
Click Continue to start the installation process.
Caution:
If the shared agent is the first Oracle product that is installed on the host, you must execute the following command from theEMSTATE
directory after completing the installation:
<EMSTATE Dir>/bin ./emctl control agent runCollection <Host name>:host Inventory
As part of this process, Agent Deploy performs some prerequisite checks before proceeding with the installation. When all the prerequisite checks are complete, the application displays the results. The results include the name, type, and status for all prerequisite checks designed for the installation.
Besides the successfully run prerequisite checks, the prerequisite checks can return either one of the following messages:
Warning: If there are warnings against certain prerequisite checks, you may choose to ignore these and continue with the installation (though this is not recommended).
Failed: If there are failed prerequisite checks, you cannot continue with the installation. A recommended course of action is to fix the failed prerequisites before proceeding with the installation.
To fix the failed prerequisites, you can either click Retry, or go to the Fixup screen of the application. The Fixup screen displays the prerequisites that can be automatically fixed, and those that require manual fixes.
Note:
You can view the status of all previous installation instances from the Status screen in the Agent Deploy application. This screen lists all agent installations that were performed using Agent Deploy. You can click the corresponding Status link for each record to view the selected installation details, including user input provided during installation and the final status of that installation.You can access the Status screen either before starting the installation process, or after the installation is complete. You cannot access the Status screen during an installation.
The Enterprise Manager release 10.2 installer supports NFS-mounted agent installations where the agent bits are shared on a Net App Filer disk, and the other hosts share these binaries to run the agent processes on each of the hosts. In this method of agent deployment, the configuration files for each host are stored in the EMSTATE
directory.
Note:
The agent Oracle home cannot be installed in an Oracle Cluster Shared File System (OCFS) drive, but is supported on an NAS (Network Attached Storage) drive.Caution:
You can perform only one nfsagent installation per host. Multiple nfsagent installations on the same host will fail.Consider the following before starting the agent installation using the nfsagentinstall
script.
The shared agent (nfsagent) can be installed only with the same user credentials that were used to perform the master agent installation.
If this shared agent installation is not the first Oracle product installation and your home directory (of the master agent installation) is shared, you must verify the oraInst.loc
location under the /etc
directory.
If oraInst.loc
and inventory_loc
are located in the your home directory, you must change this entry point to a non-shared location.
The oraInst.loc
entry should look like this:
inventory_loc=/<any location other than the home directory>/oraInventory inst_group=<group to which the user belongs>
To perform an agent installation using nsfagentinstall
script, complete the following steps:
Configure the shared drive on the host in such a way that only one host has read/write access to this shared location, while all the other hosts have only read access.
From the host that has read/write access, perform an agent installation in the shared Oracle home location. You can use any agent deployment method. This installation is called as the master agent installation.
Stop the Agent from the Oracle home.
Note:
You must not start the master agent from the installed Oracle home.Now, execute the OH/sysman/install/nfsagentinstall
script on all the hosts that should share the agent binaries, including the host on which you performed the master agent installation.
If this agent installation is the first Oracle product installation on the host, the nfsagentinstall
script prompts you to execute the following script (on UNIX machines only). You must execute this script manually.
<homedir>/oraInventory/orainstRoot.sh
The nfsagentinstall
script also prompts you to execute the <STATEDIR>/root.sh
command. You must manually execute this command.
Note:
For NFS Agent installation from 10.2.0.3.0 master agents, the NFS agents will be started automatically after rebooting the machine.Note:
For NFS Agent installation from 10.2.0.3.0 master agents, agentca script for rediscovery of targets present in the <statedir>/bin directory can be used to rediscover targets on that host../nfsagentinstall -s <EMSTATE Directory location> -p <port number>
In the preceding command syntax,
<EMSTATE Directory location> is the full path where you want the state directory to be created by the script.
<port number> is the port on which the agent runs.
Note:
Specifying the <port_number> argument is optional. If you do not specify the port number, the script will automatically select the next available port from that host.Caution:
If the nfsagent is the first Oracle product that is installed on the host, you must execute the following command from theEMSTATE
directory after completing the installation:
<EMSTATE Dir>/bin ./emctl control agent runCollection <Host name>:host Inventory
Note:
Deployment of agent through the nfsagent install script is not supported on clusters. If you want the agent to monitor a Cluster and/or Oracle RAC, you must use the agent deployment with cluster options.If the nfsagent you want to deinstall is the only Oracle product installed on the host, you must check the /etc/oraInst.loc
directory for the inventory location and perform the following steps to deinstall the agent:
Stop the agent using the following command:
<EMSTATE DIR>/bin/emctl stop agent
On Microsoft Windows, you must delete the agent service by executing the following command:
nmesrvops delete <service name>
Execute rm -rf <inventory_location>
Execute rm -rf <EMSTATE Dir>
If the nfsagent you want to deinstall is not the only Oracle product installed on the host, then go to the master agent Oracle home (using the mounted path) and perform the following steps to deinstall the agent:
Stop the agent using the following command:
<EMSTATE DIR>/bin/emctl stop agent
On Microsoft Windows, you must delete the agent service by executing the following command:
nmesrvops delete <service name>
Execute the following command from the master agent Oracle home:
<master agent home>/oui/bin/runInstaller -detachHome ORACLE_HOME=<master agent home>
Execute rm -rf <EMSTATE Dir>
This installation type makes use of the agentDownload
script that is fully functional and self-documenting. The downloadable Agent software contains a sample script called agentDownload
. This script provides a means for installing Management Agents that can be customized for specific environments using a silent, scripted installation.
The agentDownload
script uses the pull technology for agent installations. That is, though the script is not required to exist on a local file system, it must always be executed from the target host computer. You must be logged in to the target host to run the script. Files are not pushed from a central location to a list of target hosts. Instead, files are pulled to the local $ORACLE_HOME
from the staged product installation location.
This means that the agentDownload
script needs to be launched from each target host where you want to install the Management Agent. As the installation is scripted, it is possible to use a wrapper script, Linux cron
job, rdist
, or a combination of operating system features to fully automate this process for mass deployments.
Note:
Use theagentDownload
script to perform an agent installation on a cluster environment. See Chapter6, "Cluster Installation" for more information.The download script deploys the standard Management Agent installation with some additional benefits:
Can be modified for specific user environments.
Noninteractive, silent, installations.
Output is text-only (nongraphical).
Management Agents installed using the script are identical to Management Agents installed with the Oracle Universal Installer graphical installation.
Simplifies deploying Management Agents in secure Web environments that are configured to provide HTTP access.
Provides useful installation options using the command line (including the ability to control target autodiscovery, autostarting of the agent, and so on).
Allows installation onto clustered environments.
The downloadable Agent software for the operating system of the Management Service platform is available on the platform-specific CD from which the Management Service was installed, and from the Oracle Technology Network Web site under Mass Agent Deployment at
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
See Chapter6, "Downloading 10.2.0.3.0 Agent Installation Software for Different Platforms" for more information on obtaining agent installables for different platforms.
The agentDownload
script is downloaded to a target node and executed to initiate a silent Oracle Universal Installer session. The agent files are copied from the staging area in the Management Service home to the target node through HTTP.
To deploy multiple Management Agents using the agentDownload
script, you must do the following:
Install Oracle Management Service.
Install the Management Service using Oracle Universal Installer. See Chapter3, "Installing an Additional Management Service" for more information.
See Also:
Oracle Enterprise Manager Advanced Configuration for more information about the directory structure of a typical Management Service installationThe download stage for the Management Service platform is installed with the Management Service. For example, for Linux operating systems, the download stage can be found in:
OMS_HOME/sysman/agent_download/<version>/linux
The agentDownload
script is located at OMS_HOME/sysman/agent_download/<version>/linux
For example, for Enterprise Manager 10g R2, the <version>
value in the preceding syntax will be 10.2.0.2.0
The response file is located at OMS_HOME/sysman/agent_download/<version>
Caution:
If the Management Service is using a load balancer, you must modify thes_omsHost
and s_omsPort
values in the <OMS_HOME>/sysman/agent_download/<version>/agentdownload.rsp
file to reflect the load balancer host and port before using the agentDownload
script.Note:
For Enterprise Manager 10g R2, the<version>
value in the preceding syntax will be 10.2.0.2.0
.The readme file is available at OMS_HOME/sysman/agent_download
.
Download the agentDownload
script to the target host from the Management Service URL.
The Management Service installation creates a Web server alias called agent_download
that maps to a physical directory in the Oracle Application Server home directory where the Management Service is installed and deployed. For example, if you installed the Management Service on a host named mgmthost27.acme.com, you could access the following URL from a browser:
http://mgmthost27.acme.com:4889/agent_download/10.2.0.2.0/<platform>
Note:
The default port for Grid Control is 4889. This should be available after you install the Management Service.Using this Web server alias, you can download the script to the target host computer using the following URL. Save the script locally as agentDownload
.
http://mgmthost27.acme.com:4889/agent_download/10.2.0.2.0/<platform>/agentDownload.<OS>
The <OS>
argument represents the operating system platform. For example, for Linux operating systems, the script is named agentDownload.linux
. For Windows operating systems, the script is named agentDownload.vbs.
On Microsoft Windows, the URL to download the script would be as follows:
http://mgmthost27.acme.com:4889/agent_download/10.2.0.2.0/win32/agentDownload.vbs
Note:
You can also access theagentDownload
script from the command line by executing the following command:
wget http://mgmthost27.acme.com:4889/agent_download/10.2.0.2.0/<platform>/agentDownload.<OS>
or
wget http://mgmthost27.acme.com:4889/agent_download/10.2.0.2.0/win32/agentDownload.vbs
Any method of retrieving the file is acceptable: cp, rcp, scp, FTP, and so on. The script can also be retrieved by opening a browser window on the target machine and saving the link to a local file.
Note:
If you want to download using a file-based protocol rather than HTTP, you need to modify the$AgentDownload
URL variable to access the file system on the Management Server host instead of a URL.The URL is the following:
http://${OMShost}:${httpPort}/agent_download/
is a Web alias for:
$OMS_HOME/sysman/agent_download/
Execute the agentDownload
script on the target host.
Before launching the script, ensure the following:
The execute binary is set and the script file has the proper file protection settings (use chmod
to ensure the file has the correct privileges).
The base directory is specified at the command line. This will be the location of the Management Agent home on the target host. If the directory does not exist, it is created during the installation. If it exists, ensure it is empty. If the variable is not set, the script exits with an error.
Note:
The base directory for the agent installation must be specified using the-b
option. For example, if you specified the parent directory to be agent_download
(/scratch/agent_download
), then the command to be specified is:
-b /scratch/agent_download
The agent Oracle home (agent10g
) is created as a subdirectory under this parent directory.
The wget
(or other file transfer mechanism) has been defined in the script. The script checks for the existence of wget
in /usr/local/bin/wget
, followed by /usr/bin/wget
. If wget is not found in either of those locations, then it must be included in the $PATH
or the script will exit with an error.
The $AGENT_INSTALL_PASSWORD
environment variable is set in the environment if the Management Agent is uploading to a secure and locked Management Service.
Caution:
The agent that you are installing is not secure by default. If you want to secure the agent, you must specify the password using the AGENT_INSTALL_PASSWORD environment variable, or by executing the following command after the installation is complete:<Agent_Home>/bin/emctl secure agent
Note:
For Enterprise Manager 10.2.0.3.0, if the agent_download.rsp file does not contain the encrypted registration password or the AGENT_INSTALL_PASSWORD environment variable is not set, the agentDownload script in UNIX will prompt for the Agent Registration password which is used for securing the agent. Provide the password to secure the agent. If you do not want to secure the agent, continue running the agentDownload script by pressing Enter.See Also:
Oracle Enterprise Manager Advanced Configuration for more information on enabling security for Enterprise Manager componentsThe script user has the necessary file access permissions for the Management Agent home directory.
After the Management Agent installation is complete, change the directory to the Agent home directory and run the root.sh
script (on UNIX machines only) as the root
user.
For example:
$PROMPT>su root
Password: root_password
#./root.sh
#exit
$PROMPT>
The root.sh
script must be run as root
; otherwise, the Enterprise Manager job system will not be accessible to the user. The job system is required for some Enterprise Manager features, such as hardware and software configuration tasks and configuring managed database targets.
The agentDownload
script can be used to install Management Agents onto clustered environments. In order to perform this type of installation, the command-line options to be used are listed in Table 6-2.
Table 6-2 Command-Line Options for Cluster Installation
Options | Description |
---|---|
-c |
This option is followed by a comma-separated list of the nodes in the cluster. It is possible to install a standalone agent that will still discover cluster targets by not specifying this option, while still specifying the cluster name with the |
-n |
This option is followed by the name of the cluster. This option is required for Oracle9i clusters; for Oracle Database 10g clusters, if this option is not specified, the default cluster name from the |
-l |
This option specifies that the installation should be done just on the local node of the cluster. |
For example, to use the agentDownload
script to install a Management Agent on just the local node of a cluster that consists of nodes host1, host2, and host3, with cluster name myCRS, you must execute the following:
./agentDownload.<platform> -b <name of the Oracle Homes> -m <fully-qualified Oracle Management Service host name> -r <Oracle Management Service ports> -c "host1,host2,host3" -n myCRS -l
For example for Linux operating system, the command would be as follows:
./agentdownload.linux - b /oracle/agentinstall -m foo.us.oracle.com -r 4889 -c "host1,host2,host3" -n myCRS -l
The agentDownload
script performs the following actions:
Creates home directories for the Management Agent and Oracle Universal Installer if they do not exist, based on the $ORACLE_HOME
path specified through the command line.
Downloads the agent_download.rsp
response file from the Management Service Web server.
The Management Service instantiates the response file with the name and port number of the Management Service. As a result, the Management Agent you install is configured to use the Management Service from which the response file was downloaded.
Downloads an Oracle Universal Installer JAR file for the target operating system from the Management Service Web server (for UNIX only).
Extracts Oracle Universal Installer and points it to the product definition file (products.xml
) hosted by the Management Service Web server.
Starts Oracle Universal Installer in silent mode from the local machine; Universal Installer pulls files from the Web server to the target machine via HTTP.
Note:
This script uses the-ignoresysPrereqs
flag to bypass prerequisite check messages for operating system-specific patches during installation; prerequisite checks are still performed and saved to the installer logs. While this makes the Management Agent easier to deploy, check the logs to make sure the target machines on which you are installing Management Agents are properly configured for successful installation.The resulting installation and configuration, including the automatic discovery of managed targets on the Management Agent host, is identical to that provided by the Management Agent installation on the Enterprise Manager DVD set.
The agentDownload
script creates a log file in the base directory that is specified using the -b
option.
At the end of a successful installation, the Agent starts and should begin successfully uploading to the Management Service, presuming automatic discovery and automatic start were not disabled at the command line.
To run the script, use the following command:
./agentDownload.<platform> [-bcdhilmnoprtuxN]
For Linux operating system, the command would be as follows:
./agentDownload.linux [-bcdhilmnoprtuxN]
The descriptions of the script options are listed in Table 6-3.
Table 6-3 AgentDownload Script Options
Option | Description |
---|---|
-b |
To specify base directory of the Agent Oracle home. |
-c |
To specify the cluster nodes (CLUSTER_NODES) Note that there should not be any spaces between the entries in the comma-separated nodes list. |
-d |
Do not automatically discover targets during installation. Host target will be created as needed. |
-h |
To display and describe the options that can be used with this script. |
-i |
To specify the inventory pointer location file: Can be used to point the installer to a nondefault inventory. (For advanced users only.) |
-l |
To specify as local host (pass -local to runInstaller) |
-m |
To specify the Oracle Management Service host name for downloading the agent install. |
-n |
To specify the cluster name. |
-o |
To specify the OLD_ORACLE_HOME during upgrade |
-p |
To specify static port list file. |
-r |
To specify the port for connecting to the Oracle Management Service host name. |
-t |
Do not automatically start the agent at the end of the installation. |
-u |
To upgrade. |
-x |
To debug output: Turns on shell debugging. |
-N |
Do not prompt for Agent Registration Password. |
You can edit the contents of the agentDownload
script so it uses a specific tool for transferring files from the Management Service Web server. The contents of the file contain instructions for doing so, as shown in the following example:
WGET="/usr/local/bin/wget --dot-style=mega --verbose --tries=5"
InstallerDownloadCmd=$WGET # Define the command to be used to download the jarred installer from # the web server hosting the OMS. # Other download possibilities: ftp; cp/scp; use local browser to save the # link to a file on the target machine. # This example uses wget, a GNU tool for http and ftp file transfers. # If the products.xml referenced by the Oracle Installer is a URL, then the # Installer will download its files via http. This greatly facilitates # performing installs in a secure environment that may include firewalls # and servers with limited access (no ftp server, NFS mounts not available, # etc.). # Enterprise Manager version number. This is used to construct the # home name used by the installer
GNU wget
is available for most platforms and can be downloaded from the following location:
http://www.gnu.org/software/wget/wget.html
To obtain the agent download for other platforms, you must complete the following steps to make the Management Agent installable from the Management Service Oracle home.
To Obtain agentDownload for Unix
Follow the instructions below to download the agent installation software for Unix:
Download the <platform>_Grid_Control_agent_download_10_2_0_3.
zip
file from OTN:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
Copy the downloaded file to the <OMS_HOME>/sysman/agent_download/10.2.0.3.0
directory.
Note:
Create the<OMS_HOME>/sysman/agent_download/10.2.0.3.0
directory, if it does not exist.Go to this directory by executing the following:
cd <OMS_HOME>/sysman/agent_download/10.2.0.3.0
When you are here, confirm that the size and checksum calculation of the downloaded file match the information specified on the OTN download page.
Execute the following command:
unzip <platform>_Grid_Control_agent_download_10_2_0_3.zip
If the agent_download.rsp file does not exist in the <OMS_HOME>/sysman/agent_download/10.2.0.3.0
directory, do the following:
Execute mv agent_download.rsp.bak agent_download.rsp
Edit agent_download.rsp and modify s_OMSHost="REPLACE_WITH_OMS_HOST"
and s_OMSPort="REPLACE_WITH_OMS_PORT"
variables with the correct OMSHost and OMSPort values. For example:
s_OMSHost="foo.us.oracle.com" s_OMSPort="4889"
Note:
Even if you are specifying a secure Management Service, you must still enter the non-secure port number here.Download the agentDownload script by using cp, rcp, scp, FTP, or wget utility.
An example of using wget is as follows:
wget http://foo:4889/agent_download/10.2.0.3.0/linux/agentDownload.linux
Run the following command:
chmod +x agentDownload.linux ./agentDownload.linux -b <name of the Oracle Homes> -m <fully-qualified Oracle Management Service host name> -r <Oracle Management Service ports>
For example:
./agentdownload.linux - b /oracle/agentinstall -m foo.us.oracle.com -r 4889
For clusters, use the following command:
./agentdownload.linux - b /oracle/agentinstall -m foo.us.oracle.com -r 4889 -c "host1,host2,host3" -n myCRS -l
To view more options, use the ./agentdownload.linux -h command.
To obtain agentdownload for Windows:
Follow the instructions below, to download the agent installation software for Windows:
Download the Win32_Grid_Control_agent_download_10_2_0_3.zip
file from OTN:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
Copy the downloaded file to the <OMS_HOME>/sysman/agent_download/10.2.0.3.0
directory.
Note:
Create the<OMS_HOME>/sysman/agent_download/10.2.0.3.0
directory, if it does not exist.Go to this directory by executing the following:
cd <OMS_HOME>/sysman/agent_download/10.2.0.3.0
When you are here, confirm that the size and checksum calculation of the downloaded file match the information specified on the OTN download page.
Unzip this file by executing the following:
unzip Win32_Grid_Control_agent_download_10_2_0_3.zip
After unzipping, the agentdownload.vbs
will be available at <OMSHOME>/sysman/agent_download/10.2.0.3.0/win32/agentdownload.vbs
.
Download the agentDownload.vbs
by using cp, rcp, scp, FTP, or wget utility on the machine where you want to install the Management Agent.
Note:
To download agentDownload script using wget utility, ensure that the wget utility exists on the Windows path variableNote:
Before executing theagentDownload.vbs
script, ensure Windows Script Host version 5.6 is installed on the target agent host. This is required for the script to be executed successfully.Run agentDownload.vbs
by executing the following:
cscript.exe agentDownload.vbs -b /oracle/agentinstall -m foo.us.oracle.com -r 4889
For clusters, use the following command:
cscript.exe agentdownload.vbs - b /oracle/agentinstall -m foo.us.oracle.com -r 4889 -c "host1,host2,host3" -n myCRS -l