Applying patches
|
|
CAUTION: Patches do not change in . This mean that conflicts may occur if patches are applied to synchronization projects, which have been customized. This may cause loss of data.
Before you apply a patch
- Read the patch description to decide whether it provides necessary improvements for the synchronization project.
- Check whether conflict with customizations could occur.
- Create a backup of the database so that you can restore the original state if necessary.
- Deactivate the synchronization project.
|
NOTE: If synchronization projects are updated, connection parameters from the default variable set are always used. Ensure that the variables in the default variable set contain the correct values.
NOTE: As long as the update is running, none of the changes can be saved in the synchronization project.
Some patches required user input during installation, for example, to confirm that you really want a particular change to be run.
To apply patches
-
Open the synchronization project in the .
-
In the menu bar, select the Edit > Update synchronization project... menu item.
-
Select the milestone to apply under Available patches.
In the patch details view, all dependent patches are listed in the order in which they will be applied.
-
Click Apply selected patches.
-
Enter any user input as prompted.
-
Optional: Select the patches to apply for new functions under Available patches. Multi-select is possible.
In the patch detail view, patches are listed in the order in which they will be applied.
-
Click Apply selected patches.
-
Enter any user input as prompted.
-
If necessary, use the patch log to check whether customization need to be reworked.
-
If required, rework customizations in the synchronization configuration.
-
Run a consistency check.
-
Simulate the synchronization.
-
Activate the synchronization project.
- Save the changes.
NOTE: A patch does not take effect until the changes associated with it are saved in the database. If consistency check or simulation errors occur that cannot be corrected, you can dismiss the patch changes by reloading the synchronization project without saving the changes.
Related topics
Automatic patches
Patches can be labeled as automatic patches. All existing are migrated after One Manager is updated, for example, with a service pack. This updates the One Identity Manager schema and applies automatic patches. A process is queued in the to do this. Synchronization and provisioning processes are deferred until migration is complete. You can adjust the deferral time using the Common | Jobservice | RedoDelayMinutes .
After the One Identity Manager update, you should check whether the process DPR_Migrate_Shell was run successfully. If a patch could not be applied, for example because the target system was not available, you can apply the patch manually later.
A is found to migrate existing synchronization projects. To do this, the is determined from base object that is assigned to the synchronization project’s default variable set. If a synchronization server cannot be found, the Job server carries out the migration using the server function. In order to run the migration process, the must be started on all Job servers found in this way.
Related topics
Script library for synchronization projects
You can apply scripts at various points in the ; for example, when defining the schema properties, in the object filter, or when you define data operations for system connections through the . For each synchronization project, you can build a separate script library. The scripts in these script libraries can be used everywhere where scripts are implemented in the synchronization configuration. You can create and maintain scripts centrally that are required for defining different synchronization configuration components.
You can import scripts into other synchronization projects. Scripts that are used in different synchronization projects are labeled as script . The script templates are only maintained in one synchronization project. You can transfer any modification to other synchronization projects as required.
NOTE: Scripts from the One Manager script library are not available in the ‘s script library. For more information about the One Identity Manager script library, see the One Identity Manager Configuration Guide.
To display a synchronization project’s script library
- In the Synchronization Editor, open the synchronization project.
- Select the Configuration > Script library category.
Detailed information about this topic
Views in the script library
The ‘s script library has two views. The Scripts view provides an overview of all general properties of the scripts. The scripts are edited in the Editor view.
Script views
This lists all the scripts in the script library with all their general properties. You can update scripts that were created from script .
Table 74: Icons in the script view
|
 Add
|
Create a new script. |
|
 Edit
|
Edit the selected script’s general properties. |
|
 Delete
|
Deletes the selected script. |
|
 Import 
|
Imports scripts from other . |
|
|
Updates scripts with changes from script templates. |
Table 75: General properties of scripts
|
Script |
Name of script. |
|
Description |
Text field for additional explanation. |
|
|
type that the script is used on. |
|
Is template |
Script can be used as a template for other synchronization projects. |
|
Uses template |
Script was imported from another script template. |
|
Updates available |
Script template used as basis for the script has changed. |
|
Updates differences |
Shows the changes to the script template. |
|
Updates apply |
Updates the script with the changes from the script template. |
Editor view
Show the code of the selected script. It can be edited and compiled. For more information, see Support for scripting.
Table 76: Icons in the editor view
|
|
Saves changes to the script. |
|
 Compile
|
Compiles all the scripts in the script library.
 Script was compiled without errors.
 Script contains syntax errors.
|
Detailed information about this topic
One Identity