Migration Framework 10.15 | Upgrading Software AG Products On Premises | Prepare for Upgrade | Using Software AG Installer, Software AG Update Manager, Database Component Configurator, and Migration Utilities to Upgrade
 
Using Software AG Installer, Software AG Update Manager, Database Component Configurator, and Migration Utilities to Upgrade
You can upgrade all products using Software AG Installer to install new products; Software AG Update Manager to install fixes; Database Component Configurator to migrate databases; and Software AG migration utilities to migrate product configurations, data, and assets. Migration utilities automatically migrate configurations and data from your old installation to your new installation. For some products, migration utilities run without prompting you for any information (that is, silently). For other products, you can run migration utilities as follows:
*You can run a custom migration, in which you select the configurations and data to migrate. The utility gathers your settings through a series of prompts, then migrates the selected configurations and data. You can export your settings to a file named migrate.dat and use them in other upgrades.
*You can run a migration with imported settings and some prompting or without any prompting (that is, silently). The imported settings can come from settings you exported from a custom migration, or from the default migration provided by Software AG with the product installation in a file named migrateold_releasesbs.dat. The settings for default migrations are described in the product-specific chapters.
Migration utilities write detailed migration information to the command window and to the migrationLog.txt file in the new_Software AG_directory/install/logs directory. By default, utilities write INFO, ERROR, and FATAL messages to the log. If you want to increase the logging level for a product’s migration to DEBUG, go to the product directory that contains the log4j2 file (for example, the new_Software AG_directory/product/bin/migrate, or /migrate/bin, or bin/migrate/resources directory), open the file in a text editor, set the logger.1.level property to DEBUG and save and close the file.
Some products provide scripts instead of migration utilities for migrating configurations, data, and assets.
To use Software AG Installer, Software AG Update Manager, Database Component Configurator, migration utilities, and migration scripts, follow the instructions in this guide.