To exchange customizations between the development database, test database and the productive database, use the Database Transporter to create transport packages. You also use the Database Transporter to import the transport packages into the target database.
Tips for creating transport packages
-
To copy individual objects into a transport package, specify the export criteria in Database Transporter. For example, you can export all changes made by a system user, changes made starting from a defined date or change labels. We recommend that you limit the custom configuration package if you are transporting individual changes.
-
You should only create a transport for the full system configuration if you want to copy all the adjustments to the system configuration from a test database into an initial productive database.
-
To import transport packages with the Database Transporter, the user needs the program function Allows transport packages to be imported into the database (Transport_Import).
-
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.
Tips for importing transport packages
-
You can display the contents of a transport package with the Database Transporter before you import.
-
Before importing a transport package, you can protect individual properties from being overwritten in the target database.
-
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.
-
Depending on the type of transport, 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 importing a transport of the system configuration into a target database, you must also follow the Tips for importing the system configuration.
-
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.
Related topics
Before importing a transport package, you can protect individual properties from being overwritten in the target database.
For example, you may want to block processing, as follows:
-
Configuration parameters and their values should not be overwritten when a test environment is transported to a productive system.
-
Server configurations should neither be overwritten in the test environment nor the productive system during a transport.
To unlock and unlock a single property
-
Open the object in the Designer or the Manager.
-
Click the property name and select one of the following options from the context menu:
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.
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 display transport history
You create transport packages to exchange customer-specific changes between the development, test, and productive system databases.
To create a transport package
-
Start the Launchpad and log in to the One Identity Manager database.
-
In the Change & Extend view, select the Transport custom modifications entry and click Start.
This starts the Database Transporter program.
-
Select Create a transport file on the start page.
-
On the Select the database connection page, check the One Identity Manager database connection data and change it if necessary.
-
Enter the information about the transport file on the Define file name page.
-
Enter the name of the transport file and change the output directory as required.
-
(Optional) To create a log file for the export, set the Create a log file for data export option.
The log file is saved in the output directory of the transport file.
-
Enter a description of the transport data on the Show and define transport parameters page.
-
Select the export criteria for the transport on the Define transport data page.
NOTE: You can combine multiple export criteria.
Table 37: Export criteria
|
Run SQL statements before 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 transport packages. |
|
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. |
|
Transport schema extensions |
Transport custom schema extensions, such as tables, columns, database procedures, functions, 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. |
|
Transport system configuration |
Transport the entire system configuration.
For more information, see Transporting the system configuration and Tips for importing the system configuration. |
|
Transport system files |
Transport single files.
For more information, see Exporting system files. |
|
Transport synchronization projects |
Select the synchronization project for transporting.
For more 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 transport packages. |
|
Use a transport template for selection |
Select a transport template for the transport. The export criteria are determined from the transport template.
For more information, see Using transport templates. |
-
To start the export, click Next.
This create the transport package. 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.
-
On the last page, the name and storage path for the transport package are displayed. You can open the directory path using the link.
-
To end the program, click Finish on the last page.
Related topics
