Hi Gene,
> Can you provide more details on how you want the probe to "decide" what to publish?
An example to illustrate what I want: a probe to collect filesystem usage data (yes, I know about cdm, this is just a simple example).
My goal is to make a probe that can completely self-configure after deployment.
To have a "profile" created automatically, I edit the ".cfx" file in the maven project. This way, the "getUpdatedInventory" method will be called and will proceed to enumerate the existing file systems, create a FileElement (or a subclass) object for each one, collect the usage data and return it all.
However, for the data to be actually published (sent to a hub), I need to perform an extra step. I can check the "publish data" checkbox on AC, for example. Or, to automate the task, I could call "pu" and add a "<monitor>" element to the config file and then restart the probe (tried that and it works, by the way).
At this point I wondered if that last bit could be done by the probe itself, avoiding the need for manual intervention or running a script. However, as you said, I found nothing in the sample code. Browsing the api javadocs, there is no obvious way to set a MonitorDef active.
Maybe I am just not thinking the way uim wants me to ...
Thank you for the prompt response and best regards !
Sergio