Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the 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 Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Using the Designer's Own Full-Text Search

Use full-text search to look for entries within the internal Designer database. You will find the full text search on its own menu bar in the Designer.

To search for a term

  • Enter your search term in the Search text box.

    You can enter more than one partial terms. Use of wild cards (*) is permitted. Case sensitivity is not taken into account. Entries are searched for that contain all the partial terms given.

Entries (objects) are already displayed while the search term is being entered.

Figure 6: Displaying the Source

  • The icon to the left of the entry shows the entry’s object type (table),e.g. a process, a table or a menu item.
  • The source that the object is extracted from is shown to the right of the entry. The search term is highlighted by an underline.
  • Database tables, object relations and the exact source are also displayed in a tooltip.
  • Double click on an entry to jump to the corresponding object.

If there is not entry found for an search term, suggestions are made that you can accept by double clicking with the mouse.

Figure 7: Suggestions for Search Terms

If you have selected an entry, the search term is added to the search history and is therefore available for further searches.

  • Open the search history with the arrow in the search text box.
  • When you select an entry, all available sources are shown.

The number of entries in the search history depends on your program settings.

Figure 8: Search History

TIP: Update the full text catalog of the Designer database if you need to include objects in the search that have been edited after the program started, like new processes or column names. You do this with the Update index item, in the search history.

Related Topics

Using User Defined Filters for Searching

It is possible to limit the number of list entries in certain Designer editors by using a filter. After creating a filter, the filter conditions are immediately implemented on the set of result currently displayed. A filter remains in use until you reset it.

  • Ad hoc filter

    Ad hoc filters are used for a one-off reduction of list entries. These filters are not saved and are applied to the data immediately.

  • Permanent filter

    A permanent filter is recommended if you want to reuse it more frequently. Permanent filters are saved in the user configuration and therefore are always available for use.

Detailed information about this topic

Using an Ad Hoc Filter

Ad hoc filters are used for a one-off reduction of list entries. These filters are not saved and are applied to the data immediately.

To use an ad hoc filter

  • Select Filter | Define filter... in the menu or use the icon .

    This opens the wizard for creating database queries. The wizard helps you to formulate a condition (where clause) for database queries. The complete database query is composed internally. It always refers to the database table that is specified when you start the wizard.

IMPORTANT: Enter the condition for limiting the result set in SQLite notation. The condition is defined as a valid where clause for database queries. The condition relates to the selected database table found that is determined when the editor starts.

For more information, see the One Identity Manager User Guide for One Identity Manager Tools User Interface and Default Functions.

Related Topics

Using a Permanent Filter

Permanent filters are saved and are therefore always available for use. There is a wizard to help you maintain permanent filters.

Table 9: Meaning of the Icons in the Toolbar
Icon Meaning
Adds a new filter.
Edits filter name.
Deletes filter.
Switches between displaying database query input in SQLite notation or in the wizard.
Tests filter.

To create a permanent filter

  1. Select the menu Filter | Manage filters... or use the arrow next to .

    This opens the wizard for managing filters.

  2. Select the icon and enter the name of the filter on the left-hand side of the wizard. These names are also used for the entries in the editor menus and can therefore always be selected for use.
  3. Enter the conditions for limiting the number of results on the right-hand side. The condition is defined as a valid where clause for database queries. You can enter the condition directly in SQLite notation or by using the database query wizard. Us the icon to change between input methods.

    IMPORTANT: Enter the condition for limiting the result set in SQLite notation. The condition is defined as a valid where clause for database queries. The condition relates to the selected database table found that is determined when the editor starts.

  4. Test the condition using the icon.

    After the test is completed, a test report is displayed. All the list items are shown that meet the condition. A summary of the test status is also shown.

  5. Click Ok to save the filter.

For more information, see the One Identity Manager User Guide for One Identity Manager Tools User Interface and Default Functions.

Related Topics
Related Documents