Search using Wildcards
The system searches for the search term in the display values of the selected object definition, using the wildcards.
To perform a search using wildcards
- Select the method Wildcard in "Search method".
- Select the object definition you want to search in from the Search in menu under "Search parameter".
- Enter the Search pattern under "Search parameter".
Use of * (asterisk) in the search pattern is permitted.
Example
abc* - searches for all entries with a display value starting with the string "abc"
*abc - searches for all entries with a display value ending with the string "abc"
abc - searches for all entries with a display value containing the string "abc"
Searching with SQL Conditions
Searching using SQL Conditions
With a condition, the system searches for all entries that match the specified condition and correspond to the selected object definition.
To perform a search using a condition:
- Select the method SQL in "Search method".
- Select the object definition you want to search in from the Search in menu under "Search parameter".
- Enter the Search pattern under "Search parameter".
Enter the condition as a WHERE clause for a database query. You can enter the SQL query directly or with a wizard. Use the Expert view and Simple view buttons to switch to the appropriate view.
Search using Full Text
The system performs a full text search for the specified search term. To use full text search in the Manager, you must run the Manager 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.
To perform a full text search
- Select the method Full text in "Search method".
- Select the object definition you want to search in from the Search in menu under "Search parameter".
- Enter the Search pattern under "Search parameter".
| Example | Description |
|---|---|
|
John Doe |
Finds John Doe but nor John Donut. Search results must contain ALL of the separate terms in the query. A logical "AND" is applied. |
|
John OR Doe |
Finds Jane Doe and John Donut. Adding an "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. Results of this search do not contain the term, which comes after "NOT". |
|
J* |
Finds John and Joanna. The * is a wildcard for any other characters, which complete the term. |
|
Do? |
Finds Doe but not Donut. The ? is a wildcard for one more character, which completes the term. |
|
"John Doe" |
Finds results in which "John" and "Doe" 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, allows the search to 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.
You can define delimiters in the configuration parameter "Common\Indexing\IndexNonTokenChars". The configuration parameter can be extended if certain characters in the search text have linking function.
Alternative tokenizing is used, if the configuration parameter "Common\Indexing\IndexUseLegacyAnalyzer" is set. 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 to be a token.
The following tokens are named.
| Token | Description with Example |
|---|---|
|
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. |
Exporting and Importing Filters
Exporting and Importing Filters
To make customized filters available to other users, you can export and import filters.
To export a filter:
- In the category My One Identity Manager | My filters, select the filter.
- Start the export by clicking Export filter... on the context menu.
- Via the file browser, select the directory path for the report and enter a file name for the filter.
- Click Save.
The filter file (*.xml) is created.
To import a filter:
- Select the category My One Identity Manager | My filters.
- Start the import by clicking Import filter... on the context menu.
- Select the filter file from the file browser.
- Click Open.