Use transport by change information to limit transportation data by user, time period and database tables.
To transport by change information
Entry | Description | ||
---|---|---|---|
me | Only your changes are added. | ||
all users | Changes are added from all users. | ||
selected users |
Changes are added from selected users.
|
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.
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. |
|
TIP: You can exclude individual objects from the transport at this point. To do this, disable the corresponding objects. |
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
Use the transport options to transport single customizations by change label, change information or selected objects .
to transport schema extensions
|
NOTE: Use the Show button to display the schema extensions. |
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
|
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". |
ChildRelation (CR), ForeignKey (FK) and many-to-many relations for the selected database table are displayed in "Relations".
|
TIP: You can select multiple objects with the SHIFT+ CLICK or CRTL + CLICK. |
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. |
|
TIP: To remove individual object from the transport, select Remove. |
|
NOTE: You should only use a full custom configuration package to transfer all customizations from the test database into an initial production database. Use change labels to change information or selected objects to transport configuration data into an existing live database. |
|
CAUTION: This procedure overwrites the entire configuration data in the target database! This also applies to the configuration parameter settings. You can prevent individual properties from being overwritten. |
To transport the 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.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy