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, perform a custom migration that identifies the cloned database and then specify the migrate.dat file on the command below.
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).
The -instanceName option specifies both the old server instance to migrate and the new server instance to migrate to; if the new instance does not exist, the utility will create it. If an error occurs, the utility exits.
migrate.{bat|sh}
{-srcDir|-srcFile} full_path_to_{old_Integration Server_directory|ZIP_file}
-instanceName name
-importFile {full_path_to_migrate.dat|migrateold_releasesbs.dat}
[-cloneDbURL URL -cloneDbUser user -cloneDbPassword password]
-silent true