Create a target system for post-processing outstanding objects. Assign tables you want to be populated by synchronization, to this target system type. Specify the tables for which outstanding objects can be published in the target system during post-processing. Define a process for publishing the objects.
To create a target system type
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
Click 
in the result list.
-
Edit the target system type main data.
- Save the changes.
Enter the following data for a target system type.
Table 16: main data for a target system type
|
Target system type |
Target system type description. |
|
Description |
Text field for additional explanation. |
|
Display name |
Name of the target system type as displayed in One Identity Manager tools. |
|
Cross-boundary inheritance |
Specifies how user accounts are assigned to or inherit groups and system entitlements if they belong to different custom target systems.
-
If the option is set, groups and system entitlements can be assigned to user accounts that belong to the same target system or to different target systems. The target systems must have the same target system type.
For all target systems of a target system type, the settings for the User account has memberships column(UNSRootB.UserContainsGroupList) must be identical.
-
If the option is not set, groups and system entitlements can only be assigned to the same target system.
NOTE: If the option is not set, the target system type is used to simplify grouping of the target systems. |
|
Show in compliance rule wizard |
Specifies whether the target system type for compliance rule wizard can be selected when rule conditions are being set up. |
|
Text snippet |
Text snippets used for linking text in the compliance rule wizard. |
|
Alternative connectors |
List of connector that can process this type of target system. |
To add tables to target system synchronization
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
In the result list, select the target system type.
-
Select the Assign synchronization tables task.
-
In the pane, assign custom tables to the outstanding objects you want to handle.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the tables that contain the outstanding objects that can be published in the target system and set the Publishable option.
- Save the changes.
NOTE: The connector must have write access to the target system in order to publish outstanding objects that are being post-processed. That means, the Connection is read-only option must not be set for the target system connection.
To publish outstanding objects
-
For each table for which you want to publish outstanding objects, create a process, which is triggered by the event HandleOutstanding and which runs the provisioning of the objects. Use the AdHocProjection process task of the ProjectorComponent process component.
For more information about defining processes, see the One Identity Manager Configuration Guide.
To post-process outstanding objects
-
In the Manager, select the Data synchronization > Target system synchronization: <target system type> category.
All tables assigned to the target system type are displayed in the navigation view.
-
Select the table whose outstanding objects you want to edit in the navigation view.
All objects marked as outstanding are shown on the form.
TIP:
To display object properties of an outstanding object
-
Select the object on the target system synchronization form.
-
Open the context menu and click Show object.
-
Select the objects you want to rework. Multi-select is possible.
-
Click on one of the following icons in the form toolbar to run the respective method.
Table 17: Methods for handling outstanding objects
|
|
Delete |
The object is immediately deleted from the One Identity Manager database. Deferred deletion is not taken into account.
Indirect memberships cannot be deleted. |
|
|
Publish |
The object is added to the target system. The Outstanding label is removed from the object.
This runs a target system specific process that triggers the provisioning process for the object.
Prerequisites:
|
|
|
Reset |
The Outstanding label is removed for the object. |
TIP: If a method cannot be run due to certain restrictions, the respective icon is disabled.
- Confirm the security prompt with Yes.
NOTE: By default, the selected objects are processed in parallel, which speeds up the selected method. If an error occurs during processing, the action is stopped and all changes are discarded.
Bulk processing of objects must be disabled if errors are to be localized, which means the objects are processed sequentially. Failed objects are named in the error message. All changes that were made up until the error occurred are saved.
To disable bulk processing
Related topics
Memberships, such as user accounts in groups, are saved in assignment tables in the One Identity Manager database. During provisioning of modified memberships, changes made in the target system may be overwritten. This behavior can occur under the following conditions:
-
Memberships are saved as an object property in list form in the target system.
-
Memberships can be modified in either of the connected systems.
-
A provisioning workflow and provisioning processes are set up.
If one membership in One Identity Manager changes, by default, the complete list of members is transferred to the target system. Therefore, memberships that were previously added to the target system are removed in the process and previously deleted memberships are added again.
To prevent this, provisioning can be configured such that only the modified membership is provisioned in the target system. The corresponding behavior is configured separately for each assignment table.
To allow separate provisioning of memberships
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
In the result list, select the target system type.
-
Select the Configure tables for publishing task.
-
Select the assignment tables that you want to set up for single provisioning. Multi-select is possible.
-
Click Merge mode.
NOTE:
-
This option can only be enabled for assignment tables that have a base table with a XDateSubItem column.
-
Assignment tables that are grouped together in a virtual schema property in the mapping must be marked identically.
- Save the changes.
For each assignment table labeled like this, the changes made in One Identity Manager are saved in a separate table. Therefore, only newly added and deleted assignments are processed. During modification provisioning, the members list in the target system is compared to the entries in this table. This means that only modified memberships are provisioned and not the entire members list.
NOTE: The complete members list is updated by synchronization. During this process, objects with changes but incomplete provisioning are not handled. These objects are logged in the synchronization log.
You can restrict single provisioning of memberships with a condition. Once merge mode has been disabled for a table, the condition is deleted. Tables that have had the condition deleted or edited are marked with the following icon: 
. You can restore the original condition at any time.
To restore the original condition
-
Select the auxiliary table for which you want to restore the condition.
-
Right-click on the selected row and select the Restore original values context menu item.
- Save the changes.
NOTE: To create the reference to the added or deleted assignments in the condition, use the i table alias.
Example of a condition on the UNSAccountBInUNSGroupB assignment table:
exists (select top 1 1 from UNSGroupB g
where g.UID_UNSGroupB = i.UID_UNSGroupB
and <limiting condition>)
For more information about provisioning memberships, see the One Identity Manager Target System Synchronization Reference Guide.
Changes made to individual objects in the target system can be immediately applied in the One Identity Manager database without having to start a full synchronization of the target system environment. Individual objects can only be synchronized if the object is already present in the One Identity Manager database. The changes are applied to the mapped object properties. If the object is no longer present in the target system, then it is deleted from the One Identity Manager database.
Prerequisites
-
A synchronization step exists that can import the changes to the changed object into One Identity Manager.
-
The path to the base object of the synchronization is defined for the table that contains the changed object.
To define the path to the base object for synchronization for a table
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
In the result list, select the target system type.
-
Select the Assign synchronization tables task.
-
In the Add assignments pane, assign the table for which you want to use single object synchronization.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the table and enter the Root object path.
-
If a concrete base object is defined for the target system, enter the path to the base object in the ObjectWalker notation of the VI.DB.
Example: FK(UID_GAPCustomer).XObjectKey
-
If no concrete base object is defined for the target system, enter the XObjectKey of the base table.
Example: <Key><T>DialogTable</T><P>RMB-T-Org</P></Key>
- Save the changes.
icon in the form's toolbar.