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

Creating a Transport Package with the Database Transporter

Creating a Transport Package with the Database Transporter

Create a custom configuration package, which you import into the target database, in order to exchange customizations between the development database, test database and the production database.

You can specify restricting export criterion for creating custom configuration packages. System user modifications, modifications as from a defined date, or individual objects can be exported. A limited custom configuration package is recommended for transporting individual changes from a development database to a test database. However, you should create a transport of the entire system configuration package to transfer changes from the test database to the productive database.

NOTE: The current user must be entitled to use the program function "Allows transport packages to be imported into the database." in order to import a transport package with the Database Transporter. (Transport_Import).

To create a transport package

  1. Start the Launchpad and select Transport custom modifications. This starts the program "Database Transporter".
  2. Select Create a transport file on the start page.
  3. Enter the connection credentials for the One Identity Manager database on the Select the database connection page.
  4. 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 an export log file, set the option Create a log file for data export.

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

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

    NOTE: You can combine several export criteria.

    Table 318: Export Criteria
    Export Criteria Description
    Run SQL statements before data import You can integrate SQL statements into the custom configuration package, which are executed before the data is imported.
    Transport of favorite objects All modified processes, scripts, report and mail templates from a specific time period are available for preselection.
    Transport by change label Transport modifications to objects or object properties, which are grouped under a change label.
    Transport by change information Limit transportation data by user, time period and database tables.
    Transporting Schema Extensions Transport custom schema extensions, like tables, columns, database procedures, functions, triggers, views and indexes.
    "Transport selected objects and their dependencies Select single objects and their dependencies for transporting.
    System Configuration Transport Transport the complete system configuration.
    Transports system files Transport single files. These files are distributed with the automatic software update.
    Run SQL statements after data import You can integrate SQL statements into the custom configuration package, which are executed after the data is imported.
  7. Click Next to start exporting.

    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.

  8. Click Finish on the last page to end the program.

The export date, the export description, database revision and the name of the export file in the source database transport history are recorded when a transport package is created with the Database Transporter.

Detailed information about this topic
Related Topics

Transporting SQL Statements

You have the option to integrate SQL statements into the custom configuration package. These SQL statements are run either before or after the is data imported. For example, after a schema extension has been transported an SQL statement may be required for filling initial data in the new columns.

NOTE: To create transport packages, the current user must have permissions for the program function "Enables integration of SQL statements in a transport file. (Transport_SQL)".

To run SQL statements within a transport package

  1. Select the export criteria for running SQL statements. The following export criteria are available:
    • Run SQL statements before data import
    • Run SQL statements after data import
  2. Create the SQL statement using the Edit button. Differentiate between SQL statements for system data transport and user data transport.
    • Enter the SQL statements directly.

      - OR -

    • Load a *,sql file with the button.
    • Save them with the button.
Related Topics

Transporting Favorite Objects

This method of transport shows modified processes, scripts, reports and mail templates during a specific time period.

To transport favorite objects

  1. Select the export criteria Transport of favorite objects.
  2. Use the Select button to open a selection dialog box where you select the objects you want to transport.
  3. Enter the time period for the object selection in the input field Object changed in last ... days. All the objects are displayed with the change date and user.

    If you also want to add processes, scripts, reports or mail templates to the other objects in the display, use the "Load all.." option to load them.

  4. Select the objects you want and add them to the transport. All the objects you have selected and their dependencies are listed under "Transport objects".

    TIP: You can select multiple objects with the SHIFT+ CLICK or CRTL + CLICK.

    Table 319: Functionality of the Object Selection Icons
    Icon Meaning
    Selected objects and dependencies are added to the transport.
    Selected objects and dependencies are removed from the transport.
Related Topics

Transport by Change Label

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, data records that are marked for deletion in the change labels are deleted from the database.

NOTE: Use a change label to mark changes to single objects properties as well as entire objects.

Note the following:

  • If an object property is modified through a transport, you must ensure that the object to modify is present in the target database. In certain circumstances, the object must be added to the change label.
  • If the entire object is labeled with a change label, the object is added to the custom transport package with the object properties valid at the time of export.

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

To transport by change label

  1. Select the export criteria Transport by change label.
  2. Select a change label in the list.

    TIP: You can group together several change labels in one custom configuration package. To add other change labels, use the button.

  3. To display the contents of a change label, click Show.

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

    • If there are still references in the change label to objects that do not exist anymore in the database, remove the assignment with Repair.
  4. Click Options for additional setting for transporting changes labels.
    Table 320: Additional Transport Settings
    Option Description
    Close change label after export This closes the change label after the transport has completed. No more changes can be booked to this change label.
    Add dependent objects to transport file Objects that are dependent on the selected objects and are not marked with a change label are also added to the transport.
    Show with closed change labels Change labels, which are already closed, are also available for selection.
Related Topics
Related Documents