Chatta subito con l'assistenza
Chat con il supporto

Identity Manager 9.1.2 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing 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
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Tips for 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

  • In the Designer, you can use the Script Editor 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.

  • In the Designer, you can created templates, formatting scripts, methods, and table scripts. 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 processing time and the command that was run are logged.

  • SQL log

    Open the log dialog box by selecting the View > SQL log menu item.

  • Object log

    Open the log dialog box by selecting the View > Object log menu item.

Table 143: 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. In the System Debugger, select the desired script in Scripts view.

  2. Enter value for the script parameters as required.

  3. Check the options for running the script.

    • Run in debug mode: Jumps into the source code. This allows you to use all Visual Studio debugging options.

    • Define base data: The Base and Value variables of the script base class can be pre-allocated 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 run within a transaction with subsequent rollback or whether the script is run immediately against the database.

  4. Select Start.

    The script starts running. After the script has run, the result and the processing time of the script is displayed.

TIP: To find scripts more easily, you can use the following functions in the Scripts view.

  • In the Find script field, enter the string to filter on.

  • Modified scripts are marked with a * in the System Debugger.

  • To find all modified scripts, click and apply the Changed scripts menu item.

Related topics
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione