Managing project templates
The provides an overview of all available . Here you can edit display names and descriptions of project templates and delete project templates you no longer need.
To display a list of project templates
-
Select the Database > Manage templates... menu item.
This menu item is only displayed in export mode.
This opens the dialog window Manage templates....
-
To hide custom project templates, disable 
in the dialog box toolbar.
-
To hide default project templates, disable 
in the dialog box toolbar.
Table 82: Project template properties
|
Project template |
Name of the project template. |
|
|
Type of target system, which applies to the project template. |
|
Supported versions |
Version of the target system that are supported by this project template. If no value is displayed, the project template supports every version that can be connected with the target system connector. For detailed information, see the administration manuals for connection to the respective target system. |
|
Description |
Description of the project template. |
|
Last change |
Date of the last change to the project template. |
To edit a custom project template
-
Enable in the dialog box toolbar.
-
Select the project template.
-
Edit the display name or description in the Properties pane.
-
Click Save and close.
- Confirm the security prompt with Yes.
To delete a custom project template
-
Enable in the dialog box toolbar.
-
Select the project template.
-
Click 
in the dialog box toolbar.
- Confirm the security prompt with Yes.
-
Click Save and close.
- Confirm the security prompt with Yes.
Include custom tables in the synchronization
schema extensions can be included in the configuration. Custom columns are automatically assigned to additional schema properties which can be included in the mapping. The following settings must be made in order to include custom tables that were created using the default in .
To prepare a custom table for synchronization
-
In the Manager, assign a target system type to the custom table.
-
In the , select a synchronization project and create a schema class for the custom table in the One Identity Manager schema.
-
In the Synchronization Editor, define the mapping and for the schema class.
For detailed information about target system types and post-processing outstanding object, see the target system connection guides.
Integrate a custom table into provisioning processes
-
In the , define the provisioning operations.
Use the settings from other operations for the same target system and modify the following properties:
To publish outstanding objects in a custom table
-
Create a process that performs provisioning of objects for:
- Simple tables
- that contain additional information, such as a valid-from date
Use the AdHocProjection of the ProjectorComponent .
For detailed information about defining processes, see the One Identity Manager Configuration Guide.
-
Create the HandleOutstanding event for this process.
For memberships mapped to simple assignment tables, the Dependencies modified on (XDateSubItem column) is changed on the base table of the mapping when publishing. This triggers the default update process that is set up for this base table. For more information, see Changing a membership label.
Configuring single object synchronization for a custom table
-
In the Designer, define the operations for single object synchronization.
Use the settings from other operations for the same target system and modify the following properties:
-
In the Designer, assign the custom table to customizer DPR..ProjectorReadEntityLogic.
-
Create a process in the Designer for the custom table.
Use the settings from another read process for the same target system and modify the following properties.
- Replace all references to the original table with a reference to the custom table.
Process properties:
Process step properties:
For detailed information about setting up processes, see the One Identity Manager Configuration Guide.
-
Record the path to the base object of synchronization for the custom table in the Manager.
For detailed information about this, please consult the manuals for connecting target systems.
Detailed information about this topic
Related topics
Validating scripts
You can apply scripts at various points in the ; for example, when defining the schema properties, in the object filter, or when you define data operations for system connections through the . You can enter scripts in C# or Visual Basic .NET depending on script's language, which was specified for the synchronization project.
You can use the available compiling and debugging functions to troubleshoot script.
Compile
To verify the script's syntax
- Open the script in the .
- Click Compile.
Compiler errors are shown immediately and written to in the Synchronization Editor's error log.
Debug
The script is exported to a Visual Studio project for debugging. Once the project is run, the Synchronization Editor starts in debug mode and the script is tested.
Prerequisites
- Visual Studio is installed on the workstation on which the Synchronization Editor is running.
- All changes to the synchronization project are saved.
- The debugger can be used in scripts that are used in:
- Schema properties
-
- Data operations for system connections using the generic database connector
To debug a script
- Open the script in the Synchronization Editor.
- Click Debug.
- Confirm the prompt with OK.
- Start debugging in the Visual Studio project.
- If necessary, correct the script in the Synchronization Editor's default mode.
- Save the changes.
Related topics
Starting synchronization
You can also start manually by either running it on your workstation or from the . If you run synchronization from your workstation, you cannot work with the until synchronization is complete. To be able to continue working with the Synchronization Editor during synchronization, run synchronization from the synchronization server.
To start synchronization manually
-
In the Synchronization Editor, open the .
-
Select the Configuration > Start up configurations category.
-
Select a start up configuration in the document view and click Run.
- Confirm the security prompt with Yes.
Compile
Script was compiled without errors.
Script contains syntax errors.
Debug