Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
devel:documentation:systems:dev:system-mapping [2019/05/06 10:10]
svandav 		devel:documentation:systems:dev:system-mapping [2019/07/02 09:16]
svandav [Attribute mapping]
Line 18: Line 18:
  
 The last advantage is the ability to use **multiple connections** to one target system, which is especially advantageous during parallel processing. The last advantage is the ability to use **multiple connections** to one target system, which is especially advantageous during parallel processing.
 +
 +=== Pool configurations: ===
 +  * **Pooling supported** - Enable / disable entire pool
 +  * **Max idle objects**
 +  * **Minimum number of idle objects**
 +  * **Max objects** - Max number of objects in the pool.
 +  * **Max time to wait** - Max time to wait for free object in the pool.
 +  * **Minimum time to wait before evicting** - Minimum time to wait befor evicting idle object.
 +
 +<note important>By default is pool **disabled**!</note>
 +
 +<note tip>Pool configuration is persisted in EAV attributes and use form definition with code "pooling-connector-configuration".</note>
  
  
Line 40: Line 52:
  
 ===== Attribute mapping ===== ===== Attribute mapping =====
 +{{tag>attribute mapping}}
  
 When the system scheme is created, we can move on to attribute mapping in the **Attribute mapping** tab. Mapping serves two basic purposes: When the system scheme is created, we can move on to attribute mapping in the **Attribute mapping** tab. Mapping serves two basic purposes:
Line 109: Line 122:
  
 ====== Mapped attribute strategy ====== ====== Mapped attribute strategy ======
 +{{tag>attribute strategy}}
  
 The attribute strategy defines how will the attribute and primarily its value be dealt with during provisioning and synchronization. The attribute strategy defines how will the attribute and primarily its value be dealt with during provisioning and synchronization.
Line 140: Line 154:
  
 ==== AUTHORITATIVE_MERGE (Authoritative merge) ==== ==== AUTHORITATIVE_MERGE (Authoritative merge) ====
 +{{tag>authoritative merge}}
  
 This strategy (identically to MERGE) alters the logic of calculating attributes and their values. With the other strategies applies the following: if there are more occurrences of the same strategy for the same attribute (more overloaded attributes in more roles), the one with the highest priority is found (according to role priorities or their names). The resulting value going into provisioning is calculated on the basis of this one attribute only. This strategy (identically to MERGE) alters the logic of calculating attributes and their values. With the other strategies applies the following: if there are more occurrences of the same strategy for the same attribute (more overloaded attributes in more roles), the one with the highest priority is found (according to role priorities or their names). The resulting value going into provisioning is calculated on the basis of this one attribute only.
Line 154: Line 169:
  
 ==== MERGE (Merge) ==== ==== MERGE (Merge) ====
 +{{tag>merge}}
  
 <note warning>Since version **9.3.0** was provisioning merge completely reimplemented!</note> <note warning>Since version **9.3.0** was provisioning merge completely reimplemented!</note>
Line 204: Line 220:
  
 <note important>Final values merge from roles is set, **all duplicates will be removed**. For example: if you have two roles with merge mapping for same attribute and value for this attribute is same, to end system will be send only one.</note> <note important>Final values merge from roles is set, **all duplicates will be removed**. For example: if you have two roles with merge mapping for same attribute and value for this attribute is same, to end system will be send only one.</note>
 +
 +==== Skip merged value if contract is excluded ====
 +
 +{{tag>merge skip exclude contract}}
 +
 +Since version **9.7.0** was added new feature enabling skip of value defined in merge attribute, if contract (on witch is role assigned) will be excluded.
 +
 +For enable this feature you need to check the option **'Skip value when contract is excluded'**.
 +
 +**Value will be skipped only if**:
 +  - Attribute has strategy type sets to **MERGE** or **AUTHORITATIVE_MERGE** (only for this options will checkbox shows).
 +  - Feature is **enabled** on the role mapping.
 +  - Identity has assigned this role/s to the **excluded contract/s**. If identity has assigned more same roles on different contracts, then for skipping of the value must be **all** connected contracts excluded.
 +
 +<note important>**If all roles which defines the account will have skipped values, then account will not be deleted!**</note>
 +
 +{{ :devel:documentation:systems:dev:skip_m.png |}}
  
 ==== Additional characteristics of strategies ==== ==== Additional characteristics of strategies ====
  • by svandav