In this part, I am going to discuss how to install agents manually on a node
1. Port 383 must be opened bi-directional between management server and managed node.
A. On Management server:
1. Identify the agent’s binaries. Usually, agent’s binaries will be located under vendor directory.
Format of the agent’s binaries location under vendor:
2. Read OVO-Agent.xml file under RPC_BBC directory, to check the agent’s current version.
Above line states agent’s current version is 8.60
3. Compress RPC_BBC directory and name it as below (depending on OS and Agent version)  and give required permission using chmod.
Example: Linux-8.60.tar.gz
4. Transfer the compressed agent’s binaries to managed node using scp, ftp, telnet, etc. whichever is feasible.
B. On Managed Node:
1. Extract the copied agent’s compressed binaries using tar or winrar to /tmp (Unix) or C:\temp (Windows)
2. Navigate to extracted location. In case of Windows, use command prompt.
3. Add the management server’s entry in host file or in DNS server to resolve the name resolution.
4. Execute installation script
# ./ -s
In Windows
# cscript opc_inst.vbs -s
where is the name of the primary management server
Here, I am assuming that certificate server is same as primary management server and agent need to be installed on default path.
5. Check the agents status by executing
# ./ovc -status
# ovc -status
If PATH environment variable is not set for OVO agents, you can either set the PATH or you can navigate to install directory of agents
In UNIX: /opt/OV/bin
In Windows : C:\Program Files\HP OpenView\bin or C:\Program Files\HP\HP BTO Software\bin
All the agent’s processes should be running.
6. Check the certificate status from install directory
# ./ovcert -status
In Windows
# ovcert -status
If the status is pending, You can skip the next step
7. Request new certificate, if status is not pending
# ./ovcert -certreq
In Windows
# ovcert -certreq
In next part, I will discuss how to add a node in OMU from command line.