On your servers, set the value of 'PATH' to /export/home/testerA, testerB, etc appropriately. In the config file object defintion change the path of the file to ??TARGET.PATH??/runExec.sh.
that should do it.
I right click on a server and look at Properties.
However, the Properties pencil/pad icon isn't highlighted.
I've tried this as both BLAdmin and RBACAdmin.
Please see attached screenshot.
Server_Props.jpg 162.2 K
if PATH isn't there, you need to add it under Server in the Property Dictionary, then you can set it on the server. You may not want to use PATH, maybe "APP1_PATH" or some other name that's more descriptive.
A follow-up question. As you suggested, I created a Server Property called
APP_PATH. Then, on each server, I set this property locally.
Server A APP_PATH is set to /export/home/testerA
Server B APP_PATH is set to /export/home/testerB
Server C APP_PATH is set to /export/home/testerC
I then created a component template ??TARGET.APP_PATH??/FILE_X
and discovered the component on each server. Now I have
3 components :
Server A /export/home/testerA/FILE_X
Server B /export/home/testerB/FILE_X
Server C /export/home/testerC/FILE_X
I understand that now since I have similar components, I can choose one server ( for example Server A ) as
the Master and audit the other server's components compared to A's component.
However, I have an additional question.
I have a special directory on Server A that contains a "golden" image of
FILE_X . For example /export/home/testerA_GOLD/FILE_X .
Therefore, I have another Server Property called APP_PATH_GOLD on server A that I set to /export/home/testerA_GOLD .
I create my "golden" component on server A using ??TARGET.APP_PATH_GOLD??/FILE_X
My "gold" component would be /export/home/testerA_GOLD/FILE_X.
How would I audit my three standard APP_PATH components against my "gold" APP_PATH_GOLD component ?
Right idea, but change your implementation. In your component template make a local property named "APP_PATH". Then create four instances of your local properties that define APP_PATH as follows:
Then run your discovery. You will now have four components. Do your audit that way.
Some screenshots of a simple example to show where I'm going wrong.
I want to create a two instances of a component on Server A.
In one instance the group,host, and passwd files are in /etc. - Screen 1.
I set a LOCAL PROPERTY called ETC_PATH to /etc
for the Component Template called "Prop_test_component" . - Screen 2
I discover it and see my component. - Screen 3
Now here's where I don't understand you're answer.
In the other instance the group,host, and passwd files are in /etc/AU ( my gold standard component ) .
I reopen the Component Template and change ETC_PATH to /etc/AU
to discover the next instance of the component - Screen 4
But after I run discover again, I still just see my first instance.
Should I see two instances of the component with the first listing files in /etc/
and the second listing files in /etc/AU ? - Screen 5
when you reference the local property, remove the TARGET - you should have ??ETC_PATH?? as the part, not ??TARGET.ETC_PATH??.
and... you need to click on that 'instances' tab in the local property and create 2 instances, call one "etc" and the other "etc_au" and set the value of the ETC_PATH property appropriately for the name of the instance.
Change your parts. Your discovery criteria is not TARGET.ANYTHING your discovery part is just ??ETC_PATH??/passwd (and likewise for the others.
You would have two instances in your component template. One with ETC_PATH =/etc and another with it = to /etc/au. Then do your discovery
Award the points to me. Bill has too many anyways.
Another similar question about this. Lets say I defined a local property SOME_PATH .
SOME_PATH is set to equal either:
I know that when I do a discover, a target's components will be created depending on what paths
are found on the different targets.
But what if one of the directories of SOME_PATH had a variable name
that I didn't always know.
For example, say dir2 above had a variable name. Would
the following be legal in SOME_PATH's instance definition ?
SOME_PATH is set to equal either:
That won't work unfortunately. How variable is that path likely to be?