Updating existing synchronization projects
Any required changes to system connectors or the engine are made available when you update One Identity Manager. These changes must be applied to existing to prevent that are already set up, from failing. There are two way to do this:
- Apply the required patches to the existing synchronization projects.
Patches for new functions and resolved issues in One Identity Manager are installed by hotfix packages and migration packages. You must apply these patches manually for the changes to take effect in existing synchronization projects. The default configuration of these synchronization projects is update in the process. modifications are not effected by the patches.
This method is recommended if the synchronization projects conform to the default configuration and contain no, or only very little, customization.
Checks are made during daily to find out if there are patches available for the existing synchronization projects. This information is displayed on the 's start page. If there are patches, the 
icon and the number of patches are displayed next to the synchronization project's name. This display is updated each time a synchronization project is saved.
- Delete existing synchronization projects and create them again.
This method is recommended if your synchronization projects contain extensive customizations that might conflict with the modifications in the patches.
Detailed information about this topic
For more information about setting up synchronization projects, see the administration guides for connecting target systems.
Patch view, patch types and dependencies
One Identity Manager has three patch types. All patches that are applied are displayed in the 's migration details. Once a milestone has been applied, the associated patches are not listed separately in the migration details anymore.
Table 73: Patch types
| Optional features |
Patch for optional functionality |
| Fix |
Patch for solved problems. |
| Mile stone |
Milestones are provided with every new One Identity Manager version. A milestone is provided for each context, which includes all the solved issues of the previous version. It does not contain the optional features of the previous version. |
Patches can be dependent on each other. These dependencies determine the order in which the patches are applied. When a patch is applied, the patches that are dependent on it are also applied. If a new version of One Identity Manager is installed, all patches for the version are consolidated into one milestone. If patches are available for different version of the program, the older patches must always be applied first. Therefore, One Identity Manager automatically applies all previous milestone once a patch for a later version is selected.
Patches and their dependencies are displayed in the patch view. The left side shows the patches that are available. The newest patches are at the top. Dependent patches are displayed below. In this area, select the patches that you want to apply to the current synchronization project. Then the patches are displayed on the right-hand side, with all their predecessor in the order in which they will be applied.
Each patch contains a script which checks if the patch can be applied to the synchronization project. Whether or not a patch can be applied depends on the concrete synchronization configuration.
Table 74: Meaning of icons in the rule tool bar
|
 Fixes
|
Shows patches with fixes. |
|
 Optional features
|
Shows all patches for optional features. |
|
|
Shows all patches that are cannot be applied to the synchronization project. |
|
|
Shows all patches that are already applied to the synchronization project. |
Related topics
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.
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 Identity 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. 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
