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
The log file is saved in the output directory of the transport file.
|
NOTE: You can combine several 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. |
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.
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.
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
- OR -
This method of transport shows modified processes, scripts, reports and mail templates during a specific time period.
To transport favorite objects
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.
|
TIP: You can select multiple objects with the SHIFT+ CLICK or CRTL + CLICK. |
Icon | Meaning |
---|---|
Selected objects and dependencies are added to the transport. | |
Selected objects and dependencies are removed from the transport. |
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:
|
|
NOTE: There are no change labels available after initial schema installation. |
To transport by change label
|
TIP: You can group together several change labels in one custom configuration package. To add other change labels, use the |
Objects and changes are displayed, which belong to the change label.
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. |
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy