Differences
This shows you the differences between two versions of the page.
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:18] svandav [Connector pool configuration] |
||
---|---|---|---|
Line 12: | Line 12: | ||
==== Connector pool configuration ==== | ==== Connector pool configuration ==== | ||
+ | {{tag> | ||
**The connector pool** is a very useful feature that avoids unnecessarily creating a new connector instance each time a connector is called. Typically, each connector instance also creates a connection to that target system. It is effective to maintain these connections for **longer periods and for multiple calls**. | **The connector pool** is a very useful feature that avoids unnecessarily creating a new connector instance each time a connector is called. Typically, each connector instance also creates a connection to that target system. It is effective to maintain these connections for **longer periods and for multiple calls**. | ||
Line 18: | Line 19: | ||
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> | ||
+ | |||
+ | <note tip>Pool configuration is persisted in EAV attributes and use form definition with code " | ||
Line 25: | Line 38: | ||
===== System scheme ===== | ===== System scheme ===== | ||
+ | {{tag> | ||
When the connector is configured correctly, we can move on to the **System scheme** tab. There, we will create the scheme either manually or we will use the scheme which will be returned by the connector itself (according to the filled-in configuration). | When the connector is configured correctly, we can move on to the **System scheme** tab. There, we will create the scheme either manually or we will use the scheme which will be returned by the connector itself (according to the filled-in configuration). | ||
Line 40: | Line 54: | ||
===== Attribute mapping ===== | ===== Attribute mapping ===== | ||
+ | {{tag> | ||
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 124: | ||
====== Mapped attribute strategy ====== | ====== Mapped attribute strategy ====== | ||
+ | {{tag> | ||
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 156: | ||
==== AUTHORITATIVE_MERGE (Authoritative merge) ==== | ==== AUTHORITATIVE_MERGE (Authoritative merge) ==== | ||
+ | {{tag> | ||
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 171: | ||
==== MERGE (Merge) ==== | ==== MERGE (Merge) ==== | ||
+ | {{tag> | ||
<note warning> | <note warning> | ||
Line 204: | Line 222: | ||
<note important> | <note important> | ||
+ | |||
+ | ==== Skip merged value if contract is excluded ==== | ||
+ | |||
+ | {{tag> | ||
+ | |||
+ | 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 **' | ||
+ | |||
+ | **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/ | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | {{ : | ||
==== Additional characteristics of strategies ==== | ==== Additional characteristics of strategies ==== |