Here are some further details/clarifications:
- automated deployment_engine
The automated_deployment_engine (ADE) probe enables you to deploy robots in bulk. Deploying ADE on a remote hub allows you to deploy robots in bulk to robots that were discovered via USM, that belong to a remote hub that the Primary hub cannot directly reach. To use ADE from the UMP USM portlet, ADE must be installed on the remote hub that the robot(s) will be reporting to.
The discovery_agent probe scans the IT network, pinging and querying devices according to subnet masks/ranges, credential profiles, and selected profiles. These scanning parameters are configured within the Discovery Wizard. You must deploy discovery_agent to discover any servers/devices that the discovery_server or discovery_agent on the Primary hub cannot reach on its own. You can also deploy discovery_agent(s) to offload processing from the Primary in medium-to-large environments. The most important consideration is that the target IP addresses can be reached from the installed discovery agent location. For further details see: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/9-0-2/installing/discover-systems-to-monitor/configuring-discovery/discovery-probe-deployment.html
- nas and alarm_enrichment
Deploy nas and alarm_enrichment on a remote hub to either a) offload nas AO profile/preprocessing scripts/rules or b) for alarm forwarding and replication when not using ATTACH and GET queues. Please see my discussion of some architectural considerations at this link towards the bottom of the KB Article: https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=34973