Agents

Agents are provided for quite broad range of architectures and for many products (not only of Oracle origin). They work on hosts of targets and fulfill the role of a middle-man between Oracle Management Service (OMS) and target.

Agent is not the same as Database Console agent. You need to install agent provided in full installer or in Mass Agent Deployment section (depending on the architecture of target's host).

Agent software is installed on targets in two ways:

1. running Grid Control installer on target's host and choosing option Additional management agent
2. downloading agent and installing it within OMS_HOME/sysman/agent_download

Example of installation of agent for Solaris x64 for deployment:

1. download Solaris_x64_GridControl_agent_download_10_2_0_2_0.zip
2. create directory OMS_HOME/sysman/agent_download/10.2.0.2 if it does not exist
3. unzip zip file within the newly created directory
4. move agent_download.rsp.bak to agent_download.rsp, if agent_download.rsp does not exist
5. modify agent_download.rsp file
• %s_OMSHost% to correct OMS host
• %s_OMSPort% to correct port (default 4889)
• optionally one can set also %s_encrSecurePwd% (agent secure registration password) - there will not be the question about said password during installation
6. modify OMS_HOME/sysman/agent_download/10.2.0.2.0/solaris_x64/agentDownload.solaris_x64 in the same way as agent_download.rsp

Example of final installation of agent for Solaris x64 on a remote host:

1. one needs to ensure wget utility is provided and path to it within PATH environment variable
   
2. download http://OMS_HOST:4889/agent_download/10.2.0.2.0/solaris_x64/agentDownload.solaris_x64 by let's say wget (of course 10.2.0.2.0 can be substituted by any proper agent version one provided on OMS_HOST, while solaris_x64 architecture can be substituted by any supported archutecture)
   
3. run agentDownload.solaris_x64 on target host (usually one needs chmod u+x agentDownload.solaris_x64; agentDownload.solaris_x64 -b <agent_home_parent> -i <oracle_home>/oraInst.loc -t; during script run one will be prompted for agent registration password, if it was not specified already within agentDownload.solaris_x64 script)
• Configuration assistant "Agent Configuration Assistant" failed - information provided about that failure was rather scarce, <agent_home>/cfgtoollogs/configToolFailedCommands contained only name of a Java class (oracle.sysman.emcp.agent.AgentPlugIn)
• even with some commands failed agent software was installed correctly
• of course due to some problems with confguration I was made to do some additional steps to run agent - for these look "Adding target to Grid Control" post
• the configuration stage failed due to not setting AGENT_INSTALL_PASSWORD environment variable to agent secure registration password (or fulfilling the setting of said password within agent script and response (i.e. rsp) files)
  
4. after that one needs to run script AGENT_HOME/root.sh; however in case of failed installation the script exists somewhere within agentDownload{version}Oui directory. I must admit that after providing proper password (i.e. password configured at Setup->Registration Passwords of the OMS Control Console) installation fails no more. I have found also notices that any listeners should be down while installing agent.