if you want to use properties and such then the approach is:
- define the path properties, etc
- run a nsh/blcli script that finds all of the possible locations for httpd, creates psis in the template and then sets the possible values, config files, etc.
- run discovery
- run compliance
then benefit would be that you could use a blpackage to remediate this.
another approach is to write a script that does the 'find' (locally) and does the check for the configurations you want and then spits out a pass fail, probably w/ some pathing information and then the compliance condition is that your EO spits out 'pass'. and the remediation would have to be another script called by a blpackage to do the find again and fix up the files.
if you are on 8.5 you might be able to use the new 'command' construct in the condition to do the find and variable assignment - Defining a basic condition - BMC Server Automation 8.5 - BMC Documentation it looks promising but i haven't had a chance to mess w/ it much.