Latest Release
- Stable version 1.2.1 (15/07/10)
- Old stable version 1.1.2 (07/12/09)
- Nightly builds available to test
Events
- 9/07/2010 - RMLL (Bordeaux, France)
- 10-11/04/2010 - Loadays (Antwerp, Belgium)
- 6-7/02/2010 - FOSDEM (Brussels, Belgium)
- 20/09/2009 - LDAPCon 2009 (Portland, OR, USA)
- 10/07/2009 - RMLL (Nantes)
- 25/06/2009 - LinuxTag (Berlin)
Community
Get help, contribute or find professional services ...
Find out more!
Search
Download | Read more... | Get started!
General informationWho: Sebastien Bahloul When: first release 13/04/2008, never updated Summary: How updated attributes may be altered by synchronization options Technical detailsThere are different types of synchronization options, but they all share one main goal: altering attribute update strategy. A synchronization option is specified for a whole task. In fact, you may need to adapt the way attributes are synchronized according to your context. Sometimes you may want to force the data source values, sometimes you may want to keep the target directory values. You may also want to replace the value with the result of an operation based on other values. There are different synchronization option implementations:
SamplesA sample synchronization options definition cut from interldap.properties : lsc.syncoptions.sampleTask = org.interldap.lsc.beans.syncoptions.PropertiesBasedSyncOptions lsc.syncoptions.sampleTask.default.action = K lsc.syncoptions.sampleTask.sampleAttribute.action = K lsc.syncoptions.sampleTask.sampleAttribute.create_value = someSampleValue You can see in this sample that there is a policy definition for the 'sampleTask' task: properties base synchronizations options. The following options are read and used by this policy engine. In the following synchronization options definition, the default policy - force all - is used for the 'sampleTask2' task. lsc.syncoptions.sampleTask2 = org.interldap.lsc.beans.syncoptions.ForceSyncOptions |


