Radovan - I have not yet tried your LDAP tool. Is there any conflict with the std data extract used by SD? In other words, if I try this and choose not to use it does the std SD data extract still function?
No, no... My application is not a replacement - it is another way to do things. It doesn't replace anything - it is completely standalone - it's just that the outpu it produces is in the same format Data Exchange would produce. So you do not have to worry - if anything went wrong you just switch back to usual Data Exchange.
Please test it - I'm sure you'll enjoy it :-) If you have any questions - do not hesitate to ask here or contact me directly.
Here's attached newer version (0.98) that adds support for specifying timestamp formats - both for those coming from LDAP (some people were having different format - there's example in readme that should work for those) and for outputing to XML )so that SD recognizes it). Also some bug related to unrecognized timestamp formats was fixed (unrecognized format caused java.lang.NullPointerException and the program halted). Please test and enjoy!
I have discovered lately ANT (http://ant.apache.org) and I'm planning to create ANT implementation for sd_export and sd_import (one of I would like to add is to make a ANT task to make a certain value in XML sd searchcode compatible (uppercase, removes spaces and other characters). Another wish is to create a better import reporting logfile to show me only the errors and warnings in one logfile (in stead of two logfiles, scanning manually this logfile).
Are you planning to make your LDAP extractor ANT compatible?
Jasper, AFAIK the Ant is an alternative to make command (so it allows you to define tasks, their dependencies, ...). I cannot clearly imagine what use could that be (at least not with Ant only). Could you please describe the scenario further, maybe provide some examples of propsed use? If I find it usable I can do some changes to make it 'Ant compatible'.
I have used your tool yesterday for the first time. After having troubles with date (I didn't use latest version...) I was able to create a simple setup for customer within a few edited lines!
As told before I have discovered lately ANT. To me ant build scripts are easier to understand than creating batch scripts. In theory ANT scripts aren't OS specific as well. Creating log info and send this info to persons is easier as well.
It isn't a must to have ANT-integration with your LDAP tool (I can launch Jar file from ant as well), but it will make my idea of creating ANT support for data exchange stronger ;-)
Jasper - I'll check out Ant once more. In the meantime could you send me (to e-mail would be OK) how you imagine the integration of log file should look like? What would be needed? I'm willing to improve my tool - version 1.0 could be the one with Ant integration...
from what I see in the config file it is exactly the same file that I include with proggie as example. Two things:
1. Check out (send me a screenshot) what some LDAP browser returns at given searchBase. Are there any records with "objectclass=organizationalUnit"? 2. For person records (beware - these are looked for inside found Organizations!) you left an example filter there that only allows Persosns with names Petra or Lucia!
Looking at you .ini file you probably only want to extract Persons and not Organizations. In that case your .xml configuration is wrong because it first recursively searches for Organizations and inside them (below in LDAP tree) searches for Persons. To fix it you need to remove top-most with its so that directly below you'll have .
Shaun, what you want to achieve is exactly what is my tool intended for. Just seems you cannot get it work right. I changed your .xml config according to your .ini file (not all but what is most important). Get it attached here. Hope it helps.
The concatenation of strings should work as you indicated.
Regarding checking for some value: this should be specified in searchFilter. However I don't know imediately how to specify search for non-empty values. Try looking into the LDAP RFCs indicated in the readme for the tool.
Hi Shaun, some examples for conditions: CONDITION=(!(SN=*) -- all without NULL CONDITION=(&(SN=*) (objectclass=user)) --SN not null and only users CONDITION=(&(SN=*) (mail=*)) -- all where neither SN nor mail is null CONDITION=(SN=) --all with SN is null
Shaun, you should read the docs more carefully :-) There's no such thing as CONDITION in DIRECT. What was pointed out by Wilfried is to use it in ENTRY_CLASS's searchFilter. So your desired configuration should look like this probably: