Some connectors support the use of local cache. If you enable this cache, the connector loads all the necessary data into a local database after the connection has been established with the target system. The data is loaded for each schema type. The data required for are then supplied by the local database.
The aim is, to replace numerous small single read accesses to the target system by one large one. This can significantly increase the performance of where individual accesses need a lot of time but list access can be relatively quickly handled. This is generally the case for cloud-based target systems. Apart from that, the cache reduces the number of queries to the target system. The cache should, therefore, be used for target systems where the number of queries is limited through .
It does not always make sense to use the cache. When synchronizing with revision filtering, which is run at short intervals, you can expect few accesses to the target system. Filling the cache in this case, might cost more time than the sum of all system accesses without caching.
TIP: Use the cache for initial and the next synchronization after that as well as synchronization without revision filtering.
Cache is only used for synchronization.
The cache database is added in the user's 'temp' directory and deleted after the system is disconnected. contents with sensitive data (if known) are encrypted with the "Data Protection API" with the current user's key.
You specify whether the local is used in the target system connection settings. For more information, see the One Identity Manager administration guides for connecting to target systems that support local caching.
In addition to the schema overview, the provides a schema browser in expert mode. The details of the connected target system's entire schema and the details of the entire One Identity Manager schema are shown in the schema browser. types, schema properties, and the processing methods available are displayed in a hierarchical structure. The schema can be saved as XML for error analysis.
To save a schema
- Select the Configuration > One Identity Manager connection category.
- OR -
Select Configuration > category.
- Open the view.
This display the entire schema of the connected system in a hierarchical structure.
-
In the schema browser menu bar, click 
.
-
Enter a file name and repository.
-
Click Save.
A schema editor is integrated into the schema browser. It is only available in expert mode and allows you to edit virtual schema properties.
To open the schema editor
-
Select the Configuration > One Identity Manager connection category.
- OR -
Select the Configuration > category.
-
Open the view.
-
In the schema browser menu bar, click 
.
To add a custom schema property
-
Select the schema in the view to which you want to add a new virtual schema property.
-
Click Add schema property 
in the Action pane.
-
Select the schema property type and edit its details.
-
Click Create.
-
Click Commit to database to save the changes.
To edit a custom schema property
-
Select the schema property in the Schema view.
-
Edit the schema property details.
-
Click Apply changes.
-
Click Commit to database to save the changes.
To delete a custom schema property
-
Select the schema property in the Schema view.
-
Click Delete schema property 
in the Action bar.
- Confirm the security prompt with Yes.
-
Click Commit to database to save the changes.
Detailed information about this topic
You can make your own based on existing . This is particularly useful if you want to use mappings or in synchronization projects for other target systems. If you base a synchronization project on a custom project template, it includes all settings of the underlying synchronization project. To use the new project, you merely change the target system specific settings.
Script language and supported scripts
A script language and the script languages, which are supported, are specified for the project template. These properties have different functions and can therefore, have different values.
|
Script language |
Language that is used to write the project template's script.
Only change a project template's script language if the script needs to be modified manually and a specific script language should be used to do this. |
|
Supported script languages |
Script languages to be used for scripts in synchronization projects created with this project template.
-
If a project template supports more than one script language, select the script language to use when you set up the synchronization project (only in expert mode).
-
If you create a project template from an existing synchronization project, it only supports the script language of the underlying synchronization project. |
Related topics
