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/07/02 09:15] svandav [AUTHORITATIVE_MERGE (Authoritative merge)] |
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 37: | 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 52: | 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 121: | 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. |