Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the 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 Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Testing a Script with the Script Editor

Testing a Script with the Script Editor

You can use the Script Editor to test a script.

To test a script

  1. Select the script in the category Script Library in the Designer
  2. Select the task Edit script 'name of script'.
  3. Select the Test script view.
  4. Select the script to test in the menu and modify the parameters as required.

    All the parameters to be passed to the script are displayed with their data types. You can edit the values. You can also predefine values for the script base class variables "Base" and "Value" as input parameters in order to work with the script.

  5. Select one or more options for running the test from the Options list.
    Option Description
    Use master connection This option specifies whether the script test is tested against the main database or an internal SQLite database. Scripts that relate to the application part of the One Identity Manager data model should always be tested with the main database. Scripts for system parts can be test with against the main database or the internal SQLite database.
    Use transaction Use this option to specify whether a script is going to be executed within a transaction including subsequent rollback or whether it is going to be executed immediately against the database.
    Write SQL Log You can record the database actions in an SQL log whilst the script is running. The output is displayed in a separate dialog window. The execution time of the script is logged in addition to the statement being executed.
  6. Select the Start button to run the script test.

    The test results are displayed in the Result field after the script has been run.

Related Topics

Testing Scripts with the System Debugger

Testing Scripts with 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.

The following software must be installed to use the System Debugger:

  • Visual Studio 2010 or later
  • Microsoft .NET Framework Version 4.5.2 or later

    NOTE: Microsoft .NET Framework version 4.6 is not supported.

NOTE: To use the System Debugger with privileges without starting Visual Studio, you must install the One Identity Manager components in a local directory which is not controlled through user accounts.

Detailed information about this topic

Loading the System Library

A solution template SystemLibrary.sln with the solution "SystemLibrary" is loaded for editing and testing in System Debugger when the Visual Studio is called.

The following projects are defined in the solution.

Table 274: Solution Project Files
Project Script File Description
Methods Methods.vb This script file contains all methods.
Scripts VIScripts.vb This script file contains all predefined scripts from the model components. Do not edit these scripts as they are overwritten by migration.
VIDScripts.vb This script file contains all predefined scripts from the system components Do not edit these scripts as they are overwritten by migration.
CustomerScripts.vb This script file contains custom scripts. Add new scripts here.
SystemDebugger Main.vb Start up project.
Tables Tables.vb This script file contains all the table scripts.
Templates Templates.vb This script file contains all templates and formatting scripts.

To load the system library

  1. Select Start | One Identity | One Identity Manager | Configuration | System Debugging.

    - OR -

    Run the file SystemLibrary.sln from the installation directory.

  2. Check whether the project "SystemDebugger" is entered in Visual Studio as the start project.
  3. Start the solution with F5 in Visual Studio.
  4. Connect to the database.
  5. Check the solution file directory and the options for creating the script library.
    Options Meaning
    Export locked scripts Specifies whether only active scripts or other locked scripts are loaded from the library as well.
    Update project references Specifies whether references used in scripts are loaded as well.
    Create backups of existing files Specifies whether backups of existing files are made.
  6. Click OK.

    The script library files are filled with data from the database.

  7. Confirm reloading of each project in Visual Studio.
  8. Start the solution with F5 in Visual Studio.

    The source code generated for the solution is compiled.

  9. Reconnect to the database.

    Starts the System Debugger.

NOTE: The project setting Start external program must be set to <InstallFolder>\SystemLibrary\SystemDebugger\bin\Debug\SystemDebugger.Oracle.exe.

Related Topics

Testing and Editing Scripts

The System Debugger gives you the opportunity to test and, if necessary, edit scripts that are stored in the script library. Here you have Visual Studio debug and edit options available, in contrast to the Script Editor.

Detailed information about this topic
Related Topics
Related Documents