Synchronization Introduction
RadiantOne Synchronization is an advanced set of tools for synchronization and identity management. This feature allows you to synchronize objects distributed across disparate data sources (directories, databases or applications): a change in an object in one source, at the attribute level, or for the whole object can be reflected into many other connected objects. Using a publisher/subscriber approach, any object can publish events (creation, deletion or modification for the whole object, or any attributes of this object) and propagate them to subscriber objects. User-defined attribute mappings and transformations can be applied during synchronization.
If you have a RadiantOne license that entitles you to use synchronization, you will see a Synchronization tab in the Main Control Panel. Otherwise the tab doesn't show.
Architecture
The Synchronization architecture is comprised of Agents, Queues, Sync Engine, Attribute mappings and transformation scripts.
Agents manage Connectors which are components used to interface with the data sources. Changes flow to and from the Connectors asynchronously in the form of messages. This process leverages queues to temporarily store messages as they flow through the synchronization pipeline. The attribute mappings and/or transformation scripts are processed by the Sync Engine prior to the events being sent to the target endpoints.
All sources must have views mounted in the RadiantOne namespace to complete the synchronization configuration. To simplify management of the synchronization flows, it is recommended to have a dedicated section of the namespace for all source identity views. Once a view has been configured as a source for synchronization, no further changes should be made to the view (e.g. no object/attribute mapping changes, no adding/removing persistent cache, etc.). The Main Control Panel > Directory Namespace tab displays a warning for all source views that are configured for synchronization to avoid accidental configuration changes.
See the figure below for a high-level architecture of the synchronization process.
How this manual is organized
This guide is broken down into the following chapters:
Concept and Definitions This chapter introduces the main concepts that are essential to understand for configuring and administering synchronization.
Configuration This chapter describes how to configure synchronization.
Uploads This chapter describes the upload process for scenarios where source entries must be populated into a destination before starting synchronization.
This chapter describes a typical deployment architecture and how high availability is achieved. Details about managing synchronization, including where to find synchronization logs, how to suspend synchronization pipelines, and monitor synchronization activities can also be found in this chapter.
Technical support
Refer to the Technical support guide for more information.
Expert mode
Some settings in the Main Control Panel are accessible only in Expert Mode. To switch to Expert Mode, select the Logged in as, (username) drop-down menu and select Expert Mode.
The Main Control Panel saves the last mode (Expert or Standard) it was in when you log out and returns to this mode automatically when you log back in. The mode is saved on a per-role basis.