Using Local Cache
Using Local Cache
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 synchronization 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 target system synchronization 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 quotas.
It does not always make sense to use the cache. When synchronizing with revision filtering, which is executed 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. Schema type
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.
Schema Browser
Schema Browser
In addition to the schema overview, the Synchronization Editor
To save a schema
- Select the category Configuration | One Identity Manager connection.
- OR -
Select the category Configuration | Target system.
- Open the Schema browser view.
This display the entire schema of the connected system in a hierarchical structure.
- Click
in the schema browser menu bar.
- Enter a file name and repository.
- Click Save.
Creating Project Templates
Creating Project Templates
Project templates can be created in expert mode from existing synchronization projects. You can use these to create new synchronization projects with the project wizard.
|
|
NOTE: The script language of the underlying synchronization project is the only script language which is supported by the project template (DPRTemplate.SupportedScriptLanguages). When you create a synchronization project, the project wizard displays all the project templates for which the following applies:
|
To create a project template
- Select Edit | Create template....
- Enter the template properties.
The values are preset with the properties of the open synchronization project.
- Click OK.
| Property | Description |
|---|---|
| Display name | Name of the project template to display in the project wizard. |
| Script language | Script language in which the template is created. |
| Description | Spare text box for additional explanation. |
How can Custom Tables be Included in Synchronization
Custom schema extensions can be included in the synchronization configuration. Custom columns are automatically assigned to additional schema properties which can be included in the mapping. The following settings are required to include custom tables in synchronization.
To prepare a custom table for synchronization
- Assign a target system type to the custom table.
- Specify whether outstanding objects can be published in post-processing.
- Create a schema class in the One Identity Manager schema for the custom table.
Detailed information about this topic
For detailed information about target system types and post-processing outstanding object, see the target system connection guides.