Identity Manager 8.0 - Configuration Guide

Transport by Change Information

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

To transport by change information

1. Select the export criteria Transport by change information.
2. Specify which changes you want to transport.

   Table 321: User Selection

   Entry	Description
   me	Only your changes are added.
   all users	Changes are added from all users.
   selected users	Changes are added from selected users. A selection list of system users is displayed from which you can make a selection in the case of specified users. You can also specify additional users directly in an input field or by using a selection dialog, which you open with .... TIP: You can select multiple objects with the SHIFT+ SELECT or CRTL + SELECT.

3. Use the date filter to export changes for the selected user(s) from a specified date.

   To specify the date, you can can select "today", "yesterday", "day before yesterday", "this week" and "Last database migration" from the quick select menu. However, you can also choose another time period for the transport. To do this, select "period" and enter the time period in the "From:" and "To:" positions.

4. You can limit transportation data even further by selecting database tables.

   Table 322: Table Selection

   Entry	Description
   whole system	Changes are added from all tables.
   system data	Changes to system components in the tables are added.
   user data	Changes to user data components in the tables are added.
   selected tables	Changes are added from specific tables.

5. To display objects that fulfill the specified export criteria, click Show.

   TIP: You can exclude individual objects from the transport at this point. To do this, disable the corresponding objects.

Related Topics

• Creating a Transport Package with the Database Transporter

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. This customer prefix must be given for the main database. 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).

The following procedure is recommended to transport all schema extensions in their entirety, from a test database into a production database

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

• Select the export criteria Transport schema extensions.

Related Topics

• Creating a Transport Package with the Database Transporter
• Managing Custom Database Objects within a Database

Transporting Selected Objects and their Dependencies

Select single objects and their dependencies for transport. You can add objects dependent on the object you want to transport without having to select them individually.

To transport single objects and their dependencies

1. Select the export criteria Transport selected objects and their dependencies.
2. Use the Select button to open a selection dialog box where you select the objects you want to transport.
3. To select the objects, select the database table in the "Tables" list that you want to take the objects from that will be added to the custom configuration package.

   NOTE: All tables that are not labeled with the option No DB transport are in the list. If object from other tables should also be transported, disable this option in the program "Designer".

4. ChildRelation (CR), ForeignKey (FK) and many-to-many relations for the selected database table are displayed in "Relations".

   • Enable the relations you want. The objects linked through these relations are added to the transport when an object is selected.
5. All the objects in the selected table are shown in the "Object" list. You can limit the selection with a search filter. Select the objects you want and add them to the transport.

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

   Table 323: Functionality of the Object Selection Icons

   Icon	Meaning
   	Selected objects and dependencies are added to the transport. There is no post-processing after data import.
   	Selected objects and dependencies are added to the transport. Redundant objects are deleted after data import.
   	You can define a search filter. The search filter displays all matching objects.

6. All the objects you have selected and their dependencies are listed under "Transport objects".

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

Related Topics

• Creating a Transport Package with the Database Transporter
• Mapping Table Definitions

Transporting System Configuration

To transport the system configuration

• Select the export criteria Transport system configuration.

The transport of the entire system configuration is done through a transfer buffer. All relevant tables are checked when creating the transport package. The condition applied to the table, defines which objects are transported. The primary key is used to establish whether the transport entry has a GUID module and whether it is transferred to the source database transfer buffer. The transfer buffer is read and transport package is created. When importing into the target database, the contents of the transport package is transferred to the target database's transfer buffer. The information is then transferred to the target tables. Creating and importing this transport is very time consuming.

When a full custom configuration package is imported, new objects are added to the destination database and existing objects are updated. In addition, redundant objects are deleted from the target database.

Related Topics

• Creating a Transport Package with the Database Transporter

• Advice on Importing the Entire System Configuration