This OBE shows you how to install Oracle Management Agent on a host using the Agent Push method. In the process, you learn the pre-installation and the post-installation tasks for the agent push method.
Approximately 1 hour
This OBE covers the following topics:
|
Overview | |
|
Deploying Oracle Management Agent using the Agent Push Method | |
|
Summary | |
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.
The screenshots will not reflect the specific environment you are using. They are provided to give you an idea of where to locate specific functionality in the Oracle Enterprise Manager 10g Grid Control console.
Agent Push is a J2EE application that enables you to access it over the Internet. This application is used for mass deployment of Management Agents. It uses SSH to transfer files and execute remote commands (thus this installation method is not appropriate for environments that do not use, or block, SSH connections).
Perform the following steps to install an agent on a host:
| 1. |
Before you actually start the agent installation it is recommended to look at the Oracle Enterprise Manager 10g Grid Control Release 2 Firewall Port requirements. It will help you understand the ports that need to be open in your firewall for the successful implementation of the Grid Control stack.
|
|
2. |
In order to prepare a host as a destination for Agent deployment using the Agent Push method, you must run a script to set up ssh equivalence between the Oracle Management Server (OMS) host and the hosts to which you want to deploy the agents. The purpose of the script is to allow seamless access by a user on the OMS host onto the target hosts. Without configuring this equivalency, the connection between the OMS host and the target hosts will continually be interrupted by requests for password authentication, thus removing the non-interactive capabilities of the application. This equivalency is only one way from OMS host to the target hosts. The script sshConnectivity.sh can be found in $OMS_HOME/sysman/prov/resources/scripts directory on the OMS host. Along with the script specify the list of hosts and the OS user account information which will be used to deploy the agent on the target hosts. Execute the script as shown below: ./sshConnectivity.sh
-hosts edidr5p0.us.oracle.com -user oracle
Note: You can specify multiple hosts if the OS user credentials are same on all the hosts.
|
|
3. |
When prompted "Do you want to continue and let the script make the above mentioned changes (yes/no)?". Type yes and press the Enter key.
|
| 4. |
In order to test that the equivalency has been successfully created, the scripts will finish by attempting to run the “date” command remotely on the target hosts via SSH; if the final output is the date, then configuration succeeded. If the user is asked for a password once more while running the date command, then SSH connectivity was not successfully established.
Note: After the equivalency is established you can execute the following command to confirm it. $ /usr/bin/ssh -x -l oracle edidr5p0.us.oracle.com date The output of the above command should be the current date. If you prompted for a password then the equivalency is not properly established and you might have to rerun the sshConnectivity.sh script.
|
| 5. |
After successful execution of the script, open a browser window and login to Grid Control as sysman user.
|
| 6. |
Click the Deployments tab.
|
| 7. |
Click the Install Agent link under Agent Installation section.
|
| 8. |
Click the Fresh Install link.
|
| 9. |
On the New Agent Installation page keep the default option button selected
for the Source Shiphome Directory. The source shiphome directory is located
within the Management Server.
It is worth noting the default location for Source Shiphome. This is
the "Agent Download" directory of the OMS. Thus, only Agents
for operating systems that have had their installation files placed in
that directory can be deployed using this application.
|
| 10. |
Scroll down to OS Credential section to specify the host OS credentials. They must also be the same credentials used when running the sshUserSetup.sh. If this user has “sudo” privileges enabled on the remote hosts, then having the deployment process run the root.sh script is recommended. Since sudo user is not enable for the host, deselect the Run root.sh check box.
|
| 11. |
Specify the base directory for the agent installation. Make sure that the specified base installation directory is empty. In most cases, there is no need to specify a port, as the application is able to detect a free port to use. Note that if a port is specified in this field, that port will be used for all hosts being deployed onto, regardless of whether that port is free or not. Specify any additional parameter that you want to pass during the installation.
|
| 12. |
Scroll down to Management Server Security section and specify the registration password. Providing the password will configure the agents to run in secure mode after installation. After all the required details are provided click the Continue button.
Providing the Oracle Management Server (OMS) registration password will
configure the agents to run in secure mode (over HTTPS) after installation.
The password should be provided depending on the requirement of secure
communication and the Oracle Management Server state (locked/unlocked).
If it is unlocked then both secure and insecure agents can talk to the
Oracle Management service. If it is locked then only secure agents can
talk to it.
|
| 13. |
The application will check for any connection problems with any of the hosts.
|
| 14. |
Next it will perform some prerequisite checks to ensure if the destination hosts support the selected platform and the minimum requirements for the agent install are met. If any of the prerequisite checks fail, then you have to rectify the error and try the installation again.
To find more about the prerequisite checks and how to resolve any issue that might occur during the prerequisite check click here.
|
| 15. |
After all the checks are over the application will start to install the agent.
|
| 16. |
The agent is successfully installed. The last step now left is to run the root.sh file.
Click here to know the installation log files.
|
| 17. |
Login to the target host as the root user. Navigate to the $AGENT_HOME directory and execute the root.sh file. When prompted for local bin directory, press the Enter key to accept the default value.
|
In this lesson, you learned how to:
|
Deploy Oracle Management Agent using the Agent Push method | |
Place the cursor over this icon
to hide all screenshots.