Migrate Using Custom or Default Imported Settings without Prompting (Silent)
If you are using a cloned database for Integration Server database components, specify the -cloneDb options on the command as shown below. The migration utility uses the cloneDb options only for the Integration Server 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 Integration Server, 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).
If you want to specify a new name for the migrated instance, specify -newInstanceName.
If the new and old Integration Servers are on different machines, and you want the utility to update the Integration Server host name in your database tables, specify -oldHostName and -newHostName.
If an error occurs, the utility exits.
migrate.{bat|sh}
{-srcDir|-srcFile} full_path_to_{old_Integration Server_directory|ZIP_file}
-importFile {migrateold_releasesbs.dat|full_path_to_migrate.dat}
-instanceName name [-newInstanceName name]
[-cloneDbURL URL -cloneDbUser user -cloneDbPassword password]
-silent true