Chat now with support
Chat with Support

Identity Manager 9.1 - Target System Synchronization Reference Guide

Target system synchronization with the Synchronization Editor Working with the Synchronization Editor Basics of target system synchronization Setting up synchronization
Starting the Synchronization Editor Creating a synchronization project Configuring synchronization
Setting up mappings Setting up synchronization workflows Connecting systems Editing the scope Using variables and variable sets Setting up start up configurations Setting up base objects
Overview of schema classes Customizing the synchronization configuration Checking the consistency of the synchronization configuration Activating the synchronization project Defining start up sequences
Running synchronization Synchronization analysis Setting up synchronization with default connectors Updating existing synchronization projects Script library for synchronization projects Additional information for experts Troubleshooting errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples

Pausing handling of target system specific processes

Sometimes a target system is not available. For example, during maintenanceClosed. If synchronizationsClosed are started or data is changed in One Identity Manager during this time, synchronization and provisioning tasks are queued in the Job queueClosed. As long as the target system is down, these processes are sent into a FROZEN state and must be verified and re-enabled once the target system is available again.

One Identity Manager allows you to temporarily label the target system connection as offline. During this offline phase, synchronization is not run and provisioning tasks are put on hold. The respective synchronization serverClosed pauses Job queue processing. Once the target system is available again, the system connection must be switched to online. This starts Job queue processing again and all pending processes are run in sequence.

IMPORTANT: To prevent data inconsistencies, the offline phase should be kept as short as possible.

The number of processes to handle depends on the extent of the changes in the One Identity Manager database and their effect on the target system during the offline phase. To establish data consistency between the One Identity Manager database and the target system, all pending processes must be handled before synchronization can start.

Only use offline mode, if possible, for short system downtimes such as maintenance windows.

Detailed information about this topic

Enable offline mode

If a target system connector is not able to reach the target system temporarily, you can enable offline mode for the target system. This stops target system specific processesClosed from being frozen and having to be manually re-enabled later.

Whether offline mode is generally available for a target system connection is set in the base object of the respective synchronization projectClosed. Once a target system is truly unavailable, the target system connection can be switched offline and online again with the Launchpad.

In offline mode, all Job servers assigned to the base object are stopped. This includes the synchronization serverClosed and all Job servers involved in load balancing. If one of the Job servers also handles other tasks, these are not processed either.

Prerequisites

Offline mode can only be specified for a base object if certain prerequisites are fulfilled.

  • The synchronization server is not used for any other base object as a synchronization server.

  • If a server function is assigned to the base object, none of the Job servers with this server function may have any other server function (for example, update server).

  • A dedicated synchronization server must be set up to exclusively process the Job queueClosed for this base object. The same applies to all Job servers that are determined by the server function.

To allow offline mode for a base object

  1. In the Synchronization EditorClosed, open the synchronization project.

  2. Select the Base objects category.

  3. Select a base object in the document view and click .

  4. Enable Offline mode available.

  5. Click OK.
  6. Save the changes.

To flag a target system as offline

  1. Start the Launchpad and log in on the One Identity Manager database.

  2. Select Manage > System monitoring > Flag target systems as offline.

  3. Click Run.

    This opens the Manage offline systems dialog. The Base objects section displays the base objects of target system connections that can be switched to offline.

  4. Select the base object whose target system connection is not available.

  5. Click Switch offline.

  6. Confirm the security prompt with OK.

    This stops all the Job servers assigned to the base object. No more synchronization or provisioning Jobs are performed. The Job Queue InfoClosed program shows when a Job server has been switched offline and the corresponding tasks are not being processed.

Related topics

Enabling offline mode

Once the target system is available again, switch it back to online.

If offline mode should not be used for a target system in general, disable the option on the base object.

To flag a target system as online

  1. Start the Launchpad and log in on the One Identity Manager database.

  2. Select Manage > System monitoring > Flag target systems as offline.

  3. Click Run.

    This opens the Manage offline systems dialog. The Base objects section displays the base objects of target system connections that can be switched to offline.

  4. Select the base object whose target system connection is available again.

  5. Click Switch online.

  6. Confirm the security prompt with OK.

    The Job servers assigned to the base object then resume their work. SynchronizationClosed and provisioning tasks that were not processed during the offline phase are now carried out. Depending on the extent of the changes made during the offline phase, this make take some time.

To prohibit offline mode for a base object

  1. In the Synchronization EditorClosed, open the synchronization projectClosed.

  2. Select the Base objects category.

  3. Select a base object in the document view and click .

  4. Disable Offline mode available.

  5. Click OK.
  6. Save the changes.
Related topics

Maintaining synchronization information in column definitions

All columns in the One Identity Manager schema can store additional information, which is evaluated when synchronizationClosed is set up. This information is mainly required for setting up synchronization with the One Identity Manager connector, but can also be used when synchronizing customClosed tables and columns.

Settings in the synchronization information do not override the default behavior of the One Identity Manager connector. They provide information if the default behavior cannot be determined automatically. For example, if a column is marked as a mandatory column by the MinLen='1' property, the connector will automatically recognize it as a mandatory column even if the Mandatory column value is disabled in the Synchronization information field.

To edit synchronization information in column definitions

  1. In the DesignerClosed, select One Identity Manager SchemaClosed.

  2. Select the table and start the Schema Editor with the Show table definition task.

  3. Select the column and then the Column properties view.

  4. Select the More tab.

  5. Select all applicable values from the Synchronization information menu.

    • Not relevant for synchronization: The column is not displayed in the Synchronization EditorClosed.

    • Has unique value: The column contains a unique value.

    • Has conditional default value: The column contains a value that is formatted automatically under certain conditions, for example by a customizer.

    • Has a default value: The column contains a value that is formatted automatically, for example by a formation rule.

    • Conditional mandatory column: The column is a mandatory column under certain conditions, for example if the value is checked by triggers.

    • Mandatory column: The column is a mandatory column.

  6. Select the Database > Commit to database menu item and click Save.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating