Edit D:\app\Administrator\product\11.2.0\dbhome_1\oc4j\j2ee\oc4j_applications\applications\em\em\EMDocs\agent_install_readme.html
<html> <head> <title>Oracle Management Agent Installation Read Me</title> </head> <body lang=EN-US link=blue vlink=purple class="Normal" bgcolor="#FFFFFF"> <h1>Oracle Management Agent Installation Read Me</h1> <p>This document describes how to add additional Host targets to the Enterprise Manager Central Console by installing the Oracle Management Agent. </p> <p>To add a Host target, you simply install the Oracle 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. Refer to the information in this document for instructions on installing the Oracle Management Agent.</p> <p>This document is available from two locations after you install Oracle Enterprise Manager. You can display this document by clicking <b>Add</b> on the Hosts page in the Enterprise Manager Central Console, or you can locate and display this document in a text editor at the following location after you install the Oracle Management Service:</p> <pre><i>IAS_HOME</i>/sysman/agent_download/agent_install_readme.html</pre> <p><i>IAS_HOME </i>is the home directory of the Application Server where the Oracle Management Service is installed and deployed. For more information about the directories and files installed by the Enterprise Manager installation, see <a href="http://otn.oracle.com/pls/em40/em40.to_toc?partno=b10365"><i>Oracle Enterprise Manager Advanced Configuration</i></a>. </p> <h2>Methods for Installing the Management Agent</h2> <p>After you install the Oracle Management Service, your next step is to install the Oracle Management Agent on each host computer that you want to manage. Enterprise Manager provides two Management Agent installation methods:</p> <ul> <li> <p>On each host computer, run the Oracle Universal Installer from the Enterprise Manager CD-ROM and select the <b>Additional Oracle Management Agent</b> installation type. Instructions for using this Management Agent installation method are included in <i><a href="http://otn.oracle.com/pls/em40/em40.to_toc?partno=b10366">Oracle Enterprise Manager Basic Installation and Configuration</a></i>.</p> </li> <p>OR</p> <li> <p>Use the separate Management Agent installation CD-ROM to install and deploy Management Agents to many managed hosts. </p> </li> </ul> <p>This document describes how to use the Management Agent CD-ROM to install and deploy the Management Agent across multiple managed hosts across your Enterprise.</p> <h2>Overview of Using the Management Agent CD-ROM</h2> <p>There are a number of ways to install Agents from the Agent Download CD:</p> <ul> <li>You can share the Agent Download CD-ROM on the network—or copy the contents of the CD-ROM to a shared disk—and then download the jar file that contains the Oracle Universal Installer from the Management Agent CD-ROM. You can then unjar and run Oracle Universal Installer from the local host. On the Universal Installer File Locations page, enter the location of the Management Agent installation file (products.jar), which is located in the shared network location.</li> <p><b>Note:</b> You must use the version of Oracle Universal Installer that is distributed on the Management Agent installation CD-ROM; otherwise, you cannot perform some of the procedures described in this document.</p> <li> <p>You can share the Agent Download CD-ROM—or copy the contents of the CD-ROM to a shared disk—and run Oracle Universal Installer from the shared location. You can install the Management Agent using the interactive, graphical installation screens of the Universal Installer, or you can install the Management Agent silently using the response file that is included on the Agent Download CD-ROM.</p> </li> <li>You can download the entire staged Management Agent installation to the local target host, and the launch the Oracle Universal Installer from download area on the local host. This method is essentially the same as mounting the CD on the target host.</li> </ul> <h2>About the agentDownload Script</h2> <p>The Management Agent CD-ROM contains a sample script called <font face="Courier New, Courier, mono">agentDownload</font>. This sample script is provided as an example of how you can deploy Multiple Agents using a silent, scripted installation. The agentDownload script is fully functional and self-documenting so it can be customized easily for specific environments. </p> <p>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. </p> <p>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.</p> <h2>Benefits of the agentDownload Script</h2> <p>The download script deploys the standard Management Agent installation, with some additional benefits:</p> <ul> <li> <p>It can be modified for specific user environments</p> </li> <li> <p>It is non-interactive</p> </li> <li> <p>It's output is text-only (non-graphical)</p> </li> <li> <p>Management Agents installed using the script are identical to Management Agents installed with the Oracle Universal Installer graphical installation.</p> </li> <li> <p>The script invokes Oracle Universal Installer installation, but in silent mode</p> </li> </ul> <h2>Using the agentDownload Script</h2> <p>To deploy multiple Management Agents using the agentDownload script, you must do the following:</p> <ol> <li> <p>Install the Oracle Management Service.</p> </li> <p>You install the Management Service using the Oracle Universal Installer and the instructions in <i><a href="http://otn.oracle.com/pls/em40/em40.to_toc?partno=b10366">Oracle Enterprise Manager Basic Installation and Configuration</a></i>. The Management Service is installed and deployed into its own Oracle9<i>i</i>AS home directory.</p> <p>For more information about the directory structure of a typical Management Service installation, see <a href="http://otn.oracle.com/pls/em40/em40.to_toc?partno=b10365"><i>Oracle Enterprise Manager Advanced Configuration</i></a>.</p> <li> <p>Copy or mount the contents of the Management Agent CD-ROM to the following directory inside the Oracle9<i>i</i>AS home directory where the Management Service was installed and deployed:</p> </li> <pre><i>IAS_HOME</i>/sysman/agent_download/</pre> <li> <p>Download the agentDownload script to the target host from the Management Service URL.</p> </li> <p>The Management Service installation creates a Web sever alias called <font face="Courier New, Courier, mono">agent_download</font> that maps to a physical directory in the Oracle9<i>i</i>AS home directory where the Management Service is installed and deployed. OMS. For example, if you installed the Management Service on a host named <font face="Courier New, Courier, mono">mgmthost27.acme.com</font>, you could access the following URL from a browser:</p> <pre>http://mgmthost27.acme.com:4889/agent_download/</pre> <p><b>Note:</b> Port 4889 is the default port for the Enterprise Manager Central Console, and so it will always be available after you install the Management Service.</p> <p>Using this Web server alias, you can download the agentDownload script to the target host computer using the following URL:</p> <pre>http://mgmthost27.acme.com:4889/agent_download/download_scripts/agentDownload</pre> <p>Any method of retrieving the file is acceptable: for example, cp, rcp, scp, or FTP. The script can also be retrieved by launching a browser on the target machine and saving the link to a local file.</p> <li> <p>Execute the agentDownload script on the target host.</p> </li> <p>Before launching the script ensure that:</p> <ul> <li> <p>The execute bit is set and the script file has the proper file protection settings (use <font face="Courier New, Courier, mono">chmod</font> to ensure the file has the correct privileges).</p> </li> <li> <p>The $ORACLE_HOME environment variable is set in the user environment. 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.</p> </li> <li> <p>The $AGENT_INSTALL_PASSWORD environment variable is set in the environment if the Management Agent will be uploading to a secure Management Service.</p> </li> <p>For more information about enabling Security for Enterprise Manager components, see <a href="http://otn.oracle.com/pls/em40/em40.to_toc?partno=b10365">Oracle Enterprise Manager Advanced Configuration</a>.</p> <li> <p> The script user has the necessary file access permissions for the Management Agent home directory</p> </li> </ul> <li> <p>After the Management Agent installation is complete, change directory to the Agent home directory and run the <font face="Courier New, Courier, mono">root.sh</font> script as the root user.</p> </li> <p>For example:</p> <pre> $PROMPT>su root Password: <i>root_password</i> #./root.sh #exit $PROMPT> </pre> <p> The <font face="Courier New, Courier, mono">root.sh</font> script must be run as root; otherwise, the Management Agent will not be able to use the Enterprise Manager job system. The job system is required for some Enterprise Manager features, such as hardware and software configuration tasks and configuring managed database targets.</p> </ol> <h2>Script Details</h2> <p>The <font face="Courier New, Courier, mono">agentDownload</font> script performs the following actions:</p> <ul> <li> <p>Creates home directories for the Management Agent and Oracle Universal Installer if they don't exist, based on the following environment variable: </p> </li> <p>$ORACLE_HOME</p> <li> <p>Downloads the <font face="Courier New, Courier, mono">agent_download.rsp</font> response file from the Management Service Web server</p> </li> <p>The Management Service installs the response file with the name and port number of the Management Service. As a result, the Management Agent you install will be configured to use the Management Service from which the response file was downloaded.</p> <li> <p>Downloads a jarred Oracle Universal Installer for the target operating system from the Management Service Web server.</p> </li> <li> <p>Unjars the Oracle Universal Installer and points the Oracle Universal Installer to the product definition (products.jar) hosted by the Management Service Web server</p> </li> <li> <p>Launches the Oracle Universal Installer in silent mode from the local machine; the Universal Installer pulls files from the Web server to the target machine via HTTP.</p> </li> <li> <p>The resulting installation and configuration (including the autodiscovery of managed targets on the Management Agent host) is identical to that provided by the Management Agent install on the Enterprise Manager CD set.</p> </li> </ul> <h2>Customization</h2> <p>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 below:</p> <pre>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.jar 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 EmVersion=400</pre> <p>?????? </p> </body> </html>
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de