When re-applying the component template to a server,
-> means you are running a discovery job ? or what ?
it reinstalls all prior installed templates.
-> what other templates ? what is 'it' ?
If none are present, it should just install the "base set".
-> how does bsa know what the 'base set' is ?
I guess I should have been a bit clearer:
I've made a component deploy template (cot), and created the discovery (cdj) and compliance (coj) jobs from it.
the COT has rules defined to check if prior there has been an installation of any of the software components, and sets a local property if any of the software components have been installed before on the target server.
The cot also has 2 local properties defined which control wether or not the base set (being either of the software components) needs to be installed, regardless of what was on the server before.
By default, these are set to False.
What I want, is that after doing discovery, is change the local properties in the discovery job of the target server so that I can tell from within the batch job that is used, what set of software components should be installed. (which is what I referred to as the base set).
So, I'm basically looking for a way to control local properties in a discovery job, from within a batch job. I'm pretty certain it can be done through blcli/nshscript, but I haven't found the way yet.
the rules you have to set the local property values are in the compliance rules section ? but you want the rules in the discovery section to set local properties in the template so that when the next job in the batch (is that the compliance job) runs it will pickup these values ?
That sums it up, yeah.
I've got 4 properties; one to flag that the software component has been installed before (per software component), and one to flag that it should be installed regardless.
Why can’t you handle all of that in your compliance rules ?
Well, I would like to have one component template, and 3 different batch jobs, that allow for
- Install component 1
- Install component 2
- Install component 1 and 2
As such, I put the local properties for the default installation to false on both, and wanted to change these from the batch job.
Afaik the ‘persist’ doesn’t work for discovery conditions, only compliance conditions. but even if that worked i don’t see how you would get this working w/ your method. The persist is tied to the template, not the job.
Hm. Pity. I guess I'll create two separate templates, then.
How do you know if you need only the base vs whatever software ?
Well, on average, you'd only want either software package A or package B. Both can be installed on the same machine. Both depend on a 3rd package, the management agent. I can't upgrade the agent without removing and reinstalling whatever other components are on the system (hence my check-what-is-installed).
So the choice rests with the user installing the stuff.
Hmm – so you might be able to use a JOB property here in the compliance bit – i’m not sure if that would work, then you would just need two compliance jobs.