Hello Clément, Thanks for all theses responses.
Your interpretation of documentation is very interesting because i don't see anywhere that ldap was an object from destination ldap and srcLdap for source ldap. Here is the documentation : "Simple interface to some methods to access an LDAP directory. This class is available as "ldap" or "srcLdap" in several JavaScript enabled parameters in the LSC configuration. The methods allow you to interact with an LDAP directory." So thanks for that information ! Now for the search base it seems for me (with the tests i made), that base you can indicate, is a prefix/suffix of the baseDN defined in the source or the destination ldap. So with ScriptableJndiServices you can't made a search on a namingContext which is outside baseDN definition ? For the dataset, i will try it. For the bug, i've send it as Bug #541. Regards, Le 30/10/12, Clément OUDOT <[email protected]> a écrit : > 2012/10/30 "POISSON Frédéric" <[email protected]>: > > Thanks Clement, > > > > I have others questions about problems i encountered : > > > > - I used in the past the ScriptableJndiServices for group member > > synchronisation (with ldap2ldap lsc configuration), i read that it is > > available as "ldap" or "srcLdap" > > (http://lsc-project.org/javadoc/2.0-SNAPSHOT/). > > So is there a solution to be able to ask destination ldap server or i don't > > use the right documentation ? > > Destination LDAP is reachable trough "ldap", source LDAP is reachable > trough "srcLdap". > > > Is possible to specify a ldap base search with a different namingContext ? > > Or is there a method to run ldap query by initializing/using an > > com.sun.jndi.ldap.LdapCtxFactory object inside Javascript (i'm not Java > > developper probably my question is a non sense in Java/Javascript) or other > > object ? > > See list, read and search methods in > http://lsc-project.org/javadoc/2.0-SNAPSHOT/org/lsc/jndi/ScriptableJndiServices.html, > the first argument is the search base. > > > > - I have tested also the hsqldb to LDAP. And i have notice that all examples > > on sqlMap namespace are with InetOrgPerson objectClass. > > Is it possible to initialize sqlMap namespace with organizationalUnit for > > example or other ? > > Just modify the dataset for objectClass to set the values that you > need, there is no restriction. > > > > I have also read and tested hsqldb with a csv file with more than 10 000 > > lines, and i read that by default when initializing a table, hsqldb use a > > cache_scale of 10, which allow 3*(2^10) = 3072 lines. I have updated hsqldb > > script like this to optimize hsql performance, i hope it could help : > > > > # diff hsqldb hsqldb.ORIG > > 132,133c132,133 > > < scale=`echo $nblines | awk '{ print int(log($0/3)/log(2))+1 }'` > > < cp $1 $HSQLDB_DIR/`basename $1` > > --- > >> let nblines-- > >> tail -n $nblines $1 > $HSQLDB_DIR/`basename $1` > > 136d135 > > < source="`basename $1`;ignore_first=true;cache_scale=$scale;fs=$sep" > > 138c137,139 > > < source=$source";encoding=UTF-8" > > --- > >> hsqldb_sqlQuery "SET TABLE $HSQLDB_TABLE SOURCE \"`basename > >> $1`;fs=$sep;encoding=UTF-8\";" > /dev/null 2>&1 > >> else > >> hsqldb_sqlQuery "SET TABLE $HSQLDB_TABLE SOURCE \"`basename > >> $1`;fs=$sep\";" > /dev/null 2>&1 > > 140d140 > > < hsqldb_sqlQuery "SET TABLE $HSQLDB_TABLE SOURCE \"$source\";" > > > /dev/null 2>&1 > > > Thanks for this patch, could you open an issue on > http://tools.lsc-project.org/projects/lsc so that we can apply your > fix? > > Clément. > > -- FredericPoisson
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
