Highlighted
Absent Member.
Absent Member.
190 views

getting into command transform through merge


hi there,

i´m fiddling around with a problem with a user coming in on publisher
(ad > edir). a match is found and attributes are merged. i then want
policies in command transform to do things if the event was a merge.

Code:
--------------------
<if-xpath op="true">.[@from-merge='true']</if-xpath>
--------------------


this does work, when that users attributes do have different values in
AD and eDir (
Code:
--------------------
publisher="sync"
--------------------
) if they are the same (same values) the event is not further processed.


read geoff´s 2 articles about the filter, and thought, changing to
Code:
--------------------
publisher-optimize-modify="false"
--------------------
on one of those would solve the problem, but it did not.

after that i tried to change the value of an op-attr i know is in every
operation (surname) in event transform and removing that in
command-transform to be sure values in edir and ad don´t match. but
that´s messy.

anyone can think of a more elegant solution/strategy to get those "no
attrs of interest get changed, but i want to force the thing into
cmd-transform - EVENTS"?


thanks in advance for your input, florian


--
florianz
------------------------------------------------------------------------
florianz's Profile: https://forums.netiq.com/member.php?userid=309
View this thread: https://forums.netiq.com/showthread.php?t=48411

Labels (1)
0 Likes
3 Replies
Highlighted
Absent Member.
Absent Member.

Re: getting into command transform through merge

On 16.08.2013 16:34, florianz wrote:
>
> hi there,
>
> i�m fiddling around with a problem with a user coming in on publisher
> (ad > edir). a match is found and attributes are merged. i then want
> policies in command transform to do things if the event was a merge.
>
> Code:
> --------------------
> <if-xpath op="true">.[@from-merge='true']
> --------------------


Your xpath seems a bit over-complicated.

It should be enough with just

<conditions>
<and>
<if-operation op="equal">modify</if-operation>
<if-xpath op="true">@from-merge = 'true'</if-xpath>
</and>
</conditions>

Or on IDM 3.5+ - you don't even need to use xpath
<conditions>
<and>
<if-operation op="equal">modify</if-operation>
<if-xml-attr op="available" name="from-merge"/>
</and>
</conditions>

>
> this does work, when that users attributes do have different values in
> AD and eDir (
> Code:
> --------------------
> publisher="sync"
> --------------------
> ) if they are the same (same values) the event is not further processed.
>
>
> read geoff�s 2 articles about the filter, and thought, changing to
> Code:
> --------------------
> publisher-optimize-modify="false"
> --------------------
> on one of those would solve the problem, but it did not.
>


How is your merge authority set for each attribute?

Can you post a level 3 trace of this scenario?

> after that i tried to change the value of an op-attr i know is in every
> operation (surname) in event transform and removing that in
> command-transform to be sure values in edir and ad don�t match. but
> that�s messy.


I wouldn't try that. That approach has it's drawbacks.

> anyone can think of a more elegant solution/strategy to get those "no
> attrs of interest get changed, but i want to force the thing into
> cmd-transform - EVENTS"?


Until we see the trace, it's hard to say. I have at least one idea.


--
----------------------------------------------------------------------
Alex McHugh
NetIQ Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support is provided via email.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: getting into command transform through merge

On 8/16/13 8:34 AM, florianz wrote:
>
> hi there,
>
> i�m fiddling around with a problem with a user coming in on publisher
> (ad > edir). a match is found and attributes are merged. i then want
> policies in command transform to do things if the event was a merge.
>
> Code:
> --------------------
> <if-xpath op="true">.[@from-merge='true']</if-xpath>
> --------------------
>
>
> this does work, when that users attributes do have different values in
> AD and eDir (
> Code:
> --------------------
> publisher="sync"
> --------------------
> ) if they are the same (same values) the event is not further processed.
>
>
> read geoff�s 2 articles about the filter, and thought, changing to
> Code:
> --------------------
> publisher-optimize-modify="false"
> --------------------
> on one of those would solve the problem, but it did not.
>
> after that i tried to change the value of an op-attr i know is in every
> operation (surname) in event transform and removing that in
> command-transform to be sure values in edir and ad don�t match. but
> that�s messy.
>
> anyone can think of a more elegant solution/strategy to get those "no
> attrs of interest get changed, but i want to force the thing into
> cmd-transform - EVENTS"?
>
>
> thanks in advance for your input, florian
>
>


Add an attribute to the filter that you don't really care about and will
always be different in app and IDV. Set it to ignore on subscriber,
notify on the publisher, with app as the merge authority. IIRC that
should cause a merge to always generate some result that hits the
command transformation, but doesn't let the extra attribute proceed
beyond the command transformation.

--
Shon
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: getting into command transform through merge


does the trick, thanks a lot.

i did use vehicleinformation, which does not exist in Active Directory.
I wonder why i don´t even need a mapping to a "real" attribute, looks
like 'fallback-logic' is "if not found > remove all values". and then:
PT:Filtering out notification-only attributes.

florian


--
florianz
------------------------------------------------------------------------
florianz's Profile: https://forums.netiq.com/member.php?userid=309
View this thread: https://forums.netiq.com/showthread.php?t=48411

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.