Product | Migration Command |
Application Platform | sagcc exec administration product target_node_alias PLSCore migration migrate {srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file} |
Digital Event Services | sagcc exec administration product target_node_alias DEVRuntime migration migrate {srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file} |
Integration Server or Microservices Runtime and Hosted Wm Packages Command | If you want to run a custom migration, first run the migration utility manually, and then specify the resulting migrate.dat file on the importFile parameter. If you are upgrade on the same machine and you want to migrate all instances, do not specify the instanceName parameter. If you are upgrade Integration Server on a new machine, migrate one instance at a time to avoid causing concurrency issues with your database. 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] |
My webMethods Server | If you want to run a custom migration, first run the migration utility manually, and then specify the resulting 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 MwsProgramFiles migration migrate {srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file} [importFile=full_path_to_migrate.dat] [instanceName=name[,name...]] [newNodeName=instance_name:new_node_name[,instance_name:new_node_name...]] [cloneDbURL=URL cloneDbUser=user cloneDbPassword=password] Note: If you migrate the instances, and then have to re-run the migration later for some reason, Command Central handles the re-migration differently than the migration utility. If migrated instances in the new installation have the same name as old instances, the utility deletes the migrated instances and then re-migrates the old instances. Command Central, conversely, skips the migrated instances and only re-migrates old instances that do not yet exist in the new installation. |
Universal Messaging | If you want to run a custom migration, first run the migration utility manually, and then specify the resulting migrate.dat file on the importFile parameter. If you want to migrate all instances, do not specify the instanceName parameter. sagcc exec administration product case_sensitive_target_node_alias NUMRealmServer migration migrate {srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file} [importFile=full_path_to_migrate.dat] [instanceName=name[,name...]] |