Hi Maxime, I agree with Clement. Just to add that the only thing that lsc-sample is doing is to set the CLASSPATH environnement variable with the external libraries (JDBC drivers, ...) used by LSC but not distributed with the package.
My advice about configuration would be : if the security settings (and later audit settings when they will do the job) can be share between different tasks, put them in the same lsc.xml file even if it is a big file because it will avoid duplicating the connection details. Otherwise, use different etc directories (or sub-directories) and specify them with the -c flag. Regards, -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ Le 19 avril 2012 17:43, Clément OUDOT <[email protected]> a écrit : > Le 19 avril 2012 17:20, Maxime Pelletier <[email protected]> a > écrit : > > Hi guys, > > > > I've been using LSC for more than a year now and I'm more than satisfied > > with what we achieved with this tool. > > > > However, there is still something unclear to me regarding LSC. > > > > How are we suppose to setup all of our sync directories and tasks? Or in > > other word, is there any directory convention that we should follow? I > > haven't find anything about this in the wiki. > > > > What I've been doing up to now is to duplicate the "sample" directory and > > modify the files under "etc" sub-directory. Now that I start to migrate > to > > 2.0, and that I'm more confortable with LSC, I'd like to have a "clean" > > setup. > > > > I also have a script in crontab that calls all my tasks, one at a time. > This > > script is calling "bin/lsc-sample --run" for each task/directory. > > > > In short, I'd like to have some advice on all this:) > > Hi, > > I talk for myself, but you should not use any sample script in production. > > If you have several connectors, you have two choices: > * Configure all in one lsc.xml file (you can have as many connections > and tasks as you need) > * Create a conf directory for each connector > > Then, always run your connector with the official bin/lsc script, and > set the options that you need (-s, -a, -c, ...). You can set theses > commands in a cron job (see lsc.cron file example). > > > Clément. > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
