Migrate Integration Server or Microservices Runtime

2. If you are upgrading an Integration Server or Microservices Runtime that hosts Deployer, follow the instructions in Migrate the Asset Build Environment, Deployer, and Application Platform.

3. If the new and old installations are on the same machine, make sure the old installation is shut down.

4. The migration will scan the old installation for custom packages. However, it will not find custom packages whose names start with Wm, as this naming convention is used for packages provided by Software AG. If you have custom packages whose names start with Wm, and you want to migrate them, go to the new_Software AG_directory/IntegrationServer/bin/migrate directory, open the packages.cnf file, and add a <value name><\value> tag that identifies those custom packages (for example, <value name="WmFINMessages">WmFINMessages</value>).

Note:
To simplify future upgrades, and as a general best practice, do not use the naming convention Wmname for custom packages.

5. Migrate Microservices Runtime using the Integration Server migration utility. Follow the instructions in Migrate Products Using Migration Utilities.

To migrate using the Integration Server migration utility, follow the instructions in Migrate Products Using Migration Utilities.

To migrate using Command Central, use the Command Central command below. If you want to use a custom migration, first run the migration utility manually to create the migrate.dat file (see Migrate Products Using Migration Utilities for instructions), and then specify the migrate.dat file on the importFile parameter. If you want to migrate all instances, do not specify the instanceName parameter.

sagcc exec administration product target_node_alias
integrationServer migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
[importFile=full_path_to_migrate.dat]
[instanceName=name [newInstanceName=name]]
[cloneDbURL=URL cloneDbUser=user cloneDbPassword=password]