Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Get src-dn from Query

136 views
Skip to first unread message

martin....@gmx.de

unread,
Aug 31, 2004, 12:35:25 PM8/31/04
to
Hello,

My Problem is that I can't write the src-dn of an result of a query in a
local variable. I want to solve this Problem with a Policy configuring
some rules. How can I get the value of the src-dn which is delievered by
the instance in the reult of the query. I don't want to use an XSLT-
Stylesheet. Thanks for your Help

Father Ramon

unread,
Aug 31, 2004, 1:17:47 PM8/31/04
to
How are you doing the query? What have you tried to get the src-dn?
--

Father Ramon
The Patron(izing) Saint of DirXML

martin....@gmx.de

unread,
Sep 1, 2004, 2:38:48 AM9/1/04
to
I am connecting a Active Directory with eDirectory 8.7.3. If I get a
Delete Event on the Publisher I don't wanted the User Object to be deleted
in eDirectory. I only want to remove the association and modify some
attributes. From the Remote Loader I get a Delete Event with the
Association. Now I want to get the src-dn of the Object with this
Association by a query because I need the dn of the Object. In our
eDirectory there is a Object "ADS" where all User are referenced who have
an Association with the active Directory. I want to remove the User Object
from the Object ADS if a Delete Event occurs. I tried it with the
Expression "Destination Attribute("Surname",class name="User",association
(Association()))". I read the Surname only because the field is in the
Definition of the query required. If I check the Trace I see that the
Query works fine. In the result there is the correct Object mentioned. But
I have no idea how to get the src-dn of the result of the query. I do this
action in the Input Transformation. A possible solution could be to try it
in the Match Policy. But I don't know if it works. So, it would be fine if
you could tell me how to get the src-dn of the result of the query. Thanks
for helping

Father Ramon

unread,
Sep 1, 2004, 11:25:57 AM9/1/04
to
The input transformation is absolutely the wrong place to do this - I
would recommend moving the logic to the publisher command transformation.

The easiest way I know of to get the DN based on the Association is to
use the XPATH token and call the query processor directly. You will need
to make sure the query namespace is defined and then use the following
XPATH expression:

query:readObject($destQueryProcessor, string(association), "",
@class-name, "")/@src-dn

Rob Schneider

unread,
Sep 1, 2004, 2:21:39 PM9/1/04
to
I've seen statements like the following peppered throughout this forum: (by
many people other than Father Ramon)

"Father Ramon" <devf...@novell.com> wrote in message
news:9SlZc.4129$ML2...@prv-forum2.provo.novell.com...


> The input transformation is absolutely the wrong place to do this - I
> would recommend moving the logic to the publisher command transformation

Question: Is there documentation that explains what each policy should or
should not do? Where logic should be placed and why? Best practices for
where to implement specific queries? Why would I do something in the
Output command Transformations of a subscriber rather than on the Input
command transformations of a publisher?

Thanks,

Rob.


Father Ramon

unread,
Sep 1, 2004, 3:17:09 PM9/1/04
to
I don't why I didn't think of this before, but when you wait until the
command transformation you won't even need to query for the dn because
DirXML will have figured it out for you - just use the Destination DN token.
--

Father Ramon
The Patron(izing) Saint of DirXML

Father Ramon

unread,
Sep 1, 2004, 3:21:09 PM9/1/04
to
Best source I know of is:

https://secure-www.novell.com/brainshare/portal/published/TUT266/TUT266.ppt

I don't know why the fairly simple information about what each policy is
supposed to do hasn't made it into the documentation.

--

Father Ramon
The Patron(izing) Saint of DirXML

martin....@gmx.de

unread,
Sep 2, 2004, 5:10:08 AM9/2/04
to
OK. Thanks for helping. The Problem is solved
0 new messages