You can import scripts can be imported into other and them there. Sometimes you can use scripts for the same synchronization projects without having to change them. Scripts like this are maintained centrally and changes are transferred to the other synchronization projects as required. Mark scripts to use in across projects as script .
To mark a script as a script template
- Open the script library.
- Select the script in the Script view.
- Click Edit.
-
Edit the script’s general main data.
- Enable the Is template option.
- Click OK.
To import a script template into another synchronization project
- Open the synchronization project you want import the script template into.
- Open the script library.
- In the Scripts view, click Import.
-
Select the script template you want to import.
This saves a copy of the script.
You can see if the script template was changed in the script. You can decided if changes to these copies are accepted.
To view the script template changes
- Open the script library.
- Select the imported script in the Scripts view.
- In the Updates > Differences column, click Show.
To apply script template changes to the copy
- Open the script library.
- Select the imported script in the Scripts view.
- In the Updates > Apply column, click Apply.
To apply the all script templates changes
- Open the script library.
- In the Scripts view, click
.
- Confirm the security prompt with OK.
Related topics
NOTE: The following functions should only be carried out by experienced users and system administrators.
The properties and processes described here are only available in expert mode.
IMPORTANT: Changes to properties described here may affect system performance.
Check the effects on system performance of you environment before you change properties in expert mode.
To enable export mode
- Select the Database > Settings... menu item.
- EnableEnable expert mode.
- Click OK.
Topics:
Enter the following additional property for a when you are in expert mode.
Table 78: Properties of a mapping
| |
Property mapping rules can be inherited from a existing mapping. Select a mapping from the menu for this. Inherited property mapping rules can only be editing in the base mapping. Other property mapping rules can be added.
This is only visible in expert mode. |
Related topics
In expert mode, the tab Advanced is displayed in the start up configuration dialog.
Table 79: Extended properties for start up configuration
| Failure handling mode |
Specifies how failed objects are handled during .
- Repeat (default)
Synchronization is repeated until the failed objects do not yield any changes.
Advantage: This results in a full synchronization. Certain, highly complex hierarchical structures cannot only be synchronized in this mode.
Disadvantage: Synchronization in this mode takes considerably longer if a failed object arises.
- Ignore
The synchronization ignores failed objects.
Advantage: Synchronization does not take longer because of failed objects that cannot be corrected by repeating (data error).
Disadvantage: Errors, which can occur through complex data dependencies, are no longer corrected. The synchronization results may therefore not be complete.
NOTE: Repetitions of failed objects means a reduced synchronization.
It makes sense to ignore failed objects if synchronization with this start up configuration is run frequently because the failed objects are processed again by the next synchronization. This also achieves full synchronization results and at the same time reduces the runtime of each synchronization. |
|
Reload threshold |
Specifies the maximum number of properties that can be loaded by synchronization to prevent partitioned reloading. You can increase this value to accelerate synchronization of target systems with small mappings. However, more memory is required.
The reload threshold can be specified separately for each . |
| Partition size |
Specifies the number of objects and object pairs the can be processed at the same time. To prevent frequent reloading and to speed up synchronization, you can increase the size of the partition. However, more memory is required. |
| Bulk level |
Controls internal bulk processing of data For example, this is used to calculate how much object data is buffered in main memory. Depending on the operations to be run, a multiple of the value maybe applied.
Higher values speed up processing but require more memory. Smaller value reduce memory usage. This value should only be reduced if synchronizing causes memory problems. |
| Debug mode |
Sets debug mode. are handled sequentially in debug mode. This makes it much easier to find errors. Only set this option for finding errors! |
TIP: If memory problems occur, you should examine the reload threshold, partition size, and bulk level together and adjust them.
The reload threshold, partition size, and the bulk level also depend on how the performance/memory factor is configured in the synchronization steps. The performance/memory factor specifies the percentage with which the reload threshold, partition size, and bulk level are applied to an object type.
Detailed information about this topic
Related topics
