There are two prerequisite steps for configuring synchronization topologies:

  1. mount the objects you want to synchronize in the RadiantOne directory namespace
  2. extend the RadiantOne LDAP schema with any new/custom object definitions.

These steps are described below. After these steps are finished, you can create topologies.

Mount virtual views of objects

All synchronization source and target endpoints must be represented in the RadiantOne namespace, meaning that virtual views containing all source and target objects should be mounted below a root naming context. The virtual views can be created using the Control Panel > Setup > Directory Namespace > Namespace Design.

Extend RadiantOne LDAP schema

After virtual views have been mounted into the RadiantOne directory namespace, extend the LDAP schema with all needed object definitions that are not currently included. The object definitions are used in attribute mappings for synchronization. The RadiantOne LDAP schema can be extended from Control Panel > Setup > Directory Namespace > Directory Schema > Extend from ORX tab. Select the schemas associated the objects in your identity views and click + to move the schema into the column on the right. Then click GENERATE. You can verify the objects defined in the RadiantOne LDAP schema from the Control Panel > Setup > Directory Namespace > Directory Schema > LDAP Schema tab.

Create topologies

After all synchronization source and target objects are represented in the RadiantOne directory namespace and the LDAP Schema contains all object definitions, synchronization topologies can be configured from the Classic Control Panel > Synchronization tab. Pipelines are automatically created when topologies are configured.

To load the Classic Control Panel, click the logged in account profile in the upper-right and click Switch to Classic Control Panel.

  1. Navigate to the Synchronization tab.
  2. Select New Topology.
  3. Select Browse for the Source Naming Context and select the location in the RadiantOne namespace that contains the source objects you want to detect change events on.
  4. Select Browse for the Destination Naming Context and select the location in the RadiantOne namespace that contains the destination objects that you want to synchronize change events to. In the example shown below, the source objects are located in o=companydirectory (representing an LDAP directory backend) and the target is object=EMPLOYEES,o=hrdatabase (representing a table named EMPLOYEES in an HR database). Example Topology Definition
  5. Select OK. The topology is added to the list on the left and the pipelines associated with the selected topology are shown on the right where the components can be configured.

This section focuses on configuring the connector type. For details on the behavior of and properties for database connectors (Timestamp, Counter, Changelog), LDAP connectors (changelog or persistent search), and Active Directory connectors (usnChanged or DirSync), please see The Connector Properties Guide.

  1. A pipeline represents a synchronization flow from a given source object and a target object endpoint. Each pipeline in the selected topology must be configured.
  2. Select CONFIGURE next to the pipeline. There are two components that need configured per pipeline: Capture Connector and Transformation. Apply Connectors do not require configuration.


  • Prerequisites
  • Mount virtual views of objects
  • Extend RadiantOne LDAP schema
  • Create topologies