Chat now with support
Chat with Support

Identity Manager 8.1.5 - 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
Setting up Job servers 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
Using scripts Notes on message output Notes on using date values 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 of scripts in 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 executing scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
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

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 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 the 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

Creating local debug assemblies

To generate local debug assemblies

  1. In the Database Compiler, on the Compiler settings page, set the Create debug information option.

  2. Select the Scripts including all dependencies compiler setting.

  3. Start the compiler.

    During compilation you will see more messages that refer to creating the debug assemblies locally. Some compiler steps, for example, compiling web projects, are skipped because they cannot be debugged locally.

The Database Compiler saves the assemblies and associated PDB files in the %USERPROFILE%\AppData\Local\One Identity\One Identity Manager\AssemblyCache directory on the local computer.

The source code is saved in the %USERPROFILE%\AppData\Local\One Identity\One Identity Manager\AssemblyCache\Sources directory.

Therefore, the assemblies are not transferred to the database.

Debugging in the Object Browser

NOTE: You can debug locally until assemblies without debug data are generated on the workstation or new assemblies are loaded over a database connection.

To debug in the Object Browser

  1. Start the Object Browser and select the Debug | Debugger start/stop menu item.

    Visual Studio opens and the Object Browser is connected to the debugger. This process may take a few moments. If Visual Studio connection can be established, the Manage breakpoints dialog opens.

  2. In the Manage breakpoints dialog, you can define different breakpoints for scripts, templates, format scripts, table scripts, processes, and task definitions.

    • To define a new breakpoint, click and select one of the following options:

      • Script processing: Adds a breakpoint of Script type. Under Breakpoint operation, select a script.

      • Column processing: Adds a breakpoint of Column type. Under Breakpoint operation, select a format script, template, or script for conditionally removing permissions.

      • Table processing: Adds a breakpoint of Table type. Under Breakpoint operation, select a table script.

      • Process generation: Adds a breakpoint of Process type. Under Breakpoint operation, select a process.

      • Object method: Adds a breakpoint of Object method type. Under Breakpoint operation, select a task definition.

    • To use an existing breakpoint, select it in the list.
    • To delete a breakpoint, select it in the list and click .
    • To delete all breakpoints, click .

  3. Click OK.

    This closes the Manage breakpoints dialog. The breakpoint definitions are transferred to Visual Studio.

    NOTE: You can open the Manage breakpoints dialog again from the Debug | Configure breakpoints menu.

  4. In the Object Browser, execute the actions that you want to debug, for example, call a script, run a column template, or generate a process.

    The moment the action is about to be executed, Visual Studio is brought into the foreground and opens the place in the source code with the selected breakpoint. From this point on, all of Visual Studio's comprehensive debugging options are available to you in full. For example, use F10 to step through the code line for line or use F5 to continue with the program.

  5. After you have completed debugging, select the Debugger start/stop menu item to

    disconnect Visual Studio from the Object Browser and close it.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating