The TDI Update Installer is an installer included with updates to existing TDI installations; it is used whenever we need to perform maintenance in order to install fixes.
The regular installer lays down a file named .registry in the install directory that represents the current level of installed components. A script named tdiSetBackupDir.bat or tdiSetBackupDir.sh is created in the bin directory of the installation that sets the location of the backup directory; this will be a directory named BACKUP in the maintenance directory by default. We can change the backup location by running the tdiSetBackupDir script. So for example, if a fix is named "ifix1", backup files and directories would be under install dir/maintenance/BACKUP/ifix1 in this scenario. The update installer will harvest the name of the backup directory when performing maintenance. The user performing maintenance to TDI should have write permission for the install and backup directories. You should also be aware that during a complete uninstall, the uninstaller will attempt to delete the default backup directory.
The regular installer also handles maintenance of the .registry file during uninstalling and adding features. When performing a full uninstall, the .registry file will be deleted along with the other files. When performing a partial uninstall, only the components being uninstalled will be removed from the registry file, and when adding features, the .registry file will be updated to contain the newly installed features. After adding a feature, we should immediately install all of the fixes that are currently applied. Installing a fix that has previously been applied will only update the newly added features.
The update installer will be comprised of several Java files, but to avoid you having to specify the java executable, a wrapper script is created in the bin directory called applyUpdates.bat(sh). This script will use existing scripts to find the right Java JRE to use and call the underlying code. The script's usage is as follows:
applyUpdates -update fix_file.zip [-clean [-silent]] applyUpdates -rollback applyUpdates -queryreg applyUpdates -queryfix fix_file.zip applyUpdate -enroll license_file.zip applyUpdates -?
The options are as follows:
Example output:
Information from .registry file in: C:\Program Files\IBM\TDI\V7.1 Edition: Identity Level: 7.1.0.1 Fixes Applied =-=-=-=-=-=-= None Components Installed =-=-=-=-=-=-=-=-=-= BASE SERVER CE CE UPDATE JAVADOCS EXAMPLES IEHS EMBEDDED WEB PLATFORM AMC Deferred: false PLUGINS
Example output:
Information from fix file: C:\fixes\TDI-7.1s-TESTFP0001.zip Name: fixpack1 Minimum level required to apply fix: 7.1.0.0 Maximum level allowed to apply fix: 7.1.0.1 Prereq =-=-=- None Components Affected =-=-=-=-=-=-=-=-=-= BASE CE EXAMPLES
The zip file representing a fix (fix_file.zip in the examples above) will contain a manifest file named .manifest which contains information about applying the fix.