Hi Clement, Thanks for this complete feedback. Feel free to update the corresponding resources to make it logic :)
Regarding the JRE detection, using the default java executable is depending upon the path, which could be broken if launched by cron process, that's why the user is encouraged to setup the JAVA_HOME env variable prior to launch the LSC. To avoid the warning, the sample should include a getCleanFilter value. Regarding the ldif/csv issues, I need to check later. Regards -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ Le 2 avril 2012 13:42, Clément OUDOT <[email protected]> a écrit : > Hi all, > > at least I found some time to test the 2.0 release. Here is a small > feedback on the mistakes I found when following the quickstart : > http://lsc-project.org/wiki/documentation/2.0/sample > > > First, as prerequisite, is is written that JAVA_HOME environment > variable need to be set. In my case, my java is installed with my > distribution, and so there is no need to set such variable. I use > Kubuntu 11.10 with sun-java6 packages : > > clement@ader:~$ java -version > java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) > > > Then : > > * The LSC bin archive is a ZIP archive, not tar.gz as written in the > quickstart > > * The sample directory has subdirectories. To use the quickstart, we > need to go in the subdirectory hsqldb > > Other commands work fine, but I noticed some oddities : > > * We have a WARN in the log : > avr. 02 13:21:57 - WARN - No clean request has been specified for > task=MySyncTask. During the clean phase, LSC wouldn't be able to get > the right entries and may delete all destination entries ! > This warning is clear but might let be thinking the sample do not run > correctly > > * When reading logs, I found that the LDIF entries may not be just > printed below the line "avr. 02 11:51:14 - INFO - # Adding new object > ...", some entries are printed directly after others, without the INFO > line (which appears upper in the log). It is maybe a bug in the > logging code? > > * To test the connector, I updated a phone number, and the noticed > that it was not synchronized. In fact, attributes o, address and > telephoneNumber are in the sample.csv but are not configured to be > written int the LDAP directory, is it a choice or just a missing > configuration part? > > * Other test I wanted to do is put sn in uppercase as written in the > quickstart, but the quickstart refers to the old configuration file > (lsc.properties). Here is the configuration to use for lsc.xml: > > <dataset> > <name>sn</name> > <forceValues> > > <string>js:srcBean.getDatasetFirstValueById("sn").toUpperCase()</string> > </forceValues> > </dataset> > > > That's all for the moment. I would be happy to update the wiki with > these remarks if you are OK with them. > > Clément. > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-dev mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-dev >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
