Migrating a My webMethods Server Instance
Command Central uses the built-in migration utility of My webMethods Server to migrate My webMethods Server instances from an existing installation to a new installation. For more information about the My webMethods Server migration utility see Upgrading Software AG Products.
Before you migrate a My webMethods Server instance using Command Central:
1. Ensure that the My webMethods Server migration utility is available on the target My webMethods Server installation. Check for the migrate.bat file in the Software AG_directory \MWS\bin\migrate directory.
2. Ensure that the migration API for My webMethods Server is available in the migration namespace, using the sagcc list administration command. For more information about the sagcc list administration command, see Software AG Command Central Help.
3. You can create a zip file of the existing product instances to use as the source of the data to migrate. For more information about creating zip files for migration, see Upgrading Software AG Products.
The Software AG Command Central Help describes the generic syntax of the sagcc exec administration command, and the following table lists the command arguments required for My webMethods Server.
Migration Arguments for My webMethods Server
Argument | Description |
srcDir | The full path to the source installation directory of the existing My webMethods Server installation. |
srcFile | The full path to the source archive file with the configuration files and packages of an existing My webMethods Server instance. |
srcVersion | The version of the source installation. |
instanceName | The name of the My webMethods Server instance to migrate. If you do not specify an instance name, the migration utility migrates all instances in the source directory. |
destDir | The full path to the installation directory to which to migrate. |
newNodeName | Applies to My webMethods Server instances in a cluster. A new name for the cluster node that hosts the server instance. The migration utility will rename the node while migrating the instance configuration, and preserve the generated cluster ID. To rename multiple cluster nodes in the same source directory, use a comma-separated list of instance names in the following format: newNodeName=instanceName1:newNodeName1, instanceName2:newNodeName2 |
silent | Specify whether the migration utility prompts for user input during migration. Valid values are true and false. When set to false (default value), the uility executes the migration with prompts. |
importFile | The full path to a migrate.dat file with custom migration settings, exported from previous migrations. |
Command Syntax
To migrate a
My webMethods Server instance from the existing installation directory:
sagcc exec administration product node_alias productid migration migrate
srcDir=source_directory_path
instanceName=mws_instance_name
importFile=migration_settings_path
where source_directory_path is the full path to the installation directory of the existing My webMethods Server installation, mws_instance_name is the name of the instance, and migration_settings_path is the full path to the migrate.dat file that contains custom migration settings.
To migrate a
My webMethods Server instance from a zip file:
sagcc exec administration product node_alias productid migration migrate
srcFile=source_archive_path
instanceName=mws_instance_name
importFile=migration_settings_path
where source_archive_path is the full path to the zip archive file that contains the configuration and packages from the existing My webMethods Server installation, mws_instance_name is the name of the instance, and migration_settings_path is the full path to the migrate.dat file that contains custom migration settings.
For more information about the sagcc exec administration command, see Software AG Command Central Help. For more information about My webMethods Server-specific migration options, see Upgrading Software AG Products.
Examples when executing on Command Central
To check whether
My webMethods Server supports migration as a custom API:
sagcc list administration product local MwsProgramFiles
My webMethods Server runs in the installation with alias “local”. The product ID of My webMethods Server is “MwsProgramFiles”.
To list custom administrative actions for
My webMethods Server in the “migration” namespace:
sagcc list administration product local MwsProgramFiles migration
My webMethods Server runs in the installation with alias “local”. The product ID of My webMethods Server is “MwsProgramFiles”.
To migrate all
My webMethods Server instances installed under the product ID “MwsProgramFiles” in the installation with alias “local” on the
Command Central server with URL “http://localhost:8200/cce”, using the credentials of the default user and the password “manage”:
sagcc exec administration product local MwsProgramFiles migration migrate
srcDir=C:\SoftwareAG
importFile=C:\SoftwareAG\MWS\bin\migrate\MWSVersion\migrate.dat
-s http://localhost:8200/cce -p manage
The migration utility uses “C:\SoftwareAG” for a source directory, and the migration settings from the migrate.dat file in the “C:\SoftwareAG\MWS\bin\migrate\MWSVersion” directory.
To migrate the
My webMethods Server instance with name “test1” in the installation with alias “local” on the
Command Central server with URL “http://localhost:8200/cce”, using the credentials of the default user and the password “manage”:
sagcc exec administration product local MwsProgramFiles migration migrate
srcDir=C:\SoftwareAG
instanceName=test1
importFile=C:\SoftwareAG\MWS\bin\migrate\MWSVersion\migrate.dat
-s http://localhost:8200/cce -p manage
The product ID of My webMethods Server is “MwsProgramFiles”. The migration utility uses “C:\SoftwareAG” for a source directory, and the migration settings from the migrate.dat file in the “C:\SoftwareAG\MWS\bin\migrate\MWSVersion” directory.
To migrate all
My webMethods Server instances installed under the product ID “MwsProgramFiles” in the installation with alias “local” on the
Command Central server with URL “http://localhost:8200/cce”, using the credentials of the default user and the password “manage”:
sagcc exec administration product local MwsProgramFiles migration migrate
srcFile=C:\SoftwareAG\myFolder\mws.zip
importFile=C:\SoftwareAG\MWS\bin\migrate\MWSVersion\migrate.dat
-s http://localhost:8200/cce -p manage
The migration utility uses the archive file named “mws.zip” in the “C:\SoftwareAG\myFolder” directory for a source file, and the migration settings from the migrate.dat file in the “C:\SoftwareAG\MWS\bin\migrate\MWSVersion” directory.
To migrate the
My webMethods Server instance with name “mws1” in the installation with alias “local” on the
Command Central server with URL “http://localhost:8090/cce”, using the credentials of the default user and the password “manage”:
sagcc exec administration product local MwsProgramFiles migration migrate
srcDir=C:\SoftwareAG
instanceName=mws1
newNodeName=mainNode
-s http://localhost:8090/cce -p manage
The product ID of My webMethods Server is “MwsProgramFiles”. The migration utility uses “C:\SoftwareAG” for a source directory, and the migration settings from the migrate.dat file in the “C:\SoftwareAG\MWS\bin\migrate\MWSVersion” directory. During the migration, the utility changes the name of the cluster node that hosts the instance to "mainNode".
To migrate all
My webMethods Server instances in a
My webMethods Server cluster, installed under the product ID “MwsProgramFiles” in the installation with alias “local” on the
Command Central server with URL “http://localhost:8090/cce”, using the credentials of the default user and the password “manage”:
sagcc exec administration product local MwsProgramFiles migration migrate
srcDir=C:\SoftwareAG
importFile=C:\SoftwareAG\MWS\bin\migrate\MWSVersion\migrate.dat
newNodeName=mws_instance_1:mws_node_1,mws_instance_2:mws_node_2,mws_instance_3:mws_node_3
-s http://localhost:8090/cce -p manage
The migration utility uses “C:\SoftwareAG” for a source directory, and the migration settings from the migrate.dat file in the “C:\SoftwareAG\MWS\bin\migrate\MWSVersion” directory. During the migration, the utility changes the name of the cluster nodes that host all three instances in the source directory, to mws_node_1, mws_node_2, and mws_node_3.