Article
2029
Caching and the AD Publisher Channel
Problem
A Forum reader recently asked:
"Is there such a thing as a cache on the publisher channel of an AD driver? We have a large number of AD moves that have taken place that we want to ignore."
And here are responses from Father Ramon and David Gersic ...
Solution
Father Ramon
There is not a cache per se on the publisher channel. Changes on the publisher channel for the AD driver are kept track of by AD and requested by the driver via an LDAP extension.
There is a tracking cookie that is returned by AD that is used to keep track of the which changes have already been seen. You can clear this cookie by stopping the driver and removing the DirXML-DriverStorage attribute from the driver object. If you are using the Remote Loader, you will also need to remove a file that is usually kept in the c:\novell\RemoteLoader directory. Its name is state_*.xml - where * is a string that is derived from the DN of the driver object. Resetting the cookie will cause the driver to ignore any changes that happened before the next time you start the driver.
David Gersic
If the driver hasn't already processed them, you can just veto the events you don't want to handle.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 2029 reads
0