Jon, thanks again. No, no it is not dynamic at all. That's a good tip. I've been focused on the OU structure (though it has helped me a lot to get a good understanding of the product) and did not realize that approach.
*Tfn: 957-211157 / 650932877* 2015-02-11 15:12 GMT+01:00 Jon C Kidder <[email protected]>: > You should be able to do this with a one-time LDIF export and import > using (objectClass=organizationalUnit) as the export filter. Your tree > structure should be static. If the tree itself is so dynamic that you need > recurring synchronization for the structure then it’s likely a bad tree > design. LSC won’t do this. LSC is designed to synchronize data in a > single branch and not the tree itself. > > > > -Jon C. Kidder > > American Electric Power > > Middleware Services > > Email: [email protected] > > Phone: 614-716-4970 > > > > *From:* Juan Carlos Camargo [mailto:[email protected]] > *Sent:* Wednesday, February 11, 2015 1:15 AM > *To:* Jon C Kidder; lsc-userslsc-users > *Subject:* Re: [lsc-users] Dynamic filters > > > > This is an EXTERNAL email. STOP. THINK before you CLICK links or OPEN > attachments. > ------------------------------ > > Hi Jon, > > > > Thanks for the tip. I do use js in the mainidentifier to replace the > domain part, yes. But let's go back to the previous phase. > > > > I'm trying to replicate the entire OU structure. If I use either OU or CN > as pivots in my former example then OU=Networking,OU=Systems,dc=domainA > will be erratic, because it will unsuccessfuly try to find OU=Networking > in domainB and it hence create OU=Networking,dc=DomainB in the target ldap > service. That's not right. > > > > > > [image: Image removed by sender.] > > *Tfn: 957-211157 / 650932877* > > > > 2015-02-10 16:17 GMT+01:00 Jon C Kidder <[email protected]>: > > Don’t use entryDN as a pivot. Use an attribute that is unique to each > record but common to both copies of the record. In your case the RDN might > be a good choice. I’m assuming that’s either UID or CN. You can then do a > simple JavaScript substring replace on the entryDN attribute in the > <mainIdentifier> element of your LSC job to convert your source DN to a > destination DN. > > > > -Jon C. Kidder > > American Electric Power > > Middleware Services > > Email: [email protected] > > Phone: 614-716-4970 > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Juan Carlos > Camargo > *Sent:* Tuesday, February 10, 2015 6:41 AM > *To:* lsc-userslsc-users > *Subject:* [lsc-users] Dynamic filters > > > > This is an EXTERNAL email. STOP. THINK before you CLICK links or OPEN > attachments. > ------------------------------ > > Hi LSC'ers :) > > > > Is there a way to insert scripts in destination filters? The point is, if > I could build a <getOneFilter> in destination to match the source, then > things would be easier when handling different ldap domains. In my case > I'm trying to sync the whole OU (just organizational units) tree from > server A to B: > > - Server A is dc=domainA,dc=org > - Server B is dc=domainB,dc=org > > Pivot is entryDN and it will never be the same , so entries are always > treated as new, no matter if they already exist in B. However, if I could > use a script then it'd be as easy as replacing the domain in B, kind of > <getOneFilter>js:<buildDN>.replace("domainA","domainB") </getoneFilter> or > similar. > > > > [image: Image removed by sender.] > > *Tfn: 957-211157 / 650932877* > > >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
