Migrate Using Custom or Default Imported Settings without Prompting (Silent)
If you are using a cloned database for Integration Server or Microservices Runtime database components, specify the -cloneDb options on the command as shown below. The migration utility uses the -cloneDb options only for the Integration Server or Microservices Runtime database components. If you are using a cloned database for the database components of hosted products (for example, Trading Networks), perform a custom migration that identifies the cloned database, then run the command below with the migrate.dat file created by the custom migration.
On the machine that hosts the new installation, open a command window or shell, go to the new_Software AG_directory/IntegrationServer/bin/migrate directory, and run the command below. For the migrateold_releasesbs.dat file, specify the source release number without periods (for example, 980, or 9100, or 1030).
If you want to specify a new name for the migrated instance, specify -newInstanceName.
If an error occurs, the utility exits.
migrate.{bat|sh}
{-srcDir|-srcFile} full_path_to_{old_Integration Server_or_
Microservices_Runtime_directory|ZIP_file}
-importFile {migrateold_releasesbs.dat|full_path_to_migrate.dat}
-instanceName old_instance_name [-newInstanceName new_instance_name]
[-cloneDbURL URL -cloneDbUser user -cloneDbPassword password]
-silent true