Chat now 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

Editing the One Identity Manager database during update with the Configuration Wizard

The One Identity Manager database is updated automatically by the Configuration Wizard. This procedure may take some time depending on the amount of data and system performance.

The Configuration Wizard performs the following steps:

  • Updating the One Identity Manager schema.

    Before the schema installation, the Configuration Wizard checks the database. Error messages are displayed in a separate window. The errors must be corrected manually. The schema update cannot be started until these are resolved.

    All the tables, data types, and database procedures that are required are loaded into the database by the schema update. When a transport package is imported into a One Identity Manager database, the following operations are carried out:

    Table 32: Operations when importing a migration package
    Operations Description
    Insert If the object is not found in the target database, a new object is generated with the key values.
    Refresh If the object is found in the target database, the object is updated.
    Delete Objects that are no longer needed are deleted.

    During a schema update, calculation tasks are queued in the database. These are processed by the DBQueue Processor.

    For a schema update with the Configuration Wizard, the migration date and the migration status are recorded in the transport history of the database.

  • Compiling the system.

    Scripts, templates and processes are declared in the database. The System user authentication module with the specified system user is used for compilation.

  • Uploading files for automatic software update.

    In order to distribute One Identity Manager files using the automatic software updating mechanism, the files are loaded into the One Identity Manager database.

  • Migration of synchronization projects,

    A process that migrates all existing synchronization project is queued in the Job queue. This updates the One Identity Manager schema and applies automatic patches.

Related Topics

Installing a hotfix in the One Identity Manager database

IMPORTANT: Test changes in a test system before you install a hotfix in a productive system.

Hotfix packages contain:

  • Transport packages which contain changes to the default configuration, such as templates, scripts, processes in the One Identity Manager database
  • Modified files, such as *.exe, *.dll or *.vif

If you receive a transport package using a hotfix package, use the Database Transporter program to update the One Identity Manager database.

If a hotfix contains a modified file, copy the file to the install directory of the test computer for testing. To distribute the files to all workstations and servers using the automatic software automation, use the program Software Loader to import the files into the One Identity Manager database.

NOTE: If more custom configuration adjustments are made to a One Identity Manager database, then create a custom configuration package and import this transport package in the target database with the Database Transporter. There is no support for merging a hotfix package with a custom configuration package into one transport package.

Detailed information about this topic

Displaying the contents of a transport package with the Database Transporter

You can display the contents of a transport package with the Database Transporter before you import.

NOTE: Always start the Database Transporter on an administrative workstation!

To display the contents of a transport package

  1. Open Launchpad. In Change & Extend, select Transport custom modifications. This starts the Database Transporter program.
  2. Select Show transport file.
  3. Select the transport package file browser and click Open.
  4. Click Next on the Select transport file page.
  5. The contents of the transport file are displayed on the Show transport file page.
    • To display the sequence in which the objects are imported
      1. Click + to select an entry in the transport file and select Sort in import order from the context menu.
      2. Click OK and enter the connection credentials for the database. This step is only required when you established the first in the order.

        The order in which the entry's objects are imported into the database is found.

      3. Repeat this step for all other entries for which you want to determine the import order.
    • To display the objects required for an import in the target environment, select the entry for the .xml file and select Show required objects from the context menu.

      Objects that are dependent on another object that is not part of the transport package are highlighted.

  6. To end the program, click Finish on the last page.

TIP: You can start the import of the transport package from display mode. On the Show transport file page, click the name of the transport package and use the Import context menu.

Related Topics

Importing a transport package with the Database Transporter

NOTE:

  • Test the changes in a test environment before you load a transport package in a production system. Use a copy of the production database for testing.

  • To import transport packages with Database Transporter, the user requires the Allows transport packages to be imported into the database (Transport_Import) program function.

  • Start Database Transporter on an administrative workstation.

  • The database is set to single-user mode for the duration of the import. Close all existing connections to the database before starting the import.

  • When you import a transport package with schema extensions, the database is set to maintenance mode. Objects cannot be processed in the database during this time.

  • When you import a transport package with the Database Transporter, the import date and description, the database version, and the transport package name are recorded in the transport history of the target database.

To import a transport package

  1. Open Launchpad. In Change & Extend, select Transport custom modifications. This starts the Database Transporter program.
  2. Select Import transport file on the start page.
  3. On the Select database connection page, enter the connection credentials for the One Identity Manager database into which you want to import the transport package.
  4. Select the transport package file browser and click Open.

  5. Specify your import options on Select transport file.

    Table 33: Import options

    Setting

    Description

    Create a log file for the data import

    Enable this option to create a log file for the import. The log file is saved in the output directory of the transport file.

    Import objects singly and ignore errors

    Enable this option to import options individually. Errors, which might occur during importing are ignored and displayed when importing is complete. If you do not enable this option, the import procedure is canceled when errors occur.

    Ignore default data differences

    Enable this option to ignore changes to default data during the import. If you do not enable this option, the import procedure is canceled if changes to default data are included.

  6. Import steps and import progress are displayed on the Importing transport data page. The import procedure can take some time. Calculation tasks are queued for the DBQueue Processor on termination.
  7. If changes have been made to the system configuration, for example, processes or scripts imported, you have to compile the database after the tasks have been processed. Compilation is started automatically once importing is complete.
  8. To end the program, click Finish on the last page.

    NOTE: Use the button to save any errors that occur whilst importing.

Related Topics
相关文档