Start up configurations for cloud application synchronization
The project wizard adds two start up configurations that run cloud application synchronization.
-
Synchronization of the cloud application
Cloud application objects, such as user accounts, groups, group memberships, are synchronized. This is done by the Initial synchronization workflow. Synchronization is run on a daily basis by the default schedule.
-
Synchronization of pending changes
If cloud objects are changed in the Cloud Systems Management Module, these changes must first be transferred to the Universal Cloud Interface Module and can then be provisioned in the cloud application itself. To track whether the changes have been successfully provisioned in the cloud application, they are labeled with Pending changes. The details, time of creation, and processing status of every pending change are saved. Once provisioning is complete, the processing status must be transferred from the Universal Cloud Interface to the Cloud Systems Management Module. To do this, run the Synchronization of pending changes start up configuration. This is done by the State synchronization workflow. Synchronization is run on an hourly basis with the default schedule.
Related topics
Configuring the synchronization log
All the information, tips, warnings, and errors that occur during synchronization are recorded in the synchronization log. You can configure the type of information to record separately for each system connection.
To configure the content of the synchronization log
-
To configure the synchronization log for target system connection, select the Configuration > Target system category in the Synchronization Editor.
- OR -
To configure the synchronization log for the database connection, select the Configuration > One Identity Manager connection category in the Synchronization Editor.
-
Select the General view and click Configure.
-
Select the Synchronization log view and set Create synchronization log.
-
Enable the data to be logged.
NOTE: Some content generates a particularly large volume of log data. The synchronization log should only contain data required for error analysis and other analyzes.
- Click OK.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
Related topics
Customizing the synchronization configuration
Having used the Synchronization Editor to set up a synchronization project for initial synchronization with a Universal Cloud Interface, you can use the synchronization project to load cloud application objects into the Cloud Systems Management Module. If you manage user accounts and their authorizations with One Identity Manager, changes are provisioned in the Universal Cloud Interface environment.
You must customize the synchronization configuration in order to regularly compare the cloud application and to synchronize changes.
-
To use Cloud Systems Management Module as the primary system during synchronization, create a workflow with synchronization in the direction of the Target system.
-
You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.
-
Use variables to set up a synchronization project for synchronizing different cloud applications. Store the connection parameter as a variable for logging in to the databases.
-
To specify which target system objects and database objects are included in synchronization, edit the scope of the target system connection and the One Identity Manager database connection. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
-
Update the schema in the synchronization project if the One Identity Manager schema or target system schema has changed. Then you can add the changes to the mapping.
-
Add your own schema types if you want to synchronize data, which does not have schema types in the connector schema. Include the schema extensions in the mapping.
-
If the cloud application schema cannot be adequately represented by the default project template, customize the synchronization configuration. At the same time, define how the system entitlements are mapped in the One Identity Manager schema. When you are setting up synchronization, ensure that the base object for the cloud application(CSMRoot) is created in the database and the System entitlements types used (GroupUsageMask) and User account contains memberships (UserContainsGroupList) properties are set correctly.
For more information about configuring synchronization, see the One Identity Manager Target System Synchronization Reference Guide.
Detailed information about this topic
How to configure Universal Cloud Interface synchronization
The synchronization project for initial synchronization provides a workflow for initial loading of target system objects (initial synchronization) and one for provisioning object modifications from the One Identity Manager database to the target system (provisioning). To use One Identity Manager as the primary system during synchronization, you also require a workflow with synchronization in the direction of the Target system.
To create a synchronization configuration for synchronizing Universal Cloud Interface
-
In the Synchronization Editor, open the synchronization project.
-
Check whether the existing mappings can be used to synchronize into the target system. Create new maps if required.
-
Create a new workflow with the workflow wizard.
This creates a workflow with Target system as its direction of synchronization.
-
Create a new start up configuration. Use the new workflow to do this.
- Save the changes.
-
Run a consistency check.
Related topics