you can create local properties and instances in the template for this. the best way is to write a nsh script to 'find' all the stuff you want, run some blcli to setup the property values / instances and then run discovery and compliance w/ the template.
I would love to be able to set local property values/instances on the fly. Are you saying to update the template as part of a “component install” batch? The only problem I foresee (other than I have no idea how to do this with blcli) is permissions. Our users do not have modify rights to our templates…
It’s not a huge need at the moment, I can use other things to verify an application is healthy, but there’s times when being able to check a file version in an unknown location would be extremely handy. Like for instance when only a file version changes as part of a patch/upgrade.
For the most part, apps are installed where they should be, but not always, so I prefer to not assume (I’ve seen some admins redirect their %ProgramFiles% and/or %ProgramFiles(x86)% paths to non-standard locations).
So what you would do is something like this:
Nsh script to find the install dir of your application.
Blcli command in that script to add that as an instance in the CT.
An EO that takes that path as input and runs whatever you need to get a version or use the install path as a property that points to some file or whatever
Compliance rules that use the parameterized paths
You run discovery to find all the instances of your apps – maybe multiple per box,maybe not
Then run compliance, targeting the components.
I think I have an example of this w/ oracle from a while ago if that would be helpful.
An example would be good...I am not dealing with "instance" applications, but whatever you've got may help.
Use BLCLI help to assist you.
Sample create instance
Template createParameterInstance Apache /Applications/WebServers/Unix Dev "Development Environment Values"
Sample set instance property value
Template setParameterInstanceOverriddenValue Apache /Applications/WebServers/Unix Dev install_dir "/opt/apache/dev"
we had some offline discussions - so i think he just needs to create a local EO that gets the info he needs, and then target some compliance rules at that output. the "but that application can be installed anywhere" typically triggers the "you need to use local parameter instances" thought, but in this case, since there is only a single instance per system and he can pull the install location from a know reg key, the EO can do that (w/ reg or blquery) and then run whatever needs to be run.