Chatta subito con l'assistenza
Chat con il supporto

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

Copying scripts in the Script Editor

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.

To copy an existing script

  1. In the Designer, select the script that you want to copy from the Script Library category.

  2. Select the Copy script task.

  3. In the Copy script dialog, check the following information and correct if necessary.

    Table 140: Copying a script

    Property

    Description

    Old script name

    Name of the copied script.

    script

    The name of the new script is made up of the CCC_ prefix and the name of the old script. You can change the name. Prefix custom scripts with CCC_.

    Script code

    The script code from the original is copied over. If necessary, you can modify the script code of the script to copy beforehand.

  4. To create the copy, click OK.

  5. In the Script Editor, edit the main data of the script.

Related topics

Testing scripts in the Script Editor

You can use the Script Editor to test a script.

To test a script

  1. In the Designer, select the script in the Script Library.

  2. Select the Edit script task.

  3. Select the View > Test script menu item.

  4. In the Test script view, select the script from 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 Base and Value script base class variables as input parameters and use these in the script.

  5. Use Options to select one or more of the following options for running the test.

    • Use main database connection: 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: Specifies whether the script is run within a transaction with subsequent rollback or whether the script is run immediately against the database.

    • Record SQL log: Specifies whether the database actions should be recorded in an SQL log while the script is running. The output is displayed in a separate dialog window. The time to run the script is output in addition to the statement run.

  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 script compilation in the Script Editor

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

To test compiling scripts

  • In the Designer, select the script in the Script Library category.

  • Select the Edit script task.

  • Start compilation with the icon , the Script > Compile script menu item 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 more 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 overridable property.

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 the Designer, select the script to override in Script Library > Overridable scripts.

  2. Select the Copy script task.

  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. Prefix custom scripts with CCC_.

  4. To create the copy, click OK.

  5. In the Script Editor, replace the overridable property 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
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione