Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Editing script code in the System Debugger

After loading the system library, you can edit scripts, templates, formatting scripts, methods and table scripts in the System Debugger and test them.

Note the following:

  • You are not permitted to edit VI-Key comments in the source code or to delete them because they label each code block and are needed for backing up scripts in the database.
  • When templates and formatting scripts are loaded, the $ notation is converted into a GetTriggerValue method call. All GetTriggerValue methods calls are converted into $ notation when the changes are saved in the database.

    Example:

    $FK(UID_Person).IsExternal:Bool$ is converted into GetTriggerValue("FK(UID_Person).IsExternal").Bool when it is loaded

  • You can use the Script Editor in the Designer to create scripts. Enter the name of the script in the Script Editor and a skeleton script body. This you can export to the script library where you can edit the script with the System Debugger.
  • You can created templates, formatting scripts, methods and table scripts in the Designer. You can edit these elements with the System Debugger after you have exported them to the system library.
Related Topics

Logging database queries and object actions

Use database query and object action logging in the System Debugger to look for errors and optimize scripts during development. The execution time and the command that was run are logged.

  • SQL log

    Open the log dialog box by selecting View | SQL protocol.

  • Object log

    Open the log dialog box by selecting View | Object log.

Table 158: Functions for Logging Database Queries and Object Actions
Icon Meaning
Starts recording.
Stops recording.
Copies logged data to the clipboard.
Save logged data in a file.
Deletes the logged data.

Testing script code in the System Debugger

The System Debugger gives you the opportunity to test scripts, templates, formatting rules, methods and table scripts. Visual Studio debug and edit options are available to you.

Detailed information about this topic

Testing scripts in the System Debugger

To test a script

  1. Select the desired script in the System Debugger in Scripts.
  2. Enter value for the script parameters as required.
  3. Check the options for executing the script.
    Option Meaning
    Run in debug mode Jumps into the source code. This allows you to use all Visual Studio debugging options.
    Define base data The variables Base and Value of the script base class can be preallocated as input parameters to be used in the script.

    Example:

    Base is initialized with a DB object key in order to use base.GetValue("column name").String.

    Transaction with rollback Use this option to specify whether the script is executed within a transaction with subsequent rollback or whether the script is executed immediately against the database.
  4. Select Start.

    The script starts executing. After the script has executed, the result and the execution time of the script is displayed.

Related Topics
Related Documents