Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
documentation:latest:basics [2017/01/30 17:10]
127.0.0.1 external edit
documentation:latest:basics [2018/05/24 14:29] (current)
nqb add clarification regarding source and destination
Line 12: Line 12:
  
   - All entries are read in source. This is done with ''​getAllFilter''​ for LDAP, ''​requestNameForList''​ for Database or ''​listScript''​ for executable plugin. The values of attributes defined in ''​pivotAttributes''​ (in the source) are read.   - All entries are read in source. This is done with ''​getAllFilter''​ for LDAP, ''​requestNameForList''​ for Database or ''​listScript''​ for executable plugin. The values of attributes defined in ''​pivotAttributes''​ (in the source) are read.
-  - For each entry found at step 1, the pivot values are used to get the entry in source and values of attributes defined in ''​fetchedAttributes''​ are read. This is done with ''​getOneFilter''​ for LDAP, ''​requestNameForObject''​ for Database or ''​getScript''​ for executable plugin. +  - For each entry found at step 1, the pivot values are used to get the entry in source and values of attributes defined in ''​fetchedAttributes''​ are read (in the source). This is done with ''​getOneFilter''​ for LDAP, ''​requestNameForObject''​ for Database or ''​getScript''​ for executable plugin ​(in the source)
-  - For each entry found at step 1, the pivot values (from the source) are used to get the entry in destination and values of attributes defined in ''​fetchedAttributes''​ are read.  This is done with ''​getOneFilter''​ for LDAP, ''​requestNameForObject''​ for Database or ''​getScript''​ for executable plugin.+  - For each entry found at step 1, the pivot values (from the source) are used to get the entry in destination and values of attributes defined in ''​fetchedAttributes''​ are read (in the destination).  This is done with ''​getOneFilter''​ for LDAP, ''​requestNameForObject''​ for Database or ''​getScript''​ for executable plugin ​(in the destination).
   - Attributes and values found at step 2 are placed in ''​srcBean'',​ and those found at step 3 are in ''​dstBean''​. The synchronizations rules are run and LSC calculate modifications.   - Attributes and values found at step 2 are placed in ''​srcBean'',​ and those found at step 3 are in ''​dstBean''​. The synchronizations rules are run and LSC calculate modifications.
   - The modification are applied on the destination,​ if associated ''​conditions''​ are true.   - The modification are applied on the destination,​ if associated ''​conditions''​ are true.