| I don't think the "target entity" is supported on the create rule directive,
and it's probably a mistake that it's showing up in the attributes at all.
QAR'd as 2915 in MCC_INTERNAL. It should either be removed from the shown
attributes or supported in the create directive.
But, what you can do with t1.2.7 is use targetting to re-target a rule.
For example, if you wanted to re-target a rule that is defined on a node4
remote node, which will fire on the remote node child entity of your local
node4,to instead fire on the remote node itself, you could do the following:
assign target domain <domain_name> -
event source = domain <domain_name> rule <rule_name>, -
event name = "any osi event", -
managed object = "node4 #1 remote node #2", -
target entity = "node4 #2"
That's a pretty fancy example, using symbol substitution (the #2 thingys), but
it's the kind of thing folks use a lot to overcome entity model restrictions.
A simpler one, e.g. retargetting a rule that is on a node to instead fire
on a bridget would be:
assign target domain <domain_name> -
event source = domain <domain_name> rule <rule_name>, -
event name = "any osi event", -
target entity = "bridge foo"
You can also re-target the severity of events (not just domain rule events)
by using the target severity argument. See the online help for the
targetting stuff in the IMPM.
Map window Application->Notification Services, then
Notification window Targeting->Assign Target, then
Assign Target window Help->Overview
Also, MB2->Help while in any of the "assign target" fields will give you help
on that field.
|