Chatta subito con l'assistenza
Chat con il supporto

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

Query parameter clauses

In the One Identity Manager query language, query parameter clauses allow values to be passed in parameters that can be used in where clauses. You can pass a single parameter or a list of parameters.

Syntax for a single parameter

PARAM <Parameter name> [ OF <Type> ] = <Value>

Syntax for multiple parameters

PARAMS

<Param1> [ OF <Type> ] = <Value>,

<Param1> [ OF <Type> ] = <Value>,

Permitted parameter names are:

  • Syntax for parameter references with a qualifying @ character

  • Identifier

Valid types are the .Net data types of the object layer defined in ValType enumeration. If the type can be derived from the value, you do not have to give a type.

Examples of query parameters

PARAM Parameter1 = 'User'

PARAM @Parameter2 = 'User'

PARAM Parameter3 OF String = 'User'

PARAM @Parameter4 OF String = 'User'

PARAM Parameter5 = 42

PARAM Parameter6 OF Int = 42

PARAMS

Parameter7 OF Double = 3.14,

Parameter8 OF Date = 2020-04-30

Example: Complete query with parameter reference and definition

FROM Person

WHERE LastName = @Param1

SELECT DISPLAYS

PARAM Param1 = 'User'

Related topics

Query hints

Query hints (keyword HINT) can be used in the One Identity Manager query language to provide the query processor with additional data. Query hints are used internally to provide a context for additional permission queries to display columns that are only available when loaded as display values for foreign keys of another table.

HINT 'Name' = 'Value'

Example: Loading an identity that is referenced in a company structure as UID_PersonHead

FROM Person

WHERE PRIMARYKEY '<Key><T>Person</T><P>99918ef1-113f-480a-8e6e-704b1a3cf73a</P></Key>'

SELECT DISPLAYS

HINT 'SourceContext' = 'Org'

Conditions

Conditions combine all expressions that filter the resulting entities according to one or more criteria.

In the One Identity Manager query language, conditions can be linked with the AND and OR operators. You can overwrite operator precedence with curly brackets ({ }). Conditions can be inverted using the NOT keyword.

Example of a condition

WHERE Lastname = 'User'

AND (Firstname = 'Alex' OR Firstname = 'Sam')

Related topics

Special conditions

Selecting an entity using the primary key

n the One Identity Manager query language, use the PRIMARYKEY keyword to select the entity with the matching primary key. The primary key must be given in object key notation.

WHERE PRIMARYKEY 'Object Key'

Example

FROM Person

WHERE PRIMARYKEY '<Key><T>Person</T><P>99918ef1-113f-480a-8e6e-704b1a3cf73a</P></Key>'

SELECT DISPLAYS

Selecting an entity using a key

Use the KEY keyword to select the entity with the matching key. Keys can be object keys or alternative object keys, each in their XML notation.

WHERE KEY 'Key'

Example

FROM ADSAccount

WHERE KEY '<Key><Table Name="ADSAccount" Key="c149784b-6386-45d7-a38d-3c6e8e1b69d4"><Prop Name="UID_ADSAccount"><Value>c149784b-6386-45d7-a38d-3c6e8e1b69d4</Value></Prop></Table></Key>'

SELECT COLUMNS cn

Select using predefined SQL

With the LIMITEDSQL keyword you use a preformatted Where clause from the QBMLimitedSQL table. Any parameters used in it can be specified with the PARAMETER or the PARAMETERS clause.

WHERE LIMITEDSQL 'Identifier'

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione