Using component templates, it's possible to have multiple components of the same type (template) associated w/ a server. think instances of oracle, or instances of weblogic.
if you choose the component specificially, the audit will run against just that one component, if you choose the server and there are multiple instances of your component, all are audited.
if there's only 1 instance of the component, then only that will be audited.
That clears it up somewhat, but the reason
I asked is that the Audit job
has only 1 instance of a component on
the server. When I set up the Audit job using
the server as the target, I would get
"No Targets for audit job .... " warnings
when trying to run the job.
I had to change the Target to
the matching live component itself in order
to get the job to run without warnings.
unless something has changed, i thought you could target servers for audit and compliance jobs using a component template, assuming that the component already exists for that server.
Here's a real world example of my confusion ( BL 7.4.3 ).
I'm setting up an Audit job where I have one
master which is a snapshot of a component.
I have two targets which I'd like to be the live
corresponding components . I'm unable to
use them as targets because I keep getting an error.
I'm forced to define the servers as the targets to avoid
the error. Please see the attached screenshots.
have you changed the template since you've taken the snapshot? that could be the problem, otherwise i'd talk to support about this.
Yes, I did change the template, however I rediscovered
it on the servers and resnapped for a new master.
I'll enter a ticket.
That's correct - always re-snap after updating the template. you've got permissions on all the objects to do what you want right?
if you get a fix, post it back here.
Solved it. Wasn't a problem with permissions
but I forgot my own rule. When something
doesn't work in BL that should, always
try logging completely out and back in again.
Once I did that, I was able to specify the components
I'm not sure what logging out and in again does
( using same ID ) but it's work for me other times