| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
PDF · Mobi · ePub |
Oracle Management Agent (Management Agent) is one of the integral components of Enterprise Manager Grid Control (Grid Control) architecture. Management Agent communicates with the monitored targets, collects information about their health, transports that information to Oracle Management Service (OMS), which in turn stores the collected details in the central repository created in Oracle Database.
This chapter describes how you can install a Management Agent. In particular, it covers the following:
Note:
To download the Management Agent software from My Oracle Support (formerly Metalink) using the Grid Control console, follow the instructions given in Downloading Management Agent Software Using Grid Control Console.In addition to the installation types described in this chapter, you can also use the following installation types:
Cluster Agent Installation
This type of installation allows you to perform a standalone Management Agent installation on a selected cluster node, or perform a cluster Management Agent installation on a selected cluster. See Chapter 12, "Deploying Management Agent on a Cluster" for more information.
Management Agent Cloning
This type of installation allows you to clone an installed Management Agent (also referred to as the master Management Agent) on multiple destination Oracle homes. See Chapter 13, "Cloning 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 Installing Enterprise Manager Grid Control in Silent Mode for more information.
Note:
On Microsoft Windows, after the Management Agent is installed, the Windows service names of the Management Agent are recorded as
Oracle<OH_name>Agent. For example, Oracleagent10g1Agent, Oracleagent10g1SNMPPeerEncapsulator, Oracleagent10g1SNMPPeerMasterAgent. However, if you want to change or reconfigure the service names without the prefix "Oracle", then do the following:
Pass the "s_agentServiceName" variable while running the runInstaller. For example, ./runInstaller s_agentServiceName="GRIDCONTROL"
If you are installing the Management Agent in silent mode, then provide the "s_agentServiceName" value in the response file additional_agent.rsp.
If you are installing the Management Agent using agentDownload script, then provide the "s_agentServiceName" value in the response file agent_download.rsp.
Before applying any one-off patch that relinks the nmo binary, Oracle recommendeds you to install the one-off for bug7436312. The nmo binary needs the steuid privilege set to root, which gets erased when nmo is relinked by the application of a one-off patch. For example, the one-off patch# 5976285 is one such patch that relinks nmo. If the prereq patch is not applied before, jobs can no longer run. The only recourse will be to manually run root.sh on the target Management Agent homes. With the prerequisite already applied to Management Agent homes, root.sh can be run from Patchwizard or it can be deferred.
Note:
If you want to configure the Management Agent on AIX operating system, then follow the configuration steps described in My Oracle Support note 552404.1.This section describes how you can install a Management Agent using the Agent Deploy application. In particular, this section covers the following:
Note:
If the installation fails, review the log files described in Appendix C, "Agent Log Files".Agent Deploy application is an application within Grid Control console that allows you to install Management Agents using GUI-rich, interactive screens.
Although the Agent Deploy application can be used for installing one, single Management Agent, the application is best suited for installing multiple Management Agents, as a mass deployment, and is particularly useful when you want to perform remote installations across your organization.
The Agent Deploy application gives you the flexibility to specify multiple hosts on which the Management Agent needs to be installed. This helps you when you want to install the Management Agent on several hosts, in one attempt. The application connects to OMS where the Management Agent software is located and copies all the required files and scripts from there to the specified hosts, and then runs them to install the Management Agent. The connectivity between OMS and the specified hosts is established using SSH protocol.
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.
Caution:
If you are deploying the Management Agent in an environment having multiple OMS installations that are using a load balancer, then you should not access the Agent Deploy application using this load balancer. Oracle recommends that you access the OMS directly.Before installing a Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 10-1 Prerequisites for Installing a Management Agent Using Agent Deploy Application
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the hardware and softwrae requirements. For hardware requirements, see Hardware Requirements. For software requirements, see Software Requirements. |
|
|
Operating System Requirements |
Check if that operating systemon which you are going to install the Management Agent is ceritified. For information about certified operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Install the packages that are required for your operating system. For information about packages, see Appendix G, "Check Platform-Specific Package Requirements for Agent Installation". |
|
|
SSH Setup Requirements |
If you are installing the Management Agent using Enterprise Manager 10g Grid Control Release 2 (10.2.0.2 or 10.2.0.1), then ensure that SSH is set up. For information about setting up SSH, see SSH (Secure Shell) Setup. (Note that SSH2 is supported only from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)). In Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) or higher, the Agent Deploy application sets up and drops the SSH connection automatically, but if agent targets are on Microsoft Windows operating systems, then you need to setup Cygwin as explained in SSH (Secure Shell) Setup. |
|
|
Load Balancer Requirements |
If you are installing the Management Agent in an environment that has multiple OMSes managed by a Server Load Balancer (SLB), then ensure that you enable communication between the Management Agent and the host running the SLB. For information about configuration to be done for SLB, see Configurations Required for Management Agent to Communicate with Oracle Management Service with Server Load Balancer. |
|
|
Operating System Group Requirements |
Ensure that you are part of the same operating system group that installed Oracle Application Server and/or Oracle Collaboration Suite. |
|
|
User and Operating System Group Requirement |
Ensure that the target host where you want to install the Management Agent has the appropriate users and operating system groups created. For information about creating operating system groups and users, see Operating System Groups and Users Requirements. |
|
|
Path Validation Requirements |
Validate the path to all command locations. For more information, see Validate All Command Locations. |
|
|
Permission Requirements |
Ensure that you have read, write, and execute permissions to For information about oraInventory permissions, see Installing Enterprise Manager Grid Control As the First Oracle Software. |
|
|
Oracle Inventory Location Requirements |
Ensure that the Oracle Inventory ( |
|
|
Default Port Requirements |
Ensure that the SSH daemon is running on the default port (that is, 22) on all the target hosts.
|
|
|
PubkeyAuthentication Parameter Requirements |
Ensure that the To verify the value of this parameter, run the following command:
The result of this command must be Yes. If the result is No, then edit the |
|
|
Virtual Host Requirements |
If you are deploying a Management Agent on a virtual host using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower, then you must make the following changes.
Note: This step is applicable only if you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower. Also, if you have multiple OMSes in your environment with a Software Load Balancer (SLB), then you must modify the agentpush.properties file on all OMSes. In Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher, the New Agent Installation Wizard has a check box in the Hosts section that allows you to indicate that the hosts specified are virtual hosts; and therefore, you need not update the agentpush.properties file. |
|
|
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is abc and user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory. |
|
|
SUDO Requirements |
Ensure that you have SUDO privileges to run To verify whether you have SUDO privileges to run these files, access the
|
|
|
Agent User Account Permissions and Rights (For Microsoft Windows) |
(For Microsoft Windows) Ensure that the agent user account has permissions and rights to perform the following:
To verify whether the agent user has these rights, follow these steps:
|
|
|
Permissions for cmd.exe (For Microsoft Windows) |
(For Microsoft Windows) Grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
You can view the prerequisite checks and installation status from the Status screen in the Agent Deploy application. For more information about prerequisite checks related to Agent Deploy application, see Appendix G, "Agent Deploy Application - Installation Prerequisites".
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.
If you are deploying a Management Agent in an environment that has multiple OMSes managed by a Server Load Balancer (SLB), then ensure that you follow these steps to enable communication between the Management Agent and the host running the SLB.
Note:
This section is applicable only if you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower. In Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher, the New Agent Installation Wizard has a new section "Load Balancer Host and Port" that allows you to specify the Load Balancer host name and port; and therefore, you need not update the agentpush.properties file.Access the following file to provide the name of the host where SLB is set up:
<OMS_HOME>/sysman/prov/agentpush/agentpush.properties
Uncomment the following property and provide the name of the host where SLB is set up:
oracle.sysman.prov.agentpush.slb.host=
Management Agents installed by the Agent Deploy application try to connect to the SLB host using the specified host name.
Uncomment the following property and provide the port value of the host where SLB is set up:
oracle.sysman.prov.agentpush.slb.port=
Management Agents installed by the Agent Deploy application try to connect to the load balancer hosts using the specified port values.
Ensure that you stage the agent software uniformly across all the OMS hosts that are managed by the SLB.
The following shows what values will be considered for host and port when only one of them or none of them are specified in the agentpush.properties file.
Table 10-2 Host and Port Values Considered When Not Specified in agentpush.properties File
| Property Not Specified | Host Name Considered | Port Value Considered |
|---|---|---|
|
When SLB host name is not specified in the following property of the oracle.sysman.prov.agentpush.slb.host |
The OMS host name specified in the following property of the oracle.sysman.emSDK.svlt.ConsoleServerHost |
The OMS port value specified in the following property of the oracle.sysman.emSDK.svlt.ConsoleServerPort Therefore, the port value specified in the |
|
When SLB port value is not specified in the following property of the oracle.sysman.prov.agentpush.slb.port |
The SLB host name specified in the following property of the oracle.sysman.prov.agentpush.slb.host |
The port value 80 is considered. |
|
When both, SLB host and SLB port, values are not specified in the following properties of the oracle.sysman.prov.agentpush.slb.host oracle.sysman.prov.agentpush.slb.port |
The OMS host name specified in the following property of the oracle.sysman.emSDK.svlt.ConsoleServerHost |
The OMS port value specified in the following property of the oracle.sysman.emSDK.svlt.ConsoleServerPort |
Agent Deploy provides the following two options for deploying the Management Agent:
Note:
If you want to view the status of an installation or upgrade session that was previously run, click Agent Installation Status in the Deployments screen. However, do not attempt to view the installation status until the installation is complete. If you do, you will see 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 Prerequisite Checks Executed by Agent Deploy for more information.
Note:
You can choose to skip the prerequisite check that is run by the Agent Deploy application. To do so, navigate to the <OMSHOME>/sysman/prov/agentpush directory, access the agentpush.properties file, and change the value of oracle.sysman.prov.agentpush.step2 to "false", that is oracle.sysman.prov.agentpush.step2=false.
On Microsoft Windows, do not open the agentpush.properties file using Microsoft Word software. Open it using other text editors such as VIM or Notepad.
To perform a new Management Agent installation, complete the following steps:
In Grid Control, click Deployments.
On the Deployments page, from the Agent Installation section, click Install Agent.
On the Agent Deploy home page, select Fresh Install. 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 OMS, for example <OMS_HOME>/sysman/agent_download/10.2.0.2.0/<platform>, or any other location where the software is available.
If you select Default, from Management Server location, then ensure that the path to the Management Agent software directory on the OMS host that you specify is visible over HTTP from all remote hosts.
To choose a location other than the default location from the OMS, select Another Location, and specify the full path to the software location where the software is staged. Ensure that the path leads up to the product.xml file. For example: /net/host1/shiphomes/linux/agent/stage/products.xml. Also ensure that this location (shared or non-shared) is accessible from all the remote hosts , and you have read permission on it.
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 H-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 H-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 Management Agent that you want to install. The values available in this list will depend on the staged software that are available on the OMS 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 Management Agent installation.
Note:
Ensure that 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.
When virtual host names are provided in Provide Host List and when Cluster Install checkbox is selected, the same virtual host names will be populated in Cluster Node List. These virtual host names listed in Cluster Node List must be changed to match the actual cluster node names of the hosts. The correct cluster node names can be found in OraInventory/ContentsXML/inventory.xml on each remote host.
Alternatively, click Get Host Names From File to browse and select the file that contains a list of all the required host names.
If you choose to select a file that contains a list of all required host names, then ensure that the file format is similar to /etc/hosts file. Note that the first column of the file must have the host name and when you provide multiple hosts, then ensure that the hosts are mentioned in separate lines.
Let's consider that you have the following hosts in your environment:
(1) host1 with fully qualified name host1.foo.com and IP address 154.87.3.229
(2) host2 with fully qualified name host2.foo.com and IP address 154.87.3.109
(3) host3 with fully qualified name host3.foo.com and IP address 154.80.5.218
In this case, the format of the host file should look like this:
host1 host2 host3
Alternatively, if you already have a file that has the following format, then you can use that file and format as is.
host1 host1.foo.com 154.87.3.229 host2 host2.foo.com 154.87.3.109 host3 host3.foo.com 154.80.5.218
The Agent Deploy application picks up only the values in the first column of the Host List file that you specify/select. Ensure that the host list format is appropriate because the Agent Deploy application does not validate this format on the selected file.
Note:
For Grid Control 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 Allow local hostname to override provided hostname if the specified host name is a virtual host name and not a physical host name.
For example, if the destination host name is mypc.server.com but the virtual name given to it is host1, then you can specify host1 in the Provide Host List text box, but select this check box to indicate that the specified host name is a virtual host name. The Agent Deploy application will internally interpret the virtual host name specified and map to its real, physical host name in the network.
Note:
This step is applicable only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher. In Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower, the New Agent Installation Wizard does not display this check box and for specifying virtual host names, you must update the agentpush.properties file as described in Prerequisites.Select Cluster Install if you want to install the Management Agent on a cluster.
For Cluster Node List, specify the cluster nodes on which the Management Agent must be installed. Ensure that you specify only the short names of the hosts, not the fully-qualified names. 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 must be the host short names, not the fully-qualified names. For example, if the node is xyz.server.us.com, and the short name is xyz, then specify only xyz in the Cluster Node List field.
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 Chapter 12, "Deploying Management Agent on a Cluster" for more information.
When virtual host names are provided in Host List and when Cluster Install is selected, the same virtual host names will be populated in Cluster Node List (the next field). These virtual host names listed in the Cluster Node List textbox must be changed to match the actual cluster node names of the hosts. The correct cluster node names can be found in OraInventory/ContentsXML/inventory.xml on each remote host.
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 Management 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 Management 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 Management 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:
The OS credentials that you specify here must be the same for all the selected hosts.The root.sh script runs after the configuration assistants are run and before the postinstallation scripts (if any) are run. If you do not select this option here, you must run root.sh on each node manually.
Agent Deploy application uses sudo to run the root.sh script, and therefore, you must have SUDO privileges to run the script. You must also specify the invoking user's password here.
If /etc/sudoers is configured in such a way that sudo never prompts for a password, then a directory with the host password as the title gets created in the invoking users home directory. To avoid this, ensure that you configure /etc/sudoers file such that running a command using sudo always prompt for a password.
In the Destination section, specify the absolute path for the Installation Base Directory. This directory is created on all the specified hosts, and the Management Agent Oracle home directory is created as a subdirectory under this directory.
Note:
For the Management Agent installation to be successful, ensure that you extract the agentDownload kit before performing the installation.Note:
Ensure you have write permissions on the installation Base Directory that you specify.In the Port section, specify the port on which the Management Agent will communicate. The default port value for 10.2 Management Agent is 3872.
Note:
Ensure that the port you specify is not busy, otherwise the prerequisite check fails. If you do not specify a port here, then the Agent Deploy application automatically picks up a free port (3872 or in the range of 1830 - 1849).In the Load Balancer Host and Port section, specify the name of the host and port where the Server Load Balancer is set up so that communication between the Management Agent and the host running the Server Load Balancer can be enabled. This is required only if you are deploying the Management Agent in an environment that has multiple OMSes managed by a Server Load Balancer.
You can specify an HTTP or HTTPS port. However, if your OMS is configured only for secured communication(HTTPS), then you must specify only an HTTPS port.
Note:
This step is applicable only if you are using Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher. In Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower, the New Agent Installation Wizard does not display this section and for specifying these values, you must update the agentpush.properties file as described in Configurations Required for Management Agent to Communicate with Oracle Management Service with Server Load Balancer.Note:
If your Server Load Balancer is not functional for some reason, then you can optionally specify the host name and port of the OMS that is being managed by the Server Load Balancer. This is however not recommended, so use this option only if your Server Load Balancer has a problem.In the Additional Parameters text box, specify any additional parameters that you want to pass during installation.
The additional parameters 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 H-1, "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 H-2, "Parameters Supported by Oracle Universal Installer" for a list of parameters supported by OUI.
Oracle recommends you to specify only those parameters that you want to run in addition to the general parameters you have already provided in this page for installation. For example, in step (7), you are providing the installation base directory. Therefore, for additional parameters, try to avoid specifying the installation base directory again. If you still do so, then the value you specified in step (7) will be ignored and the value you specified here will be used instead.
And note that if you are specifying more than one parameter, then separate them with a white space. For example, -i /etc/oraInst.loc -p /home/config/staticports.ini.
Specify the Management Service Registration Password if you want to secure communications between the Management Agent and OMS. Alternatively, the super administrator can approve the addition of new agents to Grid Control after the installation is complete.
Note:
An unsecure Management Agent cannot upload data to a secure OMS. Oracle also recommends for security reasons that you change the OMS 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.
Grid Control displays the My Oracle Support Details page.
On the My Oracle Support Details page, do the following:
If the host where the Management Agent is being installed has a direct connection to the Internet, then specify an email address and My Oracle Support (formerly Metalink) password.
An email address is required so that security updates and install updates can be sent. You can specify any email address, but Oracle recommends you to specify the My Oracle Support user name. For example, john.mathew@xyz.com.
If the host where the Management Agent is being installed has an indirect connection to the Internet through a proxy server, then specify an email address and My Oracle Support password, and then in the Connection Details section, specify the proxy server details.
Note:
You can change the proxy server settings any time after the installation or patching process ends. To do so, run the
configCCR command from the /ccr/bin/ directory within the Oracle home directory of the Management Agent.If the host where the Management Agent is being installed does not have a direct or indirect connection to the Internet, then specify the email address and leave the other fields blank.
In this case, after you complete the installation process, manually collect the configuration information and upload it to My Oracle Support. To understand how the configuration information can be manually collected and uploaded, see the steps outlined in Manually Collecting and Uploading Configuration Information to My Oracle Support (formerly Metalink).
Note:
If you see any errors on this page, then check whether you (the user installing the Management Agent) have the necessary write permissions on crontab. If you do not, then create an entry for your user account in the/usr/lib/cron/cron.allow file.Click Continue.
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:
If you are installing the Management Agent on a cluster, then note that the preerquisite checks may take some time to complete. For more information on the prerequisite checks, installation, and configuration logs that are created, see Agent Deploy Log Files.Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
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 Management Agent Installation Fails to view a sample of the emctl status log and to troubleshoot possible errors that may occur during installation.
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 Management Agent installation on any of the nodes. Here, if you specify only two nodes (n1 and n2) for Management Agent installation, then the Agent Deploy application updates the inventory for these two nodes and installs the Management Agent on these nodes.
Now, if you want to install the Management 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, then the Agent Deploy application updates the n1 and n2 inventory to include n3, and then installs the Management Agent only on the third node (n3).
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 Management Agent on the node (n4) that is an extension of the existing cluster (cr1 with nodes n1, n2, and n3.) But during the Management Agent installation, you specify only the new node (n4) in the Cluster Node List text box. Agent Deploy installs the Management 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 Management 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 Management 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 Management Agent installation.
Now, you can view these clusters in the Grid Control console under unique cluster names that you specified during Management Agent installation.
To manually collect the configuration information, follow these steps:
On the host where the Management Agent is being installed, navigate to the following location. Here, <OracleHome> is the Oracle home directory of the Management Agent you installed:
<OracleHome>/ccr/bin
Collect configuration information by running the following command:
<OracleHome>/ccr/bin/emCCR collect
For Oracle Configuration Manager 10.2.7 and higher, the collected configuration information is stored in the <OracleHome>/ccr/hosts/<hostname>/state/upload/ocmconfig.jar file. For lower versions of Oracle Configuration Manager, the collected configuration information is stored in the <OracleHome>/ccr/state/upload/ocmconfig.jar file. When you run the same command next time, the ocmconfig.jar file gets overwritten with fresh data. Therefore, at any point, you will see only one ocmconfig.jar file.
Upload the ocmconfig.jar file to a Service Request on My Oracle Support (formerly Metalink) at the following URL:
To deploy and install an Management Agent on multiple hosts using an existing Shared Agent Installation, you must have already performed a complete Grid Control product installation (including the Management Agent). Another prerequisite when using this option is that the directory where the Management 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 Prerequisite Checks Executed by Agent Deploy for more information.
Caution:
NFS agent deployment is not supported on a cluster. If you want the Management 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 Installing Management Agent Using nfsagentinstall Script for more information.The following sections briefly discuss the shared agent home concepts, and also list the prerequisites before starting the installation.
EMSTATE Directory
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 Management Agent binaries has its own EMSTATE directory.
EMSTATE Directory Location
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.
EMSTATE Directory Space Requirements
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.
Packages and OS Patches Requirement
Currently, no packages are required by the Management Agent to run on the shared hosts.
Operating System Credentials
When you are performing Management 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 Management 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.
Shared oraInventory
When performing a cluster Management Agent installation using a shared Management Agent Oracle home, ensure the oraInventory is shared (accessible by all remote hosts).
To perform a new Management Agent installation:
In Grid Control, click Deployments.
On the Deployments page, from the Agent Installation section, click Install Agent.
On the Agent Deploy home page, select Add Hosts to Shared Agent. 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 Management Agent installation.
Alternatively, click Get Host Names From File to select the file that contains a list of all the required host names.
If you choose to select a file that contains a list of all required host names, then ensure that the file format is similar to /etc/hosts file. Note that the first column of the file must have the host name and when you provide multiple hosts, then ensure that the hosts are mentioned in separate lines. To understand how the format should look, see Example 10-1, "Host File Format".
The Agent Deploy application picks up only the values in the first column of the Host List file that you specify/select. Ensure that the host list format is appropriate because the Agent Deploy application does not validate this format on the selected file.
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.
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.
Note:
The OS credentials that you specify here must be the same for all the selected hosts.Select Run root.sh (on UNIX machines only) if you want Agent Deploy to execute this script.
The root.sh script runs after the configuration assistants are run and before the postinstallation scripts (if any) are run. If you do not select this option here, you must run root.sh on each node manually.
Agent Deploy application uses sudo to run the root.sh script. You must specify the invoking user's password here.
If /etc/sudoers is configured in such a way that sudo never prompts for a password, then a directory with the host password as the title gets created in the invoking users home directory. To avoid this, ensure that you configure /etc/sudoers file such that running a command using sudo always prompt for a password.
In the Destination section:
Specify the complete path to the NFS Agent Location. This is the shared directory location on the source Management Agent host that must be visible (NFS-mounted) from all remote hosts.
Note:
Ensure that the directory to which the NFS Agent is mounted on the remote hosts is the same as the NFS Agent home directory on the source host. For example, if the NFS Agent is installed at /scratch/oraclehome/agent10g, then on all the target remote hosts, the location /scratch/oraclehome/agent10g must refer to the same NFS Agent home directory.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 Management Agent has its own EMSTATE directory.
In the Port section, specify the appropriate port on which the Management Agent will communicate. This is a mandatory field if you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower.
Note:
Ensure that the port you specify is not busy, otherwise the prerequisite check fails. If you do not specify a port here, then the Agent Deploy application automatically picks up a free port (3872 or in the range of 1830 - 1849).In the Additional Parameters section, specify the parameters that you may want to pass during installation. You can specify multiple parameters, separated by a white space.
Oracle recommends you to specify only those parameters that you want to run in addition to the general parameters you have already provided in this page for installation. For example, in step (5), you are providing the port. Therefore, for additional parameters, try to avoid specifying the port again. If you still do so, then the value you specified in step (5) will be ignored and the value you specified here will be used instead.
Note:
Besides the timezone parameter (
-z), you can also specify all the parameters that are supported by the agentDownload script. See 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 Management Agent and the OMS. Alternatively, the super administrator can approve the addition of new agents to Grid Control after the installation is complete.
Note:
An unsecure Management 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.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 Management 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 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 if you are using Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or lower. A recommended course of action is to fix the failed prerequisites before proceeding with the installation. However, if you are using Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher, then you can still continue 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 Management 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.
This section describes how you can install a Management Agent using the nfsagentinstall script. In particular, this section covers the following:
Note:
If the installation fails, review the log files described in Appendix C, "Agent Log Files".In this installation method, the software bits of a Management Agent are shared on a NFS disk, and other hosts share these binaries to run the Management Agent processes on each of the hosts. The one that shares its binaries, in this context, is called Master Agent, and the one that is installed by the nfsagentinstall script is called NFS Agent. Here, the configuration files for each host are stored in the 'State Directory'.
However, this installation method, has the following limitations:
You can perform only one nfsagent installation per host. Multiple nfsagent installations on the same host will fail. If you try to install multiple nfsagents, then the following warning and recommendation appear:
Warning: An agent home exists in the specified oracle home
Recommendation: Uninstall the existing agent that exists in the specified oracle home
This installation type is not supported on clusters. In order to monitor clustered hosts or RAC databases, the best practice would be to use the Agent Deploy application with the cluster option rather than the NFS deployment model.
This installation type is not supported on an Oracle Cluster Shared File System (OCFS) drive, but is supported on an NAS (Network Attached Storage) drive.
Before installing a Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 10-3 Prerequisites for Installing a Management Agent Using nfsagentinstall Script
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the hardware and softwrae requirements. For hardware requirements, see Hardware Requirements. For software requirements, see Software Requirements. |
|
|
Operating System Requirements |
Check if that operating system on which you are going to install the Management Agent is ceritified. For information about certified operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Install the packages that are required for your operating system. For information about packages, see Appendix G, "Check Platform-Specific Package Requirements for Agent Installation". |
|
|
Operating System Group Requirements |
Ensure that you are part of the same operating system group that installed Oracle Application Server and/or Oracle Collaboration Suite. |
|
|
User and Operating System Group Requirement |
Ensure that the target host where you want to install the Management Agent has the appropriate users and operating system groups created. For information about creating operating system groups and users, see Operating System Groups and Users Requirements. |
|
|
Operating System Requirements |
Ensure that the operating system (and version) of the target host where the NFS Agent needs to be installed is the same as the operating system (and version) of the host where the master agent is located. If the target host has a different operating system, then the NFS Agent installation will fail. For example, if the master agent is on Red Hat Linux Version 4, then the NFS agent can be installed only on those host that run Red Hat Linux Version 4. If you try to install on Red Hat Linux Version 3 or a different operating system for that matter, then the NFS installation will fail. |
|
|
Path Validation Requirements |
Validate the path to all command locations. For more information, see Validate All Command Locations. |
|
|
Permission Requirements |
Ensure that you have read, write, and execute permissions to For information about oraInventory permissions, see Installing Enterprise Manager Grid Control As the First Oracle Software. |
|
|
User Credentials Requirements |
Ensure that you use the same user credentials that were used to perform the master agent installation (the main Management Agent that is sharing its binaries). |
|
|
Verifying oraInst.loc and inventory_loc |
If this shared agent installation is not the first Oracle product installation and your home directory (of the master agent installation) is shared, then you must verify the If The inventory_loc=/<any location other than the home directory>/oraInventory inst_group=<group to which the user belongs> |
|
|
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is abc and user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory. |
|
|
Default Port Requirements |
Ensure that the SSH daemon is running on the default port (that is, 22) on all the target hosts.
|
|
|
SUDO Requirements |
Ensure that you have SUDO privileges to run To verify whether you have SUDO privileges to run these files, access the
|
|
|
PubkeyAuthentication Parameter Requirements |
Ensure that the To verify the value of this parameter, run the following command:
The result of this command must be Yes. If the result is No, then edit the |
|
|
NFS-Mounted Location Requirements |
Ensure that the NFS-mounted shared location is always readable from the remote hosts. |
|
|
Agent User Account Permissions and Rights (For Microsoft Windows) |
(For Microsoft Windows) Ensure that the agent user account has permissions and rights to perform the following:
To verify whether the agent user has these rights, follow these steps:
|
|
|
Permissions for cmd.exe (For Microsoft Windows) |
(For Microsoft Windows) Grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
You can view the prerequisite checks and installation status from the Status screen in the Agent Deploy application. For more information about prerequisite checks related to Agent Deploy application, see Appendix G, "Agent Deploy Application - Installation Prerequisites".
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 perform a Management 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 Management 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 Management 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 Management Agent binaries, including the host on which you performed the master agent installation.
If this Management 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 execute this command manually.
Note:
If you already have targets running on the host where you are installing the NFS Agent, then after the NFS Agent installation completes successfully, the targets are automatically discovered and added to Grid Control. However, if you install another target on that host after the NFS Agent installation completes, then you must manually discover that newly installed target by running theagentca script from the <NFSAGENT_STATEDIRECTORY>/bin directory../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 Management 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 run the following command from theEMSTATE directory after completing the installation:
<EMSTATE Dir>/bin ./emctl control agent runCollection <Host name>:host Inventory
This section describes how you can install a Management Agent using the agentDownload script. In particular, this section covers the following:
Note:
This installation method is supported on Microsoft Windows only from Enterprise Manager 10g Grid Control Release 2 (10.2.0.2).Note:
If the installation fails, review the log files described in Appendix C, "Agent Log Files".The agentDownload script uses the pull technology for Management Agent installations. That is, it it not necessary for the script to exist on a local file system, it must always be run 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 Management Agentinstallation on a cluster environment. See Installing on a Cluster for more information.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 OMS Web server.
The OMS instantiates the response file with the name and port number of the OMS. As a result, the Management Agent you install is configured to use the OMS from which the response file was downloaded.
Downloads an Oracle Universal Installer JAR file for the target operating system from the OMS Web server (for UNIX only).
Extracts Oracle Universal Installer and points it to the product definition file (products.xml) hosted by the OMS 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 Grid Control 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 OMS, 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 10-4.
Table 10-4 AgentDownload Script Options
| Option | Description |
|---|---|
|
-b |
To specify base directory of the Agent Oracle home. |
|
-c |
To specify the cluster nodes ("CLUSTER_NODES={node1,node2,node3}") Note that there should not be any spaces between the entries in the comma-separated nodes list. Also ensure that you specify only short names of the host, not their fully-qualified names. |
|
-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 location to the oraInst.loc file. The oraInst.loc file contains the complete path to the inventory directory. This option can be used to point the installer to a non-default inventory. (For advanced users only.) |
|
-l |
To specify as local host (pass -local to runInstaller) |
|
-m |
To specify the OMS host name for downloading the Management 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 OMS host name. |
|
-R |
To use virtual host name(ORACLE_HOSTNAME) for this installation. If this is being used along with more than one cluster nodes through "-c" option, then "-l" option also needs to be passed. |
|
-t |
Do not automatically start the Management Agent at the end of the installation. |
|
-u |
To upgrade. |
|
-v |
To specify the location to the inventory directory. For example, /scratch/oraInvenotry. |
|
-x |
To debug output: Turns on shell debugging. |
|
-N |
Do not prompt for Agent Registration Password. |
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 Management Agent, and so on).
Allows installation onto clustered environments.
Before installing a Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 10-5 Prerequisites for Installing a Management Agent Using agentDownload Script
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the hardware and softwrae requirements. For hardware requirements, see Hardware Requirements. For software requirements, see Software Requirements. |
|
|
Operating System Requirements |
Check if that operating systemon which you are going to install the Management Agent is ceritified. For information about certified operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Install the packages that are required for your operating system. For information about packages, see Appendix G, "Check Platform-Specific Package Requirements for Agent Installation". |
|
|
Operating System Group Requirements |
Ensure that you are part of the same operating system group that installed Oracle Application Server and/or Oracle Collaboration Suite. |
|
|
User and Operating System Group Requirement |
Ensure that the target host where you want to install the Management Agent has the appropriate users and operating system groups created. For information about creating operating system groups and users, see Operating System Groups and Users Requirements. |
|
|
Permission Requirements |
Ensure that you have read, write, and execute permissions to For information about oraInventory permissions, see Installing Enterprise Manager Grid Control As the First Oracle Software. |
|
|
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is abc and user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory. |
|
|
Host Name Requirements |
Ensure that the name of the host on which the installation is being performed is neither At the time of invoking the installer, you can pass Do not pass the argument as |
|
|
Install Directory Requirements |
Ensure that the installation base directory does not contain any other Oracle software. Ensure that this location is not a symlink. Ensure that you have write permission on this location to create the |
|
|
OMS Requirements |
Ensure that you already have an OMS running in your enterprise because the agentDownload script needs to be downloaded from the OMS host. |
|
|
File-Protection Setting Requirements |
Ensure that the execute binary is set and the script file has proper file-protection settings. You can use |
|
|
WGET Requirements |
The |
|
|
SUDO Requirements |
Ensure that you have SUDO privileges to run To verify whether you have SUDO privileges to run these files, access the
|
|
|
Load Balancer Requirements |
If the OMS is using a load balancer, you must modify the
|
|
|
Agent User Account Permissions and Rights (For Microsoft Windows) |
(For Microsoft Windows) Ensure that the agent user account has permissions and rights to perform the following:
To verify whether the agent user has these rights, follow these steps:
|
|
|
Permissions for cmd.exe (For Microsoft Windows) |
(For Microsoft Windows) Grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
The downloadable Management Agent software for the operating system of the OMS host is available on the platform-specific CD from which the OMS was installed, and from the Oracle Technology Network Web site under Mass Agent Deployment at:
fhttp://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
See Downloading Management Agent Software for Different Platforms for more information on obtaining Management Agent installables for different platforms.
The agentDownload script is downloaded to a target node and run to initiate a silent Oracle Universal Installer session. The Management Agent files are copied from the staging area of the OMS home to the target node using HTTP.
To install a Management Agents, do the following:
Ensure that you have the correct version of the agentDownload script that you want to download and use for installing the Management Agent.
The agentDownload script is part of the Management Agent software that is available in the agent_download directory within the Oracle home directory of the OMS. For example, ORACLE_HOME/sysman/agent_download/<version>/<platform>/agentDownload.<platform>
This agent_download directory is the Web server alias created by OMS installation. The directory maps to a physical directory in the Oracle Application Server home directory where the OMS is installed and deployed. Using this Web server alias, you can download the script to the target host using the OMS URL.
The <version> is release of the Management Agent software. If you want to use a higher release of the Management Agent software or for another platform, then you can download the software for that release or platform from the following URL:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
After you download the latest, you will have to extract the contents in the correct directory location. For information about this, see Downloading Management Agent Software for Different Platforms.
Download the agentDownload script to the target host from the OMS URL.
As described in the previous step, using this Web server alias, you can download the script to the target host using the OMS URL. For example, if OMS is installed on mgmthost27.acme.com, then download the agentDownload script from the following URL:
http://mgmthost27.acme.com:4889/agent_download/<version>/<platform>/agentDownload.<OS>
For Microsoft Windows, the URL to download the script is as follows:
http://mgmthost27.acme.com:4889/agent_download/<version>/win32/agentDownload.vbs
For Microsoft Windows, you can also access the agentDownload script from the command line by running one of the following commands:
wget http://mgmthost27.acme.com:4889/agent_download/<version>/<platform>/agentDownload.<OS>
wget http://mgmthost27.acme.com:4889/agent_download/<version>/win32/agentDownload.vbs
Note:
The default port for Grid Control is 4889. This should be available after you install the OMS.
The <version> argument represents the version of the Management Agent avaliable on OMS host.
The <OS> argument represents the platform. For example, for Linux, the script is named agentDownload.linux. For Windows operating systems, the script is named 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/
Run the following command to invoke the agentDownload script on the target host.
./agentDownload.<platform> -b <base directory> -m <full path to the OMS host> -r <port>
The base directory is the location in which the Oracle home directory for the Management Agent will be created. For example, if you specify /scratch/agent_download as the base directory, then agent10g is created as a subdirectory in this base directory.
For information about the other arguments that can be used in this command, see Table 10-4, "AgentDownload Script Options". Alternatively, you can run the following command to see online help:
./agentDownload.<platform> -help
After the installation completes successfully, run the following scripts as a root user from each of the hosts.
If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the Central Inventory:
$ORACLE_HOME/oraInventory/oraInstRoot.sh
For example, if you are using sudo to change to a root user, then you will run the following command:
/usr/local/bin/sudo $ORACLE_HOME/oraInventory/oraInstRoot.sh
Run the root.sh script from the Oracle home directory of the Management Agent:
<agent_oracle_home>/root.sh
For example, if you are using sudo to change to a root user, then you will run the following command:
/usr/local/bin/sudo /scratch/OracleHomes/agent10g/root.sh
The root.sh script must be run as root; otherwise, the Grid Control job system will not be accessible to the user. The job system is required for some Grid Control features, such as hardware and software configuration tasks and configuring managed database targets.
Finally, secure the Management Agent.
For Management Agents 10g Release 2 (10.2.0.2) or lower, secure the Management Agent by running the following command. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.
<Agent_Home>/bin/emctl secure agent
For Management Agent 10g Release 3 (10.2.0.3) or higher, secure the Management Agent in one of the following ways:
Set the environment variable AGENT_INSTALL_PASSWORD
Set the password in the agent_download.rsp file.
Do not perform Step (6.a) and Step (6.b) so that you can be prompted by the script. At the prompt, provide the Management Agent registration password.
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 10-6.
Table 10-6 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 Management 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
You can edit the contents of the agentDownload script so it uses a specific tool for transferring files from the OMS 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 agentDownload for Unix
Follow the instructions below to download the Management Agent installation software for Unix:
Download the <platform>_Grid_Control_agent_download_10_2_0_X.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.X.0 directory.
Note:
Create the<OMS_HOME>/sysman/agent_download/10.2.0.X.0 directory, if it does not exist.Go to this directory by executing the following:
cd <ORACLE_HOME>/sysman/agent_download/10.2.0.X.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_X.zip
If the agent_download.rsp file does not exist in the <OMS_HOME>/sysman/agent_download/10.2.0.X.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 OMS, 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.X.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 Management Agent installation software for Windows:
Note:
Ensure that you have Microsoft Internet Explorer version 6.0 or higher installed on the host where you are downloading the script.Download the Win32_Grid_Control_agent_download_10_2_0_X.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.X.0 directory.
Note:
Create the<OMS_HOME>/sysman/agent_download/10.2.0.X.0 directory, if it does not exist.Go to this directory by executing the following:
cd <OMS_HOME>/sysman/agent_download/10.2.0.X.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.
Extract the contents of this file by running the following:
unzip Win32_Grid_Control_agent_download_10_2_0_X.zip
After extracting the contents, the agentdownload.vbs will be available at <OMSHOME>/sysman/agent_download/10.2.0.X.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 Management Agent host. This is required for the script to be executed successfully.Run the agentDownload.vbs script:
cscript.exe agentdownload.vbs -b <basedir name> -m <omshostname> -r <httpport>
For example:
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 <basedir name> -m <omshostname> -r <httpport> -c <node1, node2, node3...> -n <cluster_name> -l
For example:
cscript.exe agentdownload.vbs - b /oracle/agentinstall -m foo.us.oracle.com -r 4889 -c "host1,host2,host3" -n myCRS -l
This section describes how you can install a Management Agent using Oracle Universal Installer. In particular, this section covers the following:
Note:
If the installation fails, review the log files described in Appendix C, "Agent Log Files".Oracle Universal Installer (OUI) is an interactive, GUI-based installer offered by Oracle for all its products. The OUI referred here is the installer provided for Enterprise Manager 10g Grid Control Release 2 or higher.
The default port for Management Agent is 3872. For more information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see Knowing About the Ports Used for Installation.
Note:
By default, this installation option from Oracle Universal Installer uses the Management Agent software that is arealdy available on the host running OMS, and installs Oracle Management Agent 10g Release 1 (10.2.0.1). If you need the latest release of Management Agent, then you must patch this first release with the help of the latest patch set. The patch sets are available on My Oracle Support (formerly Metalink) at:Alternatively, to install the latest release of Management Agent, you can use the Management Agent software kit (full kit) that is available on Oracle Technology Network (OTN) at:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
You can accept the license agreement, download the software kit (zip file), extract the contents, and invoke the runInstaller from there to start Oracle Universal Installer.
Note:
Grid Control does not support uploading of data to the same Management Repository from two Management Agents running on the same host.Before installing a Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 10-7 Prerequisites for Installing a Management Agent Using OUI
| Requirement | Description | Yes/No |
|---|---|---|
|
Hardware and Software Requirements |
Ensure that you meet the hardware and softwrae requirements. For hardware requirements, see Hardware Requirements. For software requirements, see Software Requirements. |
|
|
Operating System Requirements |
Check if that operating systemon which you are going to install the Management Agent is ceritified. For information about certified operating systems, see Operating System, Browser, Target Certification. |
|
|
Package Requirements |
Install the packages that are required for your operating system. For information about packages, see Appendix G, "Check Platform-Specific Package Requirements for Agent Installation". |
|
|
Operating System Group Requirements |
Ensure that you are part of the same operating system group that installed Oracle Application Server and/or Oracle Collaboration Suite. |
|
|
User and Operating System Group Requirement |
Ensure that the target host where you want to install the Management Agent has the appropriate users and operating system groups created. For information about creating operating system groups and users, see Operating System Groups and Users Requirements. |
|
|
Permission Requirements |
Ensure that you have read, write, and execute permissions to For information about oraInventory permissions, see Installing Enterprise Manager Grid Control As the First Oracle Software. |
|
|
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is abc and user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory. |
|
|
SUDO Requirements |
Ensure that you have SUDO privileges to run To verify whether you have SUDO privileges to run these files, access the
|
|
|
Install Directory Requirements |
Ensure the location where you are installing the Management Agent does not contain any other Oracle software. Ensure that the directory under which you are installing the agent is not a symlink. |
|
|
Host Name Requirements |
Ensure that the name of the host on which the installation is being performed is neither At the time of invoking the installer, you can pass Do not pass the argument as |
|
|
Agent User Account Permissions and Rights (For Microsoft Windows) |
(For Microsoft Windows) Ensure that the agent user account has permissions and rights to perform the following:
To verify whether the agent user has these rights, follow these steps:
|
|
|
Permissions for cmd.exe (For Microsoft Windows) |
(For Microsoft Windows) Grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
WARNING:
The installation procedures given in the following sections are for installing full, base release of Oracle Management Agent, which is part of Enterprise Manager 10g Grid Control Release 2 or higher. For details about full, base releases and what these installation instructions can be use for, see Understanding What This Guide Helps You Install and Upgrade.Start the Oracle Universal Installer by running the runInstaller script in Linux (<DVD>/runInstaller) from the top directory of the DVD.
In the Specify Installation Type screen, select the fourth option (Additional Management Agent), and specify the parent directory path and installation name.
In the Specify Installation Location screen, specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. The agent home created during the installation is placed as a sub-directory under this parent directory. For example: agent10g.
Note:
Ensure you do not use symbolic links to the Oracle home path.The installer by default installs the selected products in the English language.
The Product Specific Prerequisites Checks screen appears.
This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.
Depending on the status of the automatic checks, you must verify all warning and manual checks. To do this, select the appropriate prerequisite status check box and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen.
Note:
You can also run these prerequisite checks in standalone mode, prior to starting the
runInstaller. For more information on running these prerequisite checks in standalone mode, see Running the Prerequisite Check in Standalone Modefor more information.Click Next. The Specify Oracle Management Service Location screen appears.
Specify the OMS host name. For example: dlsun1444.acme.com. Use the fully qualified host name (including domain). If your OMS is behind a Server Load Balancer (SLB), then specify the SLB host name.
Caution:
When specifying the host name, ensure you do not include the protocol (that is,
http:// or https://).Enter the port number for the OMS. The default port is 4889 and the default secure port number is 1159. If your OMS is behind an SLB, then specify the SLB port number.
Note:
If you are installing Oracle Management Agent 10g Release 4 (10.2.0.4 or lower), not using a patch set but using a full Management Agent software download, then for Management Service Port, you must specify only a nonsecure port number (4889) even if you are specifying a secure and locked OMS. You must connect over HTTP to receive the certificate before you can connect over HTTPS.
If you are installing Oracle Management Agent 10g Release 5 (10.2.0.5 or higher), not using a patch set but using a full Management Agent software download, then for Management Service Port, you can specify either a secure port number (1159) or a nonsecure port number (4889).
If your OMS has been secured and locked, you are prompted to enter the Agent Registration password (used to secure the OMS environment). If you do not know the password, obtain it from the user who configured the OMS for SSL.
Click Next. If the OMS is found to be running in a secure mode, the Specify Agent Registration Password screen appears. You must provide the correct password to enable communications between the new Management Agent and the Secure Sockets Layer (SSL)-enabled OMS.
Note:
If you do not know the password and choose to leave the Password field blank, you must do the following after installation to enable communication between the Management Agent and secure OMS:Find out the correct password for the secure and locked OMS environment. If you do not know the password, obtain it from the user who configured the OMS for SSL.
If you have forgotten the password, then you can reset the password from the Grid Control console. Login to Grid Control as SYSMAN, select Setup from the top-right corner of the page, select Registration Passwords from the left menu panel, and on the Registration Password page, click Add Registration Password.
In the <AGENT_HOME>/bin directory, run the following command:
emctl secure agent -reg_passwd <password>
The variable <passwd> should be replaced with the Agent Registration password.
emctl secure agent
When you execute this command, you will be prompted to specify the Agent Registration password. However, note that even after securing the Management Agent, some data might still be transferred over the network without being encrypted.
Click Next. The Summary screen appears.
This screen displays a summary of the options that you have selected during the installation process. Depending on the installation type, this screen displays any or all of the following details:
Global Settings
Product Languages
Space Requirements
New Installations
For more information on each of the previously listed details, see the Grid Control online Help.
Verify the choices that you have made and click Install to start the installation. The installer starts installing the selected Oracle product.
During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only for Linux).
To execute these scripts, go to the computer window, log in as root, and run these configuration scripts.
Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.
The Configuration Assistants screen appears. At this point, the installer starts running the recommended configuration tools.
This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in Configuration Assistants Fail During Enterprise Manager Installation.
After successfully running all the recommended configuration tools, click Next. The End of Installation screen appears.
This screen displays some important information about the products you have installed. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.
For example, it might contain information about the URLs for particular Web applications.
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
|
 Copyright © 1996, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
