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
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. |
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
|
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. |
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
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.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. |
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.
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
Run the SystemLibrary.sln file in the One Identity Manager installation directory.
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. |
The script library files are filled with data from the database.
The source code generated for the solution is compiled.
Starts the System Debugger.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy