The One Identity Manager schema is customized by loading so-called ‘transport packages’. One Identity Manager recognizes the following types of transport packages that can be copied to the database depending on requirements.
Transport Package Type | Description | Tool Used | ||
---|---|---|---|---|
Migration package |
Migration packages are provided by for the initial database schema installation, for service pack and complete version updates. A migration package contains all the necessary tables, data types, database procedures, and the default One Identity Manager configuration. |
Configuration Wizard | ||
Hotfix package |
Hotfix packages are provided to load individual corrections to the default configuration such as templates, scripts, processes, or files into the database.
|
Database Transporter Software Loader | ||
Custom configuration package |
A custom configuration package is used to exchange customer specific changes between the development, test and productive system database. This transport package is created by the customer and loaded into the database. |
Database Transporter |
|
NOTE: If more custom configuration adjustments are made to a One Identity Manager database, then create a custom configuration package and import this transport package in the target database with the Database Transporter. There is no support for merging a hotfix package with a custom configuration package into one transport package. |
Different methods are implemented for transporting modifications.
Transport of single objects is done through the object layer.
When you import a transport package, the permissions, templates and customizer in the target database are taken into account.
This method is used, for example, if you use the Database Transporter program to create and import custom configuration packages that contain modifications to a system user, modifications starting from a defined date or to individual objects.
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.
This method is used if you use the Database Transporter program to create and import custom configuration packages that contain the complete system configuration. This method is also used to install and update the One Identity Manager schema using the Configuration Wizard.
When a transport package is imported into a One Identity Manager database, the following operations are carried out:
No object was found in the destination database using the primary key or alternative key, therefore a new object is created with this key value.
An object found in the target database using the primary key will be updated. The update is done using the configuration buffer.
If transporting modifies a default configuration, the default configuration is moved into the configuration buffer. You can retrieve changes from the configuration buffer and restore the default configuration in this way.
If, during a One Identity Manager version upgrade, the default configuration is changed by a service pack, a complete version upgrade or by loading a hotfix package, a check is made to see if it has already been customized. In this case, the modified default configuration is copied to the configuration buffer. This ensures that customizations do not go missing.
Objects that are no longer needed are deleted. This operation is always executed if the entire system configuration is transported.
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.
You can display the contents of a transport package with the Database Transporter before you import.
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.
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.
Before importing a transport package, you can protect individual properties from being overwritten in the target database.
For example, you might want to block processing:
To unlock and unlock a single property
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy