You can use the Script Editor to test a script.
To test a script
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.
|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.|
The test results are displayed in the Result field after the script has been run.
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:
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.
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.
|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
- OR -
Run the file SystemLibrary.sln from the installation directory.
|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.|
The script library files are filled with data from the database.
The source code generated for the solution is compiled.
Starts the System Debugger.
NOTE: The project setting Start external program must be set to <InstallFolder>\SystemLibrary\SystemDebugger\bin\Debug\SystemDebugger.Oracle.exe.
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.