NOTE: Always start the Software Loader on an administrative workstation!
To import files
The status and file size of all the files in the selected directory are displayed in the file list. The status is determined from the file information in the database. To test the file version, the file size and the hash value are determined and compared to the entry in the database.
NOTE: Take note when selecting the base directory that a directory tree is not created accidentally.
|Version unknown||The file belongs to the known files but has not been loaded into the database yet. There is no version information in the database.|
|File unknown||This 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 changed||This version of the file has change with respect to the version in the database.|
TIP: Click with the mouse in a column header to sort by the selected column.
TIP: Modified files can be preselected in the context menu.
|Context Menu Item||Meaning|
|Open all directories All the directories are opened.|
|Open all modified files||All the files with the status "Version changed" are selected. Files in the subdirectories are only selected if the directories are opened beforehand.|
Issue a change label to mark files in order to simplify the transfer of new files between various databases (test database, development database, operational database). Change labels are offered in the program "Database Transporter" as export criteria when a customer transport package is created.
|Source directory||Path in the installation source.|
|Create backup||A copy of the file is made if the software is updated automatically.|
|No update||The file is not updated automatic software update.|
Particularly local installation and updating of software can prove to be a problem due to the distributed structure of servers and workstations. To help guarantee an acceptable workload for network administrators, a method for updating One Identity Manager automatically has been developed for One Identity Manager. Apart from updating the usual One Identity Manager installation files, new custom files can be simply added to the procedure and are, therefore, distributed to workstations and servers in the One Identity Manager network using the automatic software updating mechanism.
All files in a One Identity Manager installation are saved with their name and binary code in the One Identity Manager database. The affiliation to machine roles and installation packages are entered for each file. In addition, the file size and hash values are stored in the database for each file in order to identify them.
The necessary files are loaded into the database and updated when a hotfix, a service pack or a full version update One Identity Manager is run.
A semaphore "Softwarerevision" is maintained in the database. When a file is added, changed or deleted in the database, the semaphore value is recalculated by the DBQueue Processor. In every One Identity Manager installation directory there is a file Softwarerevision.viv. This file contains the following information:
The revision number is determined by the semaphore value 'softwarerevision’ in the database.
In addition, you will find the file InstallState.config in the installation directory of all One Identity Manager installations. This file contains information about the installed machine roles, installation packages and files.
Whether a software update is required depends on the comparison of semaphore values from the database and the file. If semaphore values vary, machine roles for the computer or server are determined based on the InstallState.config. Each file belonging to a machine role is check to see if the file is known to the database.
If the file exists in the data, the following checks are made:
If this is the case, the file is added to the list of files to be updated.
If this is the case, the file is added to the list of files to be updated.
New files that have been loaded into the One Identity Manager database through a hotfix, a service pack or a version update are also added to the list. All the files in the list are updated. All actions are logged in the file update.log. After the update has finished, the current semaphore value is copied from the database to the file softwarerevision.viv.
When a program starts up, VI.DB.dll creates a connection to the database and carries out the semaphore test. If the file softwarerevision.viv is not found, a new file is added.
If the One Identity Manager installation directory does not have write access, an error message is displayed and the software update continues.
The update program (Updater.exe) expects a login by an administrator when user account control is active, assuming the logged in user does not have administration permissions for the installation directory (for example %ProgramFiles%). If installation takes place in a directory without user account control, the query does not apply. Then the update process is started.
To prevent further applications from starting during the update, a file called Update.lock is created in the installation directory. The trigger program and the update program (updater.exe) write their process ID’s in the file. The Update.lock file is deleted from the installation directory once updating has been successfully completed. The program is then restarted. To ensure that automatic updating is restarted when an application is restarted after quitting unexpectedly, Update.lock files older than two hours are ignored. If none of the processes whose ID’s are saved in the Update.lock file exist on the workstation when the application is restarted, the Update.lock file is also ignored and the update is restarted.
The semaphore test is carried out by VI.DB.dll on a cyclical basis during normal operations. If a file is identified for update, the update process is started automatically.
Once the automatic One Identity Manager tool update has been identified on a workstation, the user is prompted to close all open programs. Updating starts after the user has closed all the programs.
The configuration parameter "Common\AutoUpdate\AllowOutOfTimeApps" controls whether One Identity Manager tools users can decide when their workstation is updated.
If the user does not want to update immediately, he can continue working. The update is started the next time the program is started.
Automatic software updating is the default method for updating the One Identity Manager Service on servers. However, the update method takes into account that it may be essential to exclude certain servers from being updated automatically and to update them manually.
The One Identity Manager Service returns the actual state of the semaphore "SoftwareRevision" after each request following a process step. If this value differs from the value in the database, the Job server is labeled with "updating" in the database and no more normal process steps are sent to it.
A Job server update is executed depending on the method set in the configuration parameter "Common\Autoupdate\ServiceUpdateType".
First, the start time of the last change is determined from the file SoftwareRevision.viv. A list is compiled of all files with additional information specifying whether each file is new or not. This list is evaluated on the Job server to be updated and another list is compiled specifying which files will be updated. One Identity Manager Service is restarted if any one of the files has changed on the Job server. After the update is completed, the Job server label is reset in the database.
In principle, web applications support automatic software update. However, a few web applications may require extra configuration to take part in automatic software update.
NOTE: The following permissions are required for automatic updating:
Updating the web application requires restarting the application. The web application is restarted automatically by the web server when it has been idle for a defined length of time. This may take some time or be prevented if continuous user requests. Some web application offer you the option to restart manually.
If the web application update is identified, new files are copied from the database to a temporary directory on the server. The Updater.exe is started. It waits until the web application process is shutdown. Updater.exe copies the files from the temporary directories into the web application directory.
To implement automatic software updating
|Queue||A process for distributing files is queued in the Job queue.|
|DB||The files are loaded straight from the database. Implement this procedure if all Job servers have a direct connection to the database.|
|Auto||All root servers are filled straight from the database. A process is set up in the Job queue for all leaf servers. The root servers must have a direct database connection for this method.|