Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Identity Manager 8.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 SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Testing methods in the System Debugger

To test a method

  1. In the System Debugger, select the method in the Dialog methods area.

  2. Select the object to apply the method to under Base object.

  3. Check the Transaction with roll back option for running the methods.

    Use this option to specify whether the method is run within a transaction with subsequent rollback or whether the method is run immediately against the database.

  4. Select Start.

    The method starts running.

Related topics

Testing table scripts in the System Debugger

To test table scripts

  1. In the System Debugger, select the table and table script from the Tables view.

  2. Select the object to test the table script on under Database object.

  3. Check the Transaction with roll back option for running the table scripts.

    Use this option to specify whether the table script is run within a transaction with subsequent rollback or whether the table script is run immediately against the database.

  4. Select the following actions to test the table script.

    Action Meaning

    Save

    The object is saved. (OnSaved, OnSaving)

    Discard

    The changes made to the object are discarded. (OnDiscarded, OnDiscarding)

    Load

    The object is reloaded. (OnLoaded)

    New

    A new object is created.

Related topics

Saving changes to the database

To save changes to the database

  1. In the System Debugger, select the script, template, formatting script, method, or the table script.

  2. Select the Scripts > Save script menu item.

    This opens a dialog displaying the script name, database object, database connection, and script code to be added.

  3. Select a change label under Change labels to group your changes.

  4. Click Save.

TIP: To save several scripts in the Scripts view, hold the CTRL key down, click on the scripts and select the Scripts > Save script menu item.

NOTE: Ensure you recompile the database after making changes.

Extended debugging in the Object Browser

The Object Browser supports debugging of scripts, templates, format scripts, table scripts, processes, and methods. You can make use of the Visual Studio debug options for this purpose. You cannot alter the scripts, templates, formatting rules, table scripts, processes, or methods. Correct the errors in the Designer.

Prerequisites
  • To use the debug function in the Object Browser, you must install the following software:

    • Visual Studio 2012 with the current service pack

    • Microsoft .NET Framework 4.7.2 Developer Pack or later

  • The user requires the Allows local debug assemblies to be created program function (Common_CompileForDebug). This provides the user with an additional compiler option in the Configuration Wizard for creating local debug assemblies.

    In the Designer, assign the program function to a custom permissions group and add the system user to this permissions group. For more information about controlling conditions with program functions, see the One Identity Manager Authorization and Authentication Guide.

  • Local debug assemblies are available on the user's local workstation.

Detailed information about this topic
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation