5 Deploying the Management Agent

Fresh Installation of the Management Agent

This option helps you perform a fresh 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 AppendixE, "Prerequisite Checks Executed by Agent Deploy" for more information.

To perform a fresh Management Agent installation:

1. Select Fresh Install on the Agent Deploy application home page. The Installation Details page appears.

2. 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.1.0/<platform>, or any other location where the software is available.

   See Chapter5, "Uploading Agent Installation Software for Different Platforms" for more information on obtaining agent installables for different platforms.

   To choose a location other than the default location from the OMS, 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.

   
   
   
   

   IMPORTANT: 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 F-1 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 F-2 for a list of parameters supported by OUI.

   
   

   Figure 5-1 Source Software Section of the Installation Details Page

   
   

3. Select the appropriate platform on which you want to perform this installation.

4. 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 (,), white space, or a new line as a separator when specifying multiple hosts.

   
   
   
   

   IMPORTANT: 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, since the Agent Deploy application does not validate this format on the selected file. A sample host list format is provided in Table 5-1.

   
   

   Table 5-1 Sample Host List Format

   FullyQualified Host Name	Host Name	Host IP Address
   host1.foo.com	host1	154.87.3.229
   host2.foo.com	host2	154.87.3.109
   host3.foo.com	host3	154.80.5.218

   
   

   Figure 5-2 Hosts Section of the Installation Details Page

   
   

   1. Select Cluster Install if you want to install the Agent on a cluster.

   2. 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 3.

   3. 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 3.

      
      

      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 a 9.2 Oracle Cluster version, confirm the node names by executing lsnodes from the cluster Oracle home. See Chapter5, "Installing a Cluster Agent on Oracle Clusterware" for more information.

      
      

   4. In the Cluster Name text box, specify a unique cluster name. If you are extending a cluster, ensure you 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 install option, Agent Deploy performs the agent installation on all the cluster nodes irrespective of the number of hosts you have selected. For example, if you choose to perform a cluster install on a cluster having 10 nodes, but specified only 5 nodes, Agent Deploy installs the agent on all 10 nodes that form that cluster. If you are extending an existing cluster, ensure that the cluster name you specify is the same as the existing cluster. You must also ensure that you specify all the nodes of the existing cluster along with the new node on which you are installing the cluster agent.

      
      

5. In the OS Credentials section, specify the appropriate operating system user credentials. Select Run root.sh if you want Agent Deploy to execute this script.

   Figure 5-3 OS Credential Section of the Installation Details Page

   
   
   
   

   Note: The root.sh script executes after the configuration assistants are run, and before executing post-install 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.

   
   

6. 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 sub-directory under this directory.

   Figure 5-4 Destination Section of the Installation Details Page

   
   
   
   

   Note: Ensure you have write permissions on the installation Base Directory that you specify.

   
   

7. Specify the port on which the Agent will communicate. The default port value is 3872.

   Figure 5-5 Port Section of the Installation Details Page

   
   
   
   

   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).

   
   

8. In the Additional Parameters text box, specify any additional parameters that you want to pass during installation.

   Figure 5-6 Additional Parameters Section of the Installation Details Page

   
   
   
   

   IMPORTANT: 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 F-0 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 F-1 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 and optionally -i, -p, -t, -d, and -z.

9. In the Management Service Security section, specify the Management Service Registration Password if you want to secure communications between the Agent and OMS. Alternatively, the super administrator can approve the addition of new agents to Enterprise Manager after the installation is complete.

   Figure 5-7 Management Server Security Section of the Installation Details Page

   
   
   
   

   Note: An unsecure agent cannot upload data to the secure OMS. Oracle also recommends for security reasons that you change the OMS password specified here after the installation is complete.

   
   

10. In the Additional Scripts section, specify any pre-install and/or post-install scripts that you want to execute.

    Figure 5-8 Additional Scripts Section of the Installation Details Page

    
    

    Select Run as Superuser if you want to run these scripts as root.

    
    

    Note: The pre/post installation scripts that you specify must be available on all the hosts. These files are not copied onto the hosts from the source software location during installation.

    
    

11. 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 - This creates oraInst.loc that contains the central inventory. root.sh - This runs all the scripts that must be executed as root. If this is not the first Oracle product installation, Agent Deploy executes only root.sh.

    
    

Installation Using a Shared Agent Home

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 AppendixE, "Prerequisite Checks Executed by Agent Deploy" for more information.

Concepts and Prerequisites

The following sections briefly discuss the Shared Agent Home concepts, and also list the prerequisites that should be met before starting the installation.

Performing the Installation

To perform a fresh Management Agent installation:

1. Select Shared Agent Home on the Agent Deploy application home page. The Installation Details page appears.

2. In the Hosts section:

   Figure 5-9 Hosts Section of the Installation Details Page

   
   

   1. Select the appropriate Platform on which you want to perform this installation.

   2. 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: 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 comma (,) or just white space as a separator when specifying multiple host names.

      
      
      
      

      ATTENTION: 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 pre-install, post-install, and collect logs are executed on all the nodes. After the installation is complete, the Installation Status page 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.

      
      

3. In the OS Credentials section:

   Figure 5-10 OS Credentials Section of the Installation Details Page

   
   

   1. Specify the appropriate operating system user credentials.

   2. Select Run root.sh 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 is not set in the /etc/sudoers file.

   
   

   IMPORTANT: 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.

   
   

4. In the Destination section:

   Figure 5-11 Destination Section of the Installation Details Page

   
   

   1. Specify the complete path to the NFS Agent Location. This is the shared directory location on the source host that must be visible (NFS-Mounted) from all remote hosts.

   2. Specify an appropriate State 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 STATE directory.

5. In the Port section:

   Figure 5-12 Port Section of the Installation Details Page

   
   

   This is a mandatory field. Specify the appropriate Port on which the Agent will communicate.

   
   

   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.

   
   

6. In the Management Service Security section:

   Figure 5-13 Management Service Security Section of the Installation Details Page

   
   

   Specify the Management Service Registration Password if you want to secure communications between the Agent and OMS. Alternatively, the super administrator can approve the addition of new agents to Enterprise Manager after the installation is complete.

   
   

   Note: An insecure agent cannot upload data to the OMS. Oracle also recommends for security reasons that you change the OMS password specified here after the installation is complete.

   
   

7. In the Additional Scripts section:

   Figure 5-14 Additional Scripts Section of the Installation Details Page

   
   

   1. Specify any pre and/or post-installation 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.

   2. Click Continue to start the installation process.

      
      

      IMPORTANT: If the shared agent is the first Oracle product that is installed on the host, you must execute the following command from the EMSTATE 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 have one of the following two statuses:

   • 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 may still choose to ignore and 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 page of the application. The Fixup page displays the prerequisites that can be automatically fixed, and those that require manual fixes.

User Credentials

The shared agent (nfsagent) can only be installed with the same user credentials that were used to perform the master agent installation.

If Agent is not the First Oracle Product Installation

If this shared agent installation is not the first Oracle product installation and your (user that has performed the master agent installation) home directory 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>

Usage of the nfsagentinstall Script

./nfsagentinstall  -s <EMSTATE Directory location> -p <port number>

where,

• <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.

<EMSTATE Dir>/bin 
./emctl control agent runCollection <Host name>:host Inventory

Script Details

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 Linux only).

• Unjars the Oracle Universal Installer and points the Oracle Universal Installer to the product definition file (products.xml) hosted by the Management Service Web server.

• 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.

  
  

  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 install on the Enterprise Manager DVD set.

• The agentDownload script creates a log file in $ORACLE HOME.

• At the end of a successful installation, the Agent starts and should begin successfully uploading to the OMS, presuming automatic discovery and automatic start were not disabled at the command line.

To run the script, use the following command:

./agentDownload.<platform> [-bcdhilmnoprstux]

Descriptions of the script options follow:

Customizing the agentDownload Script

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

Installing a Standalone Agent on a 9.2 Cluster Node

You can perform a standalone agent installation using the following deployment methods:

agentDownload -n <clustername>

Installing a Cluster Agent on a 9.2 Cluster

You can perform a cluster agent installation using the following deployment methods:

./runInstaller "CLUSTER_NODES={node1,node2, ...}"

Installing a Standalone Agent on Oracle Clusterware

You can perform a standalone agent installation on Oracle Clusterware using the following deployment methods:

agentDownload -n <clustername>

Installing a Cluster Agent on Oracle Clusterware

You can perform a cluster agent installation using the following deployment methods: