Chat now with support
Chat mit Support

Identity Manager 8.1.5 - Installation Guide

About this guide One Identity Manager overview Installation prerequisites Installing One Identity Manager Installing and configuring the One Identity Manager Service Automatic updating of One Identity Manager Updating One Identity Manager Installing and updating an application server Installing the API Server Installing, configuring, and maintaining the Web Portal Installing and updating the Manager web application Logging in to One Identity Manager tools Troubleshooting Creating a One Identity Manager database for a test or development environment from a database backup Advanced configuration of the Manager web application Machine roles and installation packages

Log message for search index creation

Indexing log messages are stored in the application server log (\App_Data\Logs\AppServer.log by default).

A new indexing run usually starts after the indexing interval period specified by the Common | Indexing | Interval configuration parameter has elapsed.

If a table being indexed contains more objects to be indexed than the maximum specified by the Common | Indexing | BatchSize configuration parameter, then the indexing process for the table will stop.

A message is written to the application server log:

INFO (Indexing ) : Index for Person partially updated, will continue at next run

If at least one table has not been fully indexed, then indexing will restart after three seconds. A message is written to the application server log:

INFO (Indexing ) : Index is incomplete (28.06%); indexing will continue in 3000 ms

If a signal to reuse (<recycling>) the application pool has already been received, the log message will read, for example:

INFO (Indexing ) : Index is incomplete (28.06%); indexing will continue when the application re-starts

As long as there is at least one incomplete table, then only the incomplete tables will be indexed during an indexing run.

Creating a One Identity Manager database for a test or development environment from a database backup

NOTE: Additional steps are required if you work with granular permissions concepts at SQL level. In this case, contact support. To access the Support Portal, go to https://support.oneidentity.com/identity-manager/.

To create a test or development database from a database backup from another system

  1. Create a new database on the database server in the reference environment.
  2. Create a database backup of the original database.
  3. Restore the backup to the reference database.
  4. Restore permissions for the database user on the database server.
  5. Compile the database with the Database Compiler.

    Use the Database Compiler to customize connection data for the database and compile all scripts and processes in the database.

    1. Open Launchpad and select Compile the database. This starts the Database Compiler.
    2. On the Database Compiler start page, click Next.
    3. On the Connect to database page, enter the connection data for the One Identity Manager database.
    4. The database ID is verified. If, during the verification, it transpires that the database ID is incorrect, you will be prompted to create a new ID. Confirm this prompt with OK. The database ID is changed.
    5. On the Database connection information insufficient page, check the database connection data and change if necessary.
      • Test the connection parameters (ConnectionString).

        Change the entry using the [...] button beside the input field. Select your database connection data.

      • Test the full customer name.
    6. This test the database connection. Confirm the prompt with OK.

    7. Enter the valid connection data for the One Identity Manager database.

    8. On the Connect to database page, enter the connection data for the One Identity Manager database.

    9. The components to be compiled are displayed on the Compilation settings page. To start compiling, click Next.

      This starts the compilation process. The process may take some time.

    10. The results of the compilation process are shown on Compilation. Click Next after compilation is complete.
    11. Click Finish on the last page to end the program.
  6. In the Designer, adjust the database staging level of the database.

    1. In the Designer, select the Base Data | General | Databases category.

    2. Select the database and change the value of the Staging level property to Test environment or Development system.

    3. Select Database | Save to database and click Save.

  7. Customize the synchronization project's connection data in the Synchronization Editor.
Related topics

Advanced configuration of the Manager web application

NOTE: The Web Installer uses default values for most configuration settings. You can use these values normally. It is recommended you check the settings with the help of the Manager Web Configuration Editor.

You configure the Manager web application configuration with the Manager Web Configuration Editor. The Manager Web Configuration Editor is part of the web application and can be found in the install directory in the subdirectory WebConfigEditor.

To run configuration

  1. Start the file WebConfigEditor.exe and log in to the One Identity Manager database.

    The Manager Web Configuration Editor automatically opens the web.config file of the web application.

  2. Modify the configuration settings.

  3. Save the changes.
Detailed information about this topic

General

In the General pane, you configure the appearance of the Manager web application.

Table 48: Meaning of general configuration settings
Setting Description

Language

Language. The language influences how dates and numbers displayed amongst other things.

Session timeout

User's idle time in minutes after which the user is automatically logged out. This value depends on the timeout mode and directly effects memory requirements and therefore the application's performance.

NOTE: This value should be set as long as required and as short as possible because orphaned sessions use memory and negatively effect the application's performance.

Timeout mode

Methods for determining timeouts. Permitted values are:

  • TimeOut: A session is ended when the period of time defined under the session timeout has elapsed with no user activity.

  • HeartBeat: A session is ended when the period of time defined under the session timeout has elapsed with no user activity. The user's open browser window prompts automatically. The timeout begins when the browser window is closed.

Visualization

Visualization of the application.

Dynamic design select

Not in use.

Enable portal mode

Permits the application in a frame to be linked to another application.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen