A search query using placeholders searches for the search pattern in the display values of the selected object definition.
To create a filter query using placeholders in the Manager
-
In the Manager, select the View | Database search menu item.
The database search is shown in the navigation view.
-
To open the advanced database search, click the Advanced button in the Search area.
-
Click New search and select the Wildcard search method.
-
In the Search parameter pane, enter the following information.
-
Search in: Select the object definition in which to perform the search.
-
Search pattern: Enter the search pattern. Use of wild cards * in the search pattern is permitted.
Example:
Pattern* - searches for all entries whose display value starts with the “Pattern” string
*Pattern - searches for all entries whose display value ends with the “Pattern” string
*Pattern* - searches for all entries whose display value contains the “Pattern” string
Pattern - searches for all entries whose display value matches the “Pattern” string
-
(Optional) If required, specify the following settings in the Optional parameter pane.
-
Sort criteria: Specify the properties (columns) by which to sort the search result. Click 
to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
Display template: Specify the format in which the results are displayed. Click to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
To save the search, enter a name and a description for the search filter in the Save search pane and click Save.
A search query with a SQL condition searches all entries of the selected object definition that match the SQL condition.
To create a filter query in the Manager using a SQL condition
-
In the Manager, select the View | Database search menu item.
The database search is shown in the navigation view.
-
To open the advanced database search, click the Advanced button in the Search area.
-
Click New search and select the SQL search method.
-
In the Search parameter pane, enter the following information.
-
Search in: Select the object definition in which to perform the search.
-
Search pattern: Enter the condition. Enter the condition as a WHERE clause for a database query. You can enter the database queries as a SQL query directly or compile the database queries with a wizard. Use the Expert view and Simple view button to switch to the appropriate view.
-
(Optional) If required, specify the following settings in the Optional parameter area.
-
Sort criteria: Specify the properties (columns) by which to sort the search result. Click to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
Display template: Specify the format in which the results are displayed. Click to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
To save the search, enter a name and a description for the search filter in the Save search area and click Save.
NOTE: To use the full-text search, you must run the program over an application server with an installed search service. For detailed information about installing an application server for full text search, see the One Identity Manager Installation Guide.
A search query using full-text search, searches for the specified search term in all columns of the selected object definition that are indexed for full-text search. For detailed information about configuring columns for the full text search, see the One Identity Manager Configuration Guide.
To create a search query in the Manager using the full-text search
-
In the Manager, select the View | Database search menu item.
The database search is shown in the navigation view.
-
To open the advanced database search, click the Advanced button in the Search area.
-
Click New search and select the Full text search method.
-
In the Search parameter pane, enter the following information.
-
(Optional) If required, specify the following settings in the Optional parameter area.
-
Sort criteria: Specify the properties (columns) by which to sort the search result. Click to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
Display template: Specify the format in which the results are displayed. Click to show all available properties according to the object definition. Click on a name to transfer the entry to the input field.
-
To save the search, enter a name and a description for the search filter in the Save search area and click Save.
Table 33: Rules with examples for searching
|
John Doe |
Finds John Doe but not John Donut.
Search results must contain all of the separate terms in the query. A logical AND is used. |
|
John OR Doe |
Finds Jane Doe and John Donut.
Placing OR between the search terms, acts as a logical OR operator. The result of this search contain at least one of the two search terms. |
|
John NOT Doe |
Finds John but not John Doe.
The results of this search do not contain the term that comes after NOT. |
|
J* |
Finds John and Joanna.
The * functions as a wildcard for any number of characters to complete the term. |
|
Do? |
Finds Doe but not Donut.
The ? functions as a wildcard for a single character to complete the term. |
|
"John Doe" |
Provides results in which the search terms John and Doe follow one another.
Results of this search contain the string in quotes as phrase. |
|
John Doe~ |
Finds Jon Does but also other similar results. A tilde ~ after the search term indicates that the search should also find similar results. The means that incorrectly spelled terms can be found as well.
You can specify the level of similarity by adding a number between 0 and 1 (with decimal point) after the tilde ~. The higher the number, the more similar the results. |
During the search, the search strings are broken down into tokens by the search index in use. The search terms are compared with these tokens.
Use the Common | Indexing | IndexNonTokenChars configuration parameter to specify which delimiters are to be used. The configuration parameter can be extended if certain characters in the search text have linking function.
If the Common | Indexing | IndexUseLegacyAnalyzer configuration parameter is enabled, alternative tokenizing is performed also. The alternative method of tokenizing is preferable for long tokens. For example, if the string "Department_01" is a token, the partial string "Department" is considered a token.
The following tokens are named.
Table 34: Tokens for alternative tokenizing
|
Words |
Sequence of letters and/or numbers |
|
Enumeration |
Words linked by punctuation marks (_-/.,) of which at least every second one contains a number.
An example is Department_01.
Sequences are also decimal numbers and IP addresses. |
|
Email addresses |
An email address is often made up of first name, last name, company name and generic top-level domain (for example .com). The order or spelling of the first and last names may vary (for example, use of initials). The special character @ and the punctuation mark (.) not only separate each part of the email address but also links them so that
Examples of email addresses are Ben.King@company.com or C.Harris@company.com. |
|
Host names |
For example, website.xyz.com |
|
Acronym |
For example, U.S.A. |
|
Apostrophe |
For example, O'Reilly |
|
@, & surrounded by letters |
For example, Me&you. |
| Umlauts such as ä, ö, ü |
For example, Max Müller. |
NOTE: Changing the configuration parameter means rebuilding the search index, which may take some time.
