サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.0 LTS - 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 One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Query header

Data queries in the One Identity Manager query language always start with the FROM keyword and a table name. An optional alias for the table can be specified after the AS keyword.

FROM <table name>

FROM <table name> AS <table alias>

An alternative is to query directly using an object key.

Example of the query in long form

FROM Table WHERE PRIMARYKEY '<Key><T>Table</T><P>UID</P></Key>'

Example of the query in short form

FROM '<Key><T>Table</T><P>UID</P></Key>'

You can specify a list of clauses after the query header. The clause types do not have to be in any particular order.

Where clauses

Where-clauses in the One Identity Manager query language start with the WHERE keyword and contain a condition that the resulting data must match. Unlike SQL syntax, multiple Where clauses can be combined in a One Identity Manager query language query.

Examples of Where clauses

WHERE Lastname = 'User1'

WHERE Lastname = 'User1' AND Firstname = 'Chris'

WHERE [isnull(lastname, '') = N'User1]

WHERE Lastname IN ('User1', 'User2')

WHERE XDateInserted IN RANGE LAST MONTH

Related topics

Search clauses

In the One Identity Manager query language the SEARCH keyword is used to search for all matching entries from the full text index. To use this type of clause, a full text index must be installed and accessible from the application.

SEARCH 'Search string'

Select clauses

The One Identity Manager query language Select clauses describe the data that is fetched from the underlying database. You define the minimum amount of returned data. The object layer can select more data to meet arbitrary requirements. An example is the primary key, which is always selected, or special columns like the X columns.

Multiple select clauses can be combined into one query.

Different variations of the Select clause are supported.

Selecting specific columns of a table

SELECT COLUMNS <list of columns>

Example

FROM Person

SELECT COLUMNS Firstname, Lastname, CentralAccount

Select all columns of a table

SELECT ALL

Selecting all display values of a table

SELECT DISPLAYS

Display columns that are selected are:

  • The table's display pattern (DialogTable.DisplayPattern)

  • The table's display pattern (long) (DialogTable.DisplayPatternLong)

  • Primary key of the table

In the case of returned entries, the table's display pattern and the display pattern (long) can be overwritten by a display value clause. For more information, see Display value clauses.

Selecting the table's display pattern

SELECT DISPLAYPATTERN

Selects only the columns from the table's display pattern or DISPLAY clause if it is used. This can provide improved performance over SELECT DISPLAYS because fewer columns are selected.

Select all columns of a table that are not marked as a BLOB field

SELECT NONLOBS

Selects all columns of the table that are not marked as a very long binary object or text object by the DialogColumn.IsBlobExternal column.

A matching entry exists

EXISTS

Determines whether an entry exists that fulfills the WHERE clause. The Exist clause overrides all other Select clauses except the Count clause.

Determine the number of matching entries

COUNT

Counts the entries that fulfill the where clauses. The Count clause overrides all other clauses.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択