Hi Anmol,
Have you investigate to use the callback of the probes ?
For all action listed below, use PU (probe utility), to test all of the callback concerned. PU is available on each robot in the "bin" folder for the command line version. Inside "Infrastructure Manager", just use the "CTRL + P" combo on a probe previously selected. Inside the web admin console, PU is available by the contextual menu of the probes (represent by a sequence of 3 dots verticaly disposed)
You can create (for example), a Lua script in the scripting interface of the nas probe, that use :
- the callback with the name like "hub list" on the near hub probe, to get the list of all hubs in your infrastructure. (you can get the "nimbus path" of the hub, like /domain/hub/agent, by the usage of a callback on the local controller probe)
- In a loop (based on the previous call answer), you can use the callback name like "robot list" on each hub.
- In a subloop (based on the previous call answer), you can use on each robot, the callback on the probes ntservices, to get the list of profils.
- In another subloop, to filter the results on the profiles with the attribute "active" equal to "yes". (store in an array for example).
It's possible with Lua to use a large of native capabilities to externalized the result (mail, databases, flat files ...)
To externalize by an API, you can use a system call with your lua script, to execute, with customized arguments, an external curl binary (for example).
All about this, is available :
- with Perl, VB, JAVA, C, .Net ... if you want to create a customized probe.
- A good way, if you want to use an external mecanism, is the "pu" binary. It's userfull with Shell scripts or solutions like TALEND OpenStudio.
In case where my answer is out of subject, compare to what your really need, not hesitate to add more details about your constraints !
Best regards,
Jonathan