サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.1.3 - Operational Guide

About this guide Simulating data changes in the Manager Scheduling operations activation times Re-applying templates Exporting data with the 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 the Data Import Importing and exporting individual files for the software update Creating a One Identity Manager database for test or development from a database backup Initializing DBQueue Processor the after extending the server hardware Command line programs

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 38: Additional transport settings
    Setting Description

    Close change label after export

    The change label is completed and locked after 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

Exporting changes based on change information

Use the Transport by change information transport method to limit transportation data by user, time period and database tables.

To transport by change information

  1. In the Database Transporter, on the Define transport data page, select the Transport by change information export criteria.

  2. Specify which changes you want to transport.

    Table 39: User list
    Entry Description

    me

    Only the changes by the logged-in user are added.

    all users

    Changes are added from all users.

    selected users

    Changes are added from selected users.

    TIP: The User area displays the system users. The ... button beside the input field allows you to select other users. Use Shift + select or Ctrl + select to select multiple users in the selection dialog.

  3. Use the date filter to export changes for the selected user(s) from a specified date. The entries today, yesterday, day before yesterday, this week and last database migration and time period are available.

  4. You can limit transportation data even further by selecting database tables.
  5. Table 40: Table selection
    Entry Description

    Entire system

    Changes are added from all tables.

    System data

    Changes are added from the tables of the system data part.

    User data

    Changes are added from the tables of the user data part.

    Selected tables

    Changes are added from specific tables.

    TIP: To display objects that match the specified export criteria, click Display. In this overview, you can exclude individual objects from the transport To do this, disable the corresponding objects.

Related topics

Transporting schema extensions

Custom schema extensions, like tables, columns, database procedures, functions, triggers, views, and indexes that you want to add, must distinguished by a custom prefix CCC_. Furthermore, only custom database procedures, functions, triggers, views, and indexes that are not encoded and are smaller than 64 kb are included.

Custom database procedures, functions, triggers, and views are always exported in their entirety. Entries corresponding to custom tables and columns are generated in the One Identity Manager schema when the transport package is imported (tables DialogTable, DialogColumn, QBMRelation).

To transport all schema extensions completely from a test database to a productive database, the following procedure is recommended:

  1. Create a transport of schema extensions in the test database and import these into the production database.

  2. Create a transport of the system configuration in the test database and import these into the production database.

Use the transport options to transport single customizations by change label, change information or selected objects.

To transport schema extensions

  • In the Database Transporter, on the Define transport data page, select the Transport of schema extensions export criteria.

NOTE: Use Show to display the schema extensions.

Related topics

Exporting selected objects and dependencies

Use the Transport selected objects and dependencies transport method to select individual objects and their dependencies to transport. You can add objects dependent on the object you want to transport without having to select them individually.

NOTE: The selection for this transport criterion displays all tables not labeled with the No DB Transport option. If objects of other tables are to be transportable, then disable the option for the tables in the Designer. For more information about customizing table definitions, see the One Identity Manager Configuration Guide.

To transport single objects and their dependencies

  1. In the Database Transporter, on the Define transport data page, select the Transport of selected objects and dependencies export criteria.

  2. Click the Select button to select the single objects for the transport.

    1. In the Tables pane, select the database table from which you want to copy objects to the custom configuration package.

    2. The Relations pane displays the ChildRelation (CR), ForeignKey (FK) and many-to-many relations for the selected database table. Enable the required relations to copy the connected objects to the transport.

    3. The Objects pane displays all the objects of the selected table. Select the objects you want and add them to the transport.

      • To delete superfluous objects when the transport package is imported, select .

      • If you do not want to perform post-processing when the transport package is imported, select .

      TIP:

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

      • You can use to create a filter to limit the selection.

    4. The Objects to transport pane lists all selected objects and their dependencies.

      TIP: To remove individual object from the transport, select Remove.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択