Hi, i'm currently working in a lab Environment with the bidirectional e-directory driver, i get it to work perfectly from vault to tree (subscriber), but not from tree to vault (Publisher).
I have the changelog up and running, in the startup trace i see that the driver is connected to it, but when i add a user, or try to synchronize from imanager, i never even see the data, just a pile of filtered out classes in the trace, like this (i have blocked the subscriber channel though):
Code: -------------------- 13:58:45 C4A91700 Drvrs: Tree ST:No event transformation policies. 13:58:45 C4A91700 Drvrs: Tree ST:End transaction. 13:58:45 C4A91700 Drvrs: Tree ST:Start transaction. 13:58:45 C4A91700 Drvrs: Tree ST:Processing events for transaction. 13:58:45 C4A91700 Drvrs: Tree ST: Filtered out <sync class-name='Organizational Unit'>. 13:58:45 C4A91700 Drvrs: Tree ST: <nds dtdversion="4.0" ndsversion="8.x"> <source> <product edition="Standard" version="126.96.36.199">DirXML</product> <contact>Novell, Inc.</contact> </source> <input/> </nds> --------------------
now, i know for a fact that the organizational unit IS enabled on Publisher channel:
but nothing in the tree gets even as far as the matching policy on the Publisher channel. Added traces to see every step, and i can trace from the input transformation policy, but wont really get any data. For example tracing class name, will be an empty string.
I tried doing the same thing with the ldap driver, and it works perfectly. The version of the driver and changelog is 4.0.11, idm is 4.0.2, PL6 applied.
First, please always post a trace; in your case, a trace of driver startup would be interesting, and any trace of events you can see. You mentioned "not even as far as Matching" but Matching is not the first policyset, so seeing what you do see could help us help you determine why the event fails.
Second, which user are you using to make changes in the remote directory? Which user is used to give rights to the driver connecting to that environment (startup trace would show this)?
I believe the bidirectional driver, by default, will not show events which are written to the remote directory by the user used to connect to that directory. If you are using 'admin' to connect from the vault to that directory, and then you use 'admin' to make changes in the directory hoping to see them come through, you will not a part of loopback prevention, or at least this is my memory. You should never be using 'admin' for a driver anyway (or, arguably, almost ever) since it has more rights than you need, but in this case its use in both places could cause your symptom.
-- Good luck.
If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...