Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1)
Part No. B12012-03
  Go To Table Of Contents
Go To Index

Previous Next  

C Using the Downloadable Management Agent

This appendix describes how to add additional Host targets to the Oracle Enterprise Manager Grid Control by downloading and installing the Oracle Management Agent using the agentDownload script.

To add a Host target, you must install the Management Agent on the host computer you want to manage. When the Management Agent on that host begins communicating with the Oracle Management Service, the Agent target and the Host target will appear in the list of targets.

See Also:

For more information about the directories and files installed by the Enterprise Manager installation, see Oracle Enterprise Manager Advanced Configuration.

Methods for Installing the Management Agent

After you install the Management Service, your next step is to install the Management Agent on each host computer that you want to manage. Enterprise Manager provides a number of installation methods:

This appendix describes how to use the agentDownload script to install and deploy Management Agents across managed hosts within your enterprise.

About the agentDownload Script

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 is fully functional and self-documenting so it can be customized easily for specific environments.

The agentDownload script uses "pull" technology. In other words, even though the script does not have to exist on a local file system, it must always be executed from the target host computer. You must be logged into 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 needs to be launched from each target host where you want the Management Agent installed. Because the installation is scripted, it is possible to use a wrapper script, UNIX cron job, rdist, or a combination of operating system features to fully automate this process for mass deployments.

Benefits of the agentDownload Script

The download script deploys the standard Management Agent installation, with some additional benefits:

Obtaining the agentDownload Software

The downloadable Agent software is available on the platform-specific CD from which the Oracle Management Service was installed, and from the following Oracle Technology Network Web site under "Mass Agent Deployment":

To initiate a silent Oracle Universal Installer session using HTTP to install Management Agents, download and execute the agentDownload script to perform the installation. (Note that proxy servers are not supported.)

To obtain the script for other platforms, you must complete the following steps to make the Management Agent installable from the Management Service Oracle home:

  1. Download the appropriate files from OTN; there is one compressed cpio file for each platform.

  2. For each file, run gunzip. For example:

    gunzip <filename>.gz
  3. Run cpio to extract the archive. For example:

    cpio -idcmv <filename>.cpio
  4. Recursively copy the agentDownload for each operating system platform to the Management Service Oracle home. For example:

    cp -r linux $ORACLE_HOME/sysman/agent_download

Using the agentDownload Script

To deploy multiple Management Agents using the agentDownload script, you must do the following:

  1. Install the Oracle Management Service.

    You install the Management Service using the Oracle Universal Installer and the instructions in Chapter 2. The Management Service is installed and deployed into its own Oracle Application Server home directory.

    See Also:

    For more information about the directory structure of a typical Management Service installation, see Oracle Enterprise Manager Advanced Configuration.

  2. The download stage for the Mangement Service platform is installed with the Management Service. For example, for Solaris operating systems, the download stage can be found in:


    The agentDownload script, the response file, and readme file can be found in:

  3. Download the agentDownload script to the target host from the Management Service URL.

    The Management Service installation creates a Web sever 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, you could access the following URL from a browser:


    Port 4889 is the default port for Grid Control, so 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 (no extensions).

    Where OS represents the operating system platform. For example, for Solaris operating systems, the script is named agentDownload.solaris.

    Any method of retrieving the file is acceptable: cp, rcp, scp, FTP, etc. The script can also be retrieved by launching a browser on the target machine and saving the link to a local file.


    If you opt to download using a file-based protocol rather than HTTP, you will need to modify the $AgentDownloadURL variable to access the file system on the Management Server host instead of a URL.The URL:

    is a Web alias for:


  4. Execute the agentDownload script on the target host.

    Before launching the script, ensure that:

    • The execute bit is set and the script file has the proper file protection settings (use chmod to ensure the file has the correct privileges).

    • The $ORACLE_HOME environment variable is set in the user environment or 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 will be created during the installation. If it exists, it must be empty. If the variable is not set, the script will exit with an error.

    • The jar executable file is in the PATH environment variable. If the file is not found, the script will exit with an error.

    • The wget (or other file transfer mechanism) has been defined in the script. The script default is to call /usr/local/bin/wget. If the referenced file is not found, the script will exit with an error.

    • The $AGENT_INSTALL_PASSWORD environment variable is set in the environment if the Management Agent will be uploading to a secure Management Service.

      See Also:

      For more information about enabling Security for Enterprise Manager components, see Oracle Enterprise Manager Advanced Configuration.

    • The script user has the necessary file access permissions for the Management Agent home directory

  5. After the Management Agent installation is complete, change directory to the Agent home directory and run the script as the root user.

    For example:

    $PROMPT>su root
    Password: root_password

    The script must be run as root; otherwise, it will exit and the Enterprise Manager job system will not be available. The job system is required for some Enterprise Manager features, such as hardware and software configuration tasks and configuring managed database targets.

Script Details

The agentDownload script performs the following actions:

To run the script use the following command:

./agentDownload41 [-dhiostx]

Descriptions of the script options follow:

Option Description
-d Do not automatically discover targets during installation.
-h Usage: Displays and describes the options that can be used with this script.
-i Inventory pointer location file: Can be used to point the installer to a non-default inventory. (For advanced users only.)
-o ORACLE_HOME: Can be picked up from the environment or specified on the command line.
-s Installer stage directory: Points to an installer previously downloaded by the script. If defined, the local installer will be launched and the jarred installer will not be downloaded.
-t Do not automatically start the Agent at the end of installation.
-x Debug output: Turns on shell debugging.


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"
# 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: