Use the tdimiggbl tool located in the TDI_install_dir/bin directory to migrate any global.properties file starting with TDI 6.x to 7.1. The filename is tdimiggbl.bat on Windows and tdimiggbl.sh on UNIX/LINUX. Use the tdimiggbl-4log4j.properties file to control logging for tdimggbl.bat(sh).
The usage if the command is as follows:
tdimiggbl -f propfile [-b backfile] [-n newfile] [-v] [-?]
where:
-f propfile - The name of the file to migrate
-b backfile - Backup the original file with the specified name
-n newfile - Name to give the file that is migrated
-s dir - Working directory where the solution directory is located.
-v - Enable verbose mode
-? - Prints the usage statement
During the installation of TDI, the installer backs up the existing global.properties file; and then calls this command, in order to migrate the global.properties.
The migration tool tries to migrate a global.properties file (or solution.properties file if required) up to the latest TDI version. The tool (tdimiggbl) makes no assumptions about which release the global.properties files starts from and can handle global.properties files starting at TDI version 6.0. The tool also tries to apply all migration changes unless a particular migration step is specifically declared inappropriate for migration by the migration tool. For these cases, perform the migration steps manually.
The activities of the migration tool are broken down into stages. In sequence, the tool:
For each action set (migration modify actions for example), the migration tool tries to perform the migration actions starting from the earliest release to the latest release. For migration from TDI 6.0, the caller must separately invoke the Derby (Cloudscape) migration tool to migrate the database up to the current Derby version. The tdimiggbl tool only makes the required Derby (Cloudscape) modifications to the properties file itself.
The log4j configuration file is specified in the startup script (the bat or sh) file. The command uses a file called tdimiggbl-log4j.properties to set up the log4j logging. The command changes directory to the solution directory and therefore uses the tdimiggbl-log4j.properties file in the solution directory if the TDI installation directory is not specified.