Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting 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 in Designer 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 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 Appendix: Configuration files of the One Identity Manager Service

Testing script compilation in the Script Editor

If you have created a new script, you need to compile it. The script is not executable until it has been compiled. You can test script compilation in the Script Editor.

To test compiling scripts

  • In Designer, select the script from the Script Library.
  • Select the task Edit script.
  • Start compilation with the icon , menu item Script | Compile script or F9.

All scripts are converted during compilation. The assemblies are created and placed on the workstation where generating will take place. During the conversion, the script code is tested for validity. This process may required some time.

Error messages are sent to the Compiler errors view. A double-click on the error message takes you straight to the corresponding line in the script code view where you can edit it. It can be modified at this point.

IMPORTANT: Once you have tested the script it needs to be added to the One Identity Manager database and compiled with the Database Compiler. For detailed information, see the One Identity Manager Operational Guide.

Overriding scripts

You might want to label scripts for overriding if there are limits to how much you can modify default scripts. Scripts that can be overwritten are labeled with the property overridable.

NOTE: Only the default scripts that are supplied can be overriden. Custom scripts cannot be overridden because these are saved in a Custom scripts script class.

To override a script

  1. In Designer, select the script to override in Script Library | Overridable scripts.
  2. Select Copy script.
  3. In the Copy script dialog, edit the following information.
    • Script: The name of the new script is made up of the prefix CCC_ and the name of the old script. You can change the name. Label custom scripts with the prefix CCC_.
  4. To create the copy, click OK.
  5. In the script editor, replace the property overridable with overrides in the script header.
  6. Modify the other script code accordingly to suit your requirements.

IMPORTANT: After creating and editing the script, you should test compiling the script. Compile the scripts in the script library for this script to take effect.

Syntax example

Public overridable Function My_Function() as Boolean

'script code of the original version

End Function

Public overrides Function My_Function() as Boolean

'Custom script code

End Function

Related Topics

Editing and testing script code 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 2012 or later
  • Microsoft .NET Framework Version 4.7.2 Developer Pack or later

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

When you call the System Debugger, a SystemLibrary.sln solution template with the SystemLibrary solution is loaded in theVisual Studio for editing and testing the scripts.

The following projects are defined in the solution.

Table 157: 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.
VIDScripts.vb This script file contains all predefined scripts from the system components.
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. Run the SystemLibrary.sln file in the One Identity Manager installation directory.

  2. Check whether 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 system scripts

    Specifies whether predefined scripts are loaded into the system library.

    Export custom scripts

    Specifies whether custom scripts are loaded into the system library.

    Export locked scripts Specifies whether only active scripts or also locked scripts are loaded from the script library.
    Update project references Specifies whether references used in scripts are also loaded.
    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.

Related Topics
Related Documents