IMPORTANT: Test changes in a test system before you install a hotfix in a productive system.
Hotfix packages contain:
- Transport packages that contain changes to the default configuration, such as templates, scripts, or processes in the One Identity Manager database
- Modified files, such as *.exe, *.dll or *.vif
If you receive a transport package using a hotfix package, use the Database Transporter program to update the One Identity Manager database.
If a hotfix contains a modified file, copy the file to the install directory of the test computer for testing. To distribute the files to all workstations and servers using the automatic software automation, use the program Software Loader to import the files into the One Identity Manager database.
NOTE: If, in additional to a hotfix package, there are additional customized configuration settings to be installed in a One Identity Manager database, create a custom configuration package and use the Database Transporter to import it into the target database. There is no support for merging a hotfix package with a custom configuration package into one transport package.
Detailed information about this topic
You can display the contents of a transport package with the Database Transporter before you import.
NOTE: Always start the Database Transporter on an administrative workstation.
To display the contents of 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 Show transport file.
- Select the transport package file browser and click Open.
- Click Next on the Select transport file page.
- The contents of the transport file are displayed on the Show transport file page.
- To display the sequence in which the objects are imported:
- Click + to select an entry in the transport file and select Sort in import order from the context menu.
- Click OK and enter the connection credentials for the database. This step is only required when you established the first in the order.
The order in which the entry's objects are imported into the database is found.
- Repeat this step for all other entries for which you want to determine the import order.
-
To display the objects required for an import in the target environment, select the entry for the .xml file and select Show required objects from the context menu.
Objects that are dependent on another object that is not part of the transport package are highlighted.
-
To end the program, click Finish on the last page.
TIP: You can start the import of the transport package from display mode. On the Show transport file page, click the name of the transport package and use the Import context menu.
Related topics
NOTE:
-
Test the changes in a test environment before you load a transport package in a production system. Use a copy of the production database for testing.
-
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.
- When you import a transport package with the Database Transporter, the import date and description, the database version, and the transport package name are recorded in the transport history of the target database.
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 29: 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
NOTE:
-
Start Software Loader on an administrative workstation.
-
When selecting the base directory, ensure that a directory hierarchy is not created unintentionally.
-
For web applications, select the installation directory of the web application to ensure that the required subdirectories, for example the bin directory, are detected correctly.
-
For detailed information about how to import customer-defined files using the Software Loader, see the One Identity Manager Operational Guide.
To import files into a One Identity Manager database
-
Start the Launchpad and log in to the One Identity Manager database.
- In the Change & Extend view, select the Import files for software update entry. This starts the Software Loader program.
- Select Import into database on the start page.
- On the Connect to database page, check the One Identity Manager database connection data and change if necessary.
- Specify the file to be imported on Select files.
- Select the base directory where the files can be found.
The status and file size of all the files in the selected directory are displayed in the file list.
Table 30: Meaning of status
| Version unknown |
The file belongs to the known files but has not yet been loaded into the database. There is no version information in the database. |
| Unknown file |
The file is new. The file is in the list of known files but has not been loaded in the database yet. There is no version information in the database. |
| Version OK |
The file version matches the version in the database. |
| Version modified |
The file version has been modified compared with the version in the database. |
- Select the files you want to load into the One Identity Manager database.
TIP:
- Click a column in the table header to order the display by the selected column.
- Press Shift + select or Ctrl + select to select more than one file.
- To quickly select all files with Changed version as their status, select Open all directories and Open all modified files in the context menu. Files in subdirectories are only selected if the higher-level directories have already been opened.
- On the Select change label page, assign a change label to make it easier to exchange files between various databases, such as the test database, development database and productive database.
- Select Assign files to following change label.
- Use the button next to the option to select the change label.
-
The files are loaded straight from the One Identity Manager database.
- Specify other file settings on Assign machine roles.
- Assign a computer role to the files.
- (Optional) For more file settings, click ... next to the file names.
Table 31: More file settings
| Directory source |
Directory path in installation source. |
| Create backup |
A copy must be made of the file during the automatic software update. |
| No update |
The file is not updated by the automatic software update. |
- Click Finish on the last page to end the program.
Related topics
