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:
-
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.
Use the transport options to transport single customizations by change label, change information or selected objects.
To transport schema extensions
NOTE: Use Show to display the schema extensions.
Related topics
Use this transport method to select single objects and their dependencies for the 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
-
In the Database Transporter, on the Define transport data page, select the Transport of selected objects and dependencies export criteria.
-
Click the Select button to select the single objects for the transport.
-
In the Tables pane, select the database table from which you want to copy objects to the custom configuration package.
-
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.
-
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 
.
-
The Objects to transport pane lists all selected objects and their dependencies.
TIP: To remove individual object from the transport, select Remove.
Related topics
Use this transport method to transport individual files by exporting them from the database.
To transport new or modified One Identity Manager files
-
In the Database Transporter, on the Define transport data page, select the Transport system files export criteria.
-
Click Select and specify the files to transport.
Related topics
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
to create a filter to limit the selection.