DX UIM ADE probe callbacks explained.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are looking to improve probe deployment by setting up remote local archives.

From my understanding of the online documentation at https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-4/administering/Probe-Deployment-Forwarding-Functionality-in-ADE.html,

it states that ADE requires distsrv rules to make remote local archives accessible.

However, when I search for "automated_deployment_engine" and do a ctrl+p, I see several callbacks that seem to indicate we need some customization in ADE to utilize a remote archive.

I'm unclear about the need and explanation for the following ADE callbacks, as I can't find any references or documentation on them:

- set_package_sync_master
- create_ade_forward_queue
- add_package_sync_rule

Environment

DX UIM 23.4 CU1

OS: Windows 2019 

Resolution

Find below the ADE callbacks details:

- add_package_sync_rule

Creates a new archive sync rule for this ADE to distribute to its children. When called on a parent ADE probe, any child ADE probes that have called “set_package_sync_master” check to the contents of their archive based on the specified rule.

If a child ADE probe(s) does not have a package specified by a rule it will contact the parent ADE probe and download it to archive underneath the child ADE probe.

 

- set_package_sync_master
Establishes a parent-child relationship from the called ADE probe to the ADE specified using the “robot” parameter.

When this callback is called, the called ADE probe downloads the set of rules that are on the parent ADE probe.

It also begins the process of the initial sync with the parent to make sure the contents of parent archive are in sync with the called ADE probe.

 

- create_ade_forward_queue

Creates a new queue on the local hub that forwards messages onto a remote queue.

Please disregard my initial email on this matter, as it contained information that our L2 team has since confirmed to be irrelevant to your case.