Prepare the Old Installation
1. Install the latest product fixes on the old My webMethods Server, then start the old My webMethods Server.
2. When you edit configuration settings for My webMethods Server, you download the appropriate configuration file from the MywebMethodsServer database component to the My webMethods Server installation, make the changes in that file, and then either upload the file to the database component and delete it from the file system, or keep it in the file system so its settings are used in preference to the equivalent settings in the database (see Administering My webMethods Server). Go to the old_Software AG_directory/MWS/server/instance_name/config directory and check for any such files. If you do not want such files to be migrated to the new installation, delete them from the old installation.
3. Shut down the old installation.
If the product is running | Take this action... |
As a Windows service | Shut down from the Windows Services window. Services are listed as Software AG product release. |
As a Windows application | Shut down from the Windows start menu. Applications are listed as Software AG > Stop Servers > product . |
On a UNIX system | Use the shut down instructions in the product documentation for your old release. |
4. If your old and new installations are on different machines, create a ZIP file of the old product installation to use as the migration source.
a. On the old machine, open a command window or shell, go to the old_Software AG_directory/MWS/bin/migrate or old_Software AG_directory /MWS/bin directory, depending on which old release you have, and run the command below. The command creates a ZIP file named mws.zip in old_Software AG_directory/MWS/bin/migrate directory.
ZIP-mws.{bat|sh}
b. Copy the product’s ZIP file to any directory on the machine that hosts the new product.
Important:
If using FTP to copy, use the binary file transfer mode\type. If you use another mode\type, the ZIP file might become corrupted.