Converse agora com nosso suporte
Chat com o suporte

Identity Manager 9.2.1 - 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
Overview of the One Identity Manager schema Table types and default columns in the One Identity Manager data model Notes on editing table definitions and column definitions Table definitions Column definitions Table relations Dynamic foreign key Supporting file groups
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 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 One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Troubleshooting debugging in the Object Browser

Problem

In the Database Compiler, the Create debug information is not shown.

Cause

The system user used is not assigned the Common_CompileForDebug program function through its permissions groups.

Solution

In the Designer, assign the program function to a custom permissions group and add the system user to this permissions group. For more information about controlling conditions with program functions, see the One Identity Manager Authorization and Authentication Guide.

Problem

The Debug menu is not shown in the Object Browser.

Possible cause

  • Visual Studio is not installed with the required options.

  • The assemblies do not contain debug information.

Possible solutions
Problem

Breakpoints are shown as disabled in Visual Studio.

Cause

Breakpoints are shown as disabled if the assembly with the function to be debugged is yet not loaded into memory. For example, the assemblies for generating processes are not loaded into the application until the point of generation. From then on the breakpoint is enabled and you can jump to it.

Problem

Breakpoints in Visual Studio are always shown as disabled and you cannot jump to them.

Possible cause

  • The Object Browser still has the wrong assemblies loaded.

  • The Object Browser could not find debug information for the assemblies.

Possible solution

If Visual Studio is connected the Object Browser, switch to Visual Studio and open the Debug > Windows > Modules. Here you will find a list of all the modules that are loaded and additional information.

One Identity Manager query language

One Identity Manager has a language (One Identity Manager query language) to create queries or Where clause expressions against the One Identity Manager object layer.

For example, the One Identity Manager query language is used to communicate between application servers and clients. Currently, you can use the One Identity Manager query language in the Object Browser's query window .

The query language is not case sensitive. Keywords can be written in upper or lower case. To be able to identify them more easily, keywords are always written in capital letters in the following examples.

In a lot of parts, the query syntax is based on SQL syntax. This makes it easier to convert simple Where clauses from SQL syntax to the query syntax.

Detailed information about this topic

Language elements of the One Identity Manager query language

The One Identity Manager query language supports different language elements.

Detailed information about this topic

Comments

There are two types of comments in the One Identity Manager query language. These are analog to comments in SQL syntax:

Line comments

Line comments start with -- and end at the end of the line.

-- This is a line comment

Line comments do not have to be at the beginning of the line.

FROM Person -- This is a line comment too

Block comments

Block comments start with the /* and end with */. Block comments can span more than one line.

/* This is a block comment

that spreads over

more than one line */

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação