Database Reference
In-Depth Information
If you like, you can add the agent home to the oratab file just as you would with a database:
agent:/u01/app/oracle/agent12c/core/12.1.0.2.0:N
You can then use the oraenv utility to switch back and forth Oracle homes as you do with the database. You do
not need to worry about a start script, the agent installation creates such a script named /etc/init.d/gcstartup to
automatically start and stop the agent when a runlevel changes.
The installation process can easily be scripted and packaged in the form of an RPM for example. All you need to
do in order to fully automate the agent deployment is to:
Provide a common, well-known location for the file.
Configure the sudoers file to allow Oracle to execute the root.sh script as root.
Make the zipfile available on the destination host for your platform.
Provide the response file.
Execute the agentDeploy.sh script as part of the post-install scriptlet in RPM.
Change the sudoers file again and revoke the permission to execute root.sh.
In very security-conscious environments it might be difficult to get permissions to change the sudoers file. In
these environments you need to ensure that a qualified system administrator with root access to the destination host
is available to execute the final step in the installation procedure.
Getting Agent Software for Different Platforms
Unlike with Enterprise Manager 11.1 and before you cannot download the agent software from Oracle's OTN website
anymore. This is quite startling at first, but the new process is very elegant and compensates you for the missing agents.
You read earlier in this chapter that Enterprise Manager is built around a plugin infrastructure. As such only required
functionality is deployed initially, updates and new functionality are available via Setup Extensibility Self Update.
To use the Self-Update functionality you need to have configured access to My Oracle Support. Figure 8-19 shows the
main interface to the Self-Update functionality.
 
Search WWH ::




Custom Search