Chat now with support
Chat with Support

Identity Manager 8.1.5 - Operational Guide

About this guide Simulating data changes in the Manager Scheduling operations activation times Re-applying templates Exporting data with Manager Analyzing data and data changes Analyzing process monitoring in the Manager Schedules in One Identity Manager Mail templates in One Identity Manager Password policies in One Identity Manager Working with change labels Checking data consistency Compiling a One Identity Manager database Transporting custom changes Importing data with Data Import Importing and exporting individual files for the software update Command line programs

Creating a transport package with the Database Transporter

To create a transport package

  1. Start the Launchpad and log in to the One Identity Manager database.

  2. In the Change & Extend view, select the Transport custom modifications entry. This starts the Database Transporter program.
  3. Select Create a transport file on the start page.
  4. On the Select the database connection page, check the One Identity Manager database connection data and change it if necessary.
  5. Enter the information about the transport file on the Define file name page.
    1. Enter the name of the transport file and change the output directory as required.
    2. To create a log file for the export, enable the Create a log file for data export option.

      The log file is saved in the output directory of the transport file.

  6. Enter a description of the transport data on the Show and define transport parameters page.
  7. Select the export criteria on the Define transport data page.

    Note: You can combine multiple export criteria.

    Table 42: Export criteria
    Export criterion Description

    Run SQL statements before the data import

    You can integrate SQL statements in the custom configuration package, which are to be run before a data import.

    For more information, see Integrating SQL statements in a transport package.

    Transport of favorite objects

    In an initial selection, all modified processes, scripts, reports, and mail templates for a specific timeframe are offered.

    For more information, see Exporting favorite objects.

    Transport by change label

    Transport the changes to objects or object attributes that are summarized in a change label.

    For more information, see Exporting change labels.

    Transport by change information

    Limit the transportation data by user, timeframe, and database tables.

    For more information, see Exporting changes based on change information.

    Transporting schema extensions

    Transport custom schema extensions, such as tables, columns, database procedures, features, triggers, views, and indexes.

    For more information, see Transporting schema extensions.

    Transporting selected objects and their dependencies

    Select single objects and their dependencies for transport.

    For more information, see Exporting selected objects and dependencies.

    Transporting system configuration

    Transport the entire system configuration.

    For more information, see Transporting the system configuration and Notes about importing the system configuration.

    Transporting system files

    Transport single files.

    For more information, see Exporting system files.

    Transport of synchronization projects

    Select the synchronization project for transporting.

    For more detailed information, see the One Identity Manager Target System Synchronization Reference Guide.

    Run SQL statements after the data import

    You can integrate SQL statements in the custom configuration package, which are to be run after a data import.

    For more information, see Integrating SQL statements in a transport package.

  8. To start the export, click Next.

    The program determines the data to export and displays the progress of the export in the dialog box. The export procedure can take some time.

  9. To end the program, click Finish on the last page.
Related topics

Integrating SQL statements in a transport package

You can integrate SQL statements in the custom configuration package. The SQL statements are run before or after a data import. For example, after a schema extension has been transported a SQL statement may be required for filling initial data in the new columns.

NOTE: To create transport packages with SQL statements, the user needs the Enables integration of SQL statements in a transport file (Transport_SQL) program function.

To run SQL statements within a transport package

  1. In the Database Transporter, on the Define transport data page, select the export criteria for executing SQL expressions. The following export criteria are available:
    • Run SQL statements before data import
    • Run SQL statements after the data import
  2. Create the SQL statement using the Edit button. Differentiate between SQL statements for system data transport and user data transport.
    1. Enter the SQL statements directly.

      - OR -

      Using the interface, load a .sql file containing the statements.

    2. Use the button to save to a file.
Related topics

Exporting favorite objects

Use this transport method to select the modified processes, scripts, reports, and mail templates from a specific timeframe.

To transport favorite objects

  1. In the Database Transporter, on the Define transport data page, select the Transport of favorite objects export criteria.
  2. Click Select to select the single objects for the transport.
    1. In the Object modified in last ... days input field, enter the timeframe for the object selection.

      All objects with a change date and user in the selected timeframe are displayed.

      TIP: To include other processes, scripts, reports, or mail templates in the transport package, use the Load all entry.

    2. Select the object you want and use to add it to the transport package.

      TIP: Use Shift + select or Ctrl + select to select multiple objects in the selection dialog.

      The Transport objects pane lists all selected objects and their dependencies.

Related topics

Exporting change labels

Several changes to objects or objects properties are grouped together under a change label and can be swapped between source database and target database in this way. When a custom configuration package is imported with change labels, new data records are added to the target database and existing data records are updated. In addition, objects marked for deletion in the change label are deleted from the target database.

NOTE: There are no change labels available after initial schema installation.

To transport by change label

  1. In the Database Transporter, on the Define transport data page, select the Transport by change information export criteria.
  2. Select the change label from the menu.
  3. (Optional) To display the contents of a change label, click Display.

    Objects and changes are displayed, which belong to the change label.

    NOTE: If a change label still contains references to objects that no longer exist in the database, remove the assignment using the Repair button.

  4. (Optional) For additional settings for change label transport, click Options and specify the following options.

    Table 43: Additional transport settings
    Setting Description
    Close change label after export The change label is closed after the transport. No more changes can be booked to this change label.
    Copy dependent objects to the transport package Objects that are dependent on the selected object and do not have a change label are also copied to the transport.
    Also display closed change labels Change labels that are already closed are also offered for selection.
Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating