This article explains the differences to use the CLI opr-agt, ovdeploy and UI Tools in OBM and manage node.

Environment

Operations Bridge Manager (OBM) and Operations Agent (OA) all supported versions

Situation

1. The opr-agt requires the action agent to be running but ovdeploy does not.
How the communication works and what subagents are in play in each case.

2. The most robust way to get agent status is through opr-agt. On a daily basis almost 100% success in contacting all nodes that are running and get a status with -status.
When using ovdeploy with -cmd 10% of the agent checks fail when we call opcagt -status. Why?

3. opr-agt requires a username / password when using -cmd. Using an encrypted base64 password in a OBM tool failed. Is there another way to do this?

4. Using policy as an indirect method to get remote status and that appears to be just as robust as opr-agt. Same question. What is the communication path in this case compared to others?

5. opr-agt -status does not list the Buffering status if it is buffering. Why? 

6. Monitored Node use ovdeploy or opr-agt?

For answers to these questions, see the complete knowledge article