You should only use a transport of the system configuration if you want to copy all the adjustments to a test database into an initial productive database.
To transport custom database procedures, features, triggers, or views completely from a test database to a productive database in addition to the system configuration:
- Create a transport of schema extensions in the test database and import these into the production database.
-
Create a transport of the system configuration in the test database and import these into the production database.
To transport individual configuration data units to an existing productive database, use transports based on change labels, change information or selected objects.
Importing a transport of the system configuration overwrites the configuration data of the target database. This also applies to the configuration parameter settings. Before importing a transport package, you can protect individual properties from being overwritten. After importing the system configuration into a target database, you should check and, if necessary, modify the configuration settings.
Detailed information about this topic
You should only use a transport of the system configuration if you want to copy all the adjustments to a test database into an initial productive database.
To create a transport for the system configuration
- In the Database Transporter, on the Define transport data page, select the Transport by change information export criteria.
Related topics
When importing a transport of the system configuration into a target database, you must follow the instructions described under General notes about transporting changes and consider the following special features:
Related topics
IMPORTANT: Test changes in a test system before you load a transport package in a productive system.
To import 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. This starts the Database Transporter program.
- Select Import 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.
-
Select the transport package file browser and click Open.
-
Specify your import options on Select transport file.
Table 46: Import options
|
Create a log file for the data import |
Enable this option to create a log file for the import. The log file is saved in the output directory of the transport file. |
|
Import objects singly and ignore errors |
Enable this option to import options individually. Errors, which might occur during importing are ignored and displayed when importing is complete. If you do not enable this option, the import procedure is canceled when errors occur. |
|
Ignore default data differences |
Enable this option to ignore changes to default data during the import. If you do not enable this option, the import procedure is canceled if changes to default data are included. |
-
Import steps and import progress are displayed on the Importing transport data page. The import procedure can take some time. Calculation tasks are queued for the DBQueue Processor on termination.
NOTE: During import, if the expected value does not match with the actual value in the database, the Merge conflict dialog opens. For each conflict, you must decide which value is committed to the database.
-
If you want to keep database value, enable Current database value.
-
If you want the value from the transport package to overwrite the database value, enable Transport value.
- If changes have been made to the system configuration, for example, processes, or scripts imported, you have to compile the database after the tasks have been processed. Compilation is started automatically once importing is complete.
- To end the program, click Finish on the last page.
NOTE: Use the 
button to save any errors that occur whilst importing.
Related topics
