Chat now with support
Chat with Support

Identity Manager 8.1 - 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 Error handling Appendix: Creating a One Identity Manager database for a test or development environment from a database backup Appendix: Extended configuration of the Manager web application Appendix: Machine roles and installation packages Appendix: Settings for a new SQL Server database

Removing superfluous modules

You can remove modules from the One Identity Manager database that you no longer require in your system.

IMPORTANT:

  • By removing a module, you lose all the data that goes with it. So it is important to make a backup of the One Identity Manager database before removing any modules.

  • In certain circumstances, dependencies to other modules may be deleted by removing a module, therefore, update the One Identity Manager schema after removing a module.

  • Other tests may be necessary after removing a module. Remove the module in your test environment first and test the One Identity Manager functionality thoroughly. Make sure to also check any custom adaptations that may use functions in the modules that have been removed.

To remove a module

  1. Terminate all web applications using the Internet Information Services (IIS) Manager.

  2. Close all One Identity Manager tools except for Job Queue Info.

  3. Wait until all processes have terminated. You can do this using the Job Queue Info.

  4. Close all One Identity Manager Services via the services manager.

  5. Terminate all application servers using the IIS Manager.

  6. Wait until all DBQueue Processor tasks have completed. You can do this using the Job Queue Info.

  7. Close Job Queue Info.

  8. Start a suitable program for executing SQL queries.

    IMPORTANT:

    • Select a user, who has at least administrative permissions for the One Identity Manager database, to execute SQL queries. For more information, see Permissions for the One Identity Manager database.

    • Execute the following steps separately using a suitable program for executing SQL queries.

      Test the output of the query after each step. The output provides additional advice about removing a module.

    1. Activate single-user mode for the One Identity Manager database.

      exec dbo.QBM_PSingleUserRequest @@spid

    2. Stop the DBQueue Processor components.

      exec QBM_PWatchDogPrepare 1

      go

      exec QBM_PDBQueuePrepare 1

      go

    3. Delete all triggers in the database.

      exec QBM_PTriggerDrop '%', @force = 1

    4. Delete all constraints in the database.

      exec QBM_PConstraintFKDrop '%','%','%'

    5. Delete the module you no longer need.

      exec QBM_PModuleRemove '<3-character module abbreviation>'

      Example:

      declare @ModulesToRemove varchar(100) = 'SAP' + char(7)

      + 'SHR' + char(7)

      + 'SBW' + char(7)

      + 'SAC' + char(7)

      exec QBM_PModuleRemove @ModulesToRemove

      go

    6. If you delete the Business Roles Module (RMB), you must also delete the entries in the table OrgRoot.

      exec QBM_PDeleteDeep '<Key><T>OrgRoot</T><P>3031e9af-6a53-4876-bbfb-0f7fbf264131</P></Key>

  9. End single-user mode for the One Identity Manager database.

    exec dbo.QBM_PSingleUserRelease @@spid

  10. Update the One Identity Manager schema with the Configuration Wizard. Select all remaining modules for updating.

  11. If support sent you hotfixes for this version, then these hotfixes must also be reinstalled.

  12. Start the application server, the One Identity Manager Services and the web applications.

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 is usually started after the indexing interval period specified by the configuration parameter Common | Indexing | Interval has elapsed.

If a table being indexed contains more objects to be indexed than the maximum specified by configuration parameter Common | Indexing | BatchSize, 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 3 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, e.g.,

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.

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

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. 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 onCompilation. Click Next after compilation is complete.
    11. Click Finish on the last page to end the program.
  6. Adjust the database staging level of the database in the Designer.
    1. Select the category Base Data | General | Databases in the Designer.

    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

Appendix: Extended 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.

    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
Related Documents