Installer 10.5 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Migrate Products Using Migration Utilities | Run the Integration Server Migration Utility to Migrate Integration Server or Microservices Runtime | Perform a Custom Migration for Microservices Runtime
 
Perform a Custom Migration for Microservices Runtime
1. On the machine that hosts the new installation, open a command window or shell and go to the new_Software AG_directory/IntegrationServer/bin/migrate directory.
2. Run the command migrate.{bat|sh}.
3. The utility asks for the full path to the Software AG directory that contains the old installation or the ZIP file you made earlier.
4. If the old installation has more than one server instance, the utility asks which instance to migrate and lists the instances in the old installation.
5. The utility asks whether to import migration settings. Enter N.
6. The utility asks whether to migrate custom packages. If you choose to migrate selected packages only, the utility lists each package and asks whether to migrate it.
7. The utility asks whether to migrate the password store, and whether to migrate passwords.
8. The utility asks whether to migrate Integration Server configuration files. If you choose to migrate selected configuration files only, the utility lists each configuration file and asks whether to migrate it. There are about 50 configuration files.
9. The utility asks you to specify the behavior to use for new properties that have been added to the new installation and existing properties that have new defaults in the new installation. If you choose to specify the behavior to use, the utility lists each property and asks whether to use the new behavior or preserve existing behavior. You can read about these properties in the Microservices Runtime readme.
For CloudStreams, select the new behavior asNeeded for the watt.server.http.listRequestVars property.
10. The utility asks whether to migrate functional aliases, database driver configurations, and JDBC connection pool configurations. If you enter Y for JDBC connection pool configurations, the utility asks whether to use the live database or a cloned database with each migrated connection pool. If you respond that you are using a cloned database for the migrated connection pool, the utility asks for the database URL, user, and password.
11. If the Microservices Runtime hosts Wm packages, the utility asks whether to migrate the configuration files for those packages. For some products, you might see additional prompts for migrating other data.
12. The utility asks whether to migrate custom jar files. If you choose to migrate selected custom jar files only, the utility lists each custom jar file and asks whether to migrate it.
13. The utility asks whether to update the host name in your database tables. If the old and new installations are on different machines, respond Y.
14. The utility asks whether to export your settings. If you want to perform other migrations by importing the settings from this session, enter Y. If not, enter N.
15. The utility asks whether to begin migration. If you enter Y, the utility migrates the data you selected.