Migrate My webMethods Server
2. If the new and old My webMethods Servers are on the same machine, make sure the old My webMethods Server is shut down.
3. You can migrate using either of two methods.
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
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.